Performing a local Disaster Recovery with 11d

A local disaster recovery is when you are recovering a Backup Exec media server, with no assistance from other Backup Exec media servers. If you have more than one media server, it's easier to perform a remote disaster recovery using another media server

To perform a disaster recovery (restore from scratch) of a Windows XP, Windows 2000 or Windows Server 2003 computer, the relevant section of the Backup Exec 11d Administrator's Guide is page 659 onwards.

This process is also relevant for domain controllers, unless you are doing an authoritative restore. This covers restoring the Backup Exec media server.

The basic process is:

  1. Reinstall Windows on the PC, using the same filesystem type (NTFS or FAT) as before. Give it network settings, and the same computer name as at the time of backup. Don't join it to the domain, but instead leave it in a workgroup.
  2. Install Backup Exec, however you MUST select a different installation path from where your normal Backup Exec installation is located. Don't enter any serial numbers, as you don't need the options at this point.
  3. During installation, select a different installation path for your SQL Express instance.
  4. Inventory your backup media, then catalog it.
  5. Using Backup Exec, restore all the media server's hard drives and Shadow Copy Components. Set the Restore over existing files option.
  6. Do not reboot the server yet.
  7. Open the directory where your SQL Express files are normally installed (such as C:Program FilesMicrosoft SQL ServerMSSQL$BKUPEXECData
  8. Rename the files:
    1. master$4IDR to master.mdf
    2. mastlog$4IDR to mastlog.ldf
    3. model$4IDR to model.mdf
    4. modellog$4IDR to modellog.ldf
    5. msdbdata$4IDR to msdbdata.mdf
    6. msdblog$4IDR to msdblog.ldf
  9. Change the attributes of the above files to remove the read-only flag.
  10. Reboot the server.
  11. You may need a second reboot as Windows redetects hardware devices.
  12. Your media server will now be at the state it was when the backup took place, but before the backup completed – i.e. with serial numbers installed, catalogs and jobs restored, but not the media you have just restored from (or any later backups) in the catalog.
  13. If you need to perform further restores from the media you've just restored from, you need to re-catalog it. Note that for this to work you may need to move the media to the Retired Media set, delete it, then re-inventory it.
  14. Delete the folder location where you installed your temporary Backup Exec installation (optional).

Note that there are some steps you can take to speed up the above process. There are also some potential problems which can occur. These hints and tips are used at your own risk.

  • When installing the temporary Backup Exec installation, there's no need to install the documentation.
  • To save having to re-catalog the media after performing the restore, shutdown the Backup Exec services, copy the contents of the temporary installation's catalogs folder to your restored catalog folder, then restart the Backup Exec services.
  • As soon as you've restored the media server, put any scheduled jobs on hold – you don't want to accidentally overwrite your media! For this reason it's a good idea to use the write protection tab on the media before starting.
  • If you have problems with the media not being able to be catalogged, delete the media from Backup Exec (you will have to move it to Retired Media first). This won't delete the tape contents, but will make Backup Exec "forget" about it.