SQL+Server灾难恢复及备份恢复.pptVIP

* * * * Business Implementation Perform full database backups if: The database is small. The amount of time that is required to back up a small database is reasonable. The database has few data modifications or is read-only. Performing a full database backup captures a reasonably complete set of data. You may be willing to accept a minor loss of data if the database fails between backups and must be restored. * Business Implementation Perform a full database and transaction log backup strategy for frequently modified databases. You also should consider whether the database and transaction logs could be backed up in an acceptable amount of time. Strategy Example Consider the following example of a backup plan and the steps that you would take to restore your database. Assume the following: The database and transaction logs are stored in separate files on separate physical media. A full database backup is done each night at 6:00 P.M. The transaction log backups are performed each day at 9:00 A.M., 12:00 noon, and 3:00 P.M. The physical medium that contains the database is damaged at 1:30 P.M. Topic Objective To discuss the advantages of implementing a full database and transaction log backup strategy. Lead-in In addition to performing a full database backup, you also should back up the transaction log. * Use this strategy to reduce recovery time if the database becomes damaged. For example, rather than applying multiple, large transaction logs, you can use a differential backup to apply the changes that were made to the database since the last full database backup. * Business Implementation Use this strategy for a VLDB that is partitioned among multiple files. When combined with regular transaction log backups, this technique offers a timesensitive alternative to full database backups. For example, if you have only one hour to perform a full database backup (which normally takes four hours), you could back up individual files each night and still ensure data