Topics to be covered:

1. A section on what pieces of the system need back up. Customers need to understand how their architecture choice may limit their backup options. For example, keeping the app sever separate from the db server.
2. Magnolia Backup module - While the backup module "works" it has known bugs and can be difficult to use if you're not super familiar with it. In times of real crisis using it could create a frustrating situation. Often the people in charge or performing a restore aren't the people using magnolia. DB admins, systems admins, etc. Often I recommend customers use this module as a second line of defense.
3. Virtualization approach
4. DB and repository (filesystem) backups. Usually nightly. Involves shutting the system down to perform the backup.
5. Customers using oracle may choose to store everything in the DB. The Oracle product has more sophisticated backup options.
6. Maybe a section on what amazon offers, or rackspace perhaps. If anything.