Download backup script

Appendix B

Download Sharon Dooley's disk init generation script

Appendix C

Download DBCC script

Appendix D

Download Vince Iacoboni's task generation script

Appendix E

The essence of this scenario is as follows:

1. Each of the individual servers can backup their data to a central repository in the most efficient manner possible.
2. The Backup Server contains all of the backups from the individual applications while also containing each of the server images.
3. These images and backups are then picked up and archived to tape.
4. The tapes are then rotated offsite.

This configuration gives the ability to have a complete environment image located on the Backup Server available for immediate restore in the case of a system failure. If this image is corrupt or otherwise unusable, then the tape based backup can be restored to the Backup Server and recovery can proceed as normal.

The Backup Server will get its data dumps via the following.

1. SQL Server will perform direct database dumps to the Backup Server

SQL Server backups are recommended for a variety of reasons.

1. It is a solid, built in backup solution that incurs no cost.
2. It is extremely stable and does not use any proprietary file formats.
3. It integrates with any Enterprise backup solution since it simply creates dump files.
4. It contains all of the functionality required for backup and restoration.
5. It contains no bugs which are sporadic amongst all of the third party backup solutions.

<Insert Enterprise backup software here> is recommended for the normal file level backups because it is reliable and also the corporate standard solution.

6.5 Disaster Recovery Plan 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18