Search
Home
Articles
Backup
Books
Certification
FAQ
Products
Replication
Scripts
Seminars
Training
TSQL

MSDN Fourms
Philippine SSUG
Fort Worth SSUG
Oklahoma City SSDG

Resume

MHS Enterprises
BlowFrog Software
FilAm Software
AcrylicAcetate.com
Bargain Humidors
Western Humidor

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

Perform a single table restore from the most recent backup. You must be careful of and account for any key relationships in the database. If a single table restore does not work due to data conflicts or the table contains a text or image column, continue on to the final suggestion.
  1. If replication is installed, stop replication
  2. Dump the transaction log using the no_truncate option
  3. Restore the most recent backup
  4. Apply all transaction logs
  5. If replication is installed, remove replication for that database
  6. If the database is replicated, verify all replication components have been eliminated
  7. If the database is replicated, reinstall replication
  8. If the database is replicated, verify and test installation of all components
  9. Perform a full backup of the database

The final way to recover is to restore the entire database and apply all transaction logs. This is also the safest way in order to ensure you account for any primary - foreign key relationships.

  1. If replication is installed, stop replication
  2. Dump the transaction log using the no_truncate option
  3. Restore the most recent backup
  4. Apply all transaction logs
  5. If replication is installed, remove replication for that database
  6. If the database is replicated, verify all replication components have been eliminated
  7. If the database is replicated, reinstall replication
  8. If the database is replicated, verify and test installation of all components

Corrupt System Table

There is exactly one way to recover a corrupt system table. That is to restore from the most recent backup.

After restoring the master database, there are two ways to restore the rest of the system.

  1. If replication is installed, stop replication on all databases
  2. Place all databases in dbo use only mode
  3. Run setup and run the rebuild master option
  4. Restore the master database from the last backup
  5. Stop SQL Server
  6. Restart in single user mode
  7. Using isql/w, log in to the server
  8. If master fails to restore cleanly
    1. Rebuild master
    2. Turn on allow updates
    3. BCP in the file from syslogins
    4. Turn off allow updates
    5. Do NOT attempt another restore of master and do NOT restore msdb
    6. Run script to recreate all dump devices
    7. Run script to recreate all tasks with the exception of replication tasks
    8. Run disk reinit and disk refit on each database
  9. Stop and start SQL Server
  10. Verify all databases recovered correctly
  11. If replication is installed, remove replication for that database
  12. If the database is replicated, verify all replication components have been eliminated
  13. If the database is replicated, reinstall replication
  14. If the database is replicated, verify and test installation of all components

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

Michael R. Hotek

All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.