Disaster Recovery of a remote Windows 2000 or 2003 computer (includes non-authoritative restore of Active Directory for a domain controller)
Disaster recovery can be performed on a remote computer attached to the media server. This procedure will restore the remote computer's operating system to its pre-disaster state and will restore all data files, except those protected by one of the Backup Exec agents. If any of the data on the remote server is protected by Backup Exec database agents, read "Additional Backup Exec Options" in the Backup Exec Administrator's Guide.
The following items are required:
- A current full backup of the computer to be recovered and any subsequent incremental/differential backups
- The Windows 2000 or 2003 installation media and service packs for Windows 2003 only.
To recover a remote Windows 2000 or 2003 computer:
- This basic Windows installation is necessary to provide Backup Exec with a target to which it can restore the system. The computer name, Windows directory and the file system (NTFS) must be the same as the previous Windows installation. This basic installation will later be overwritten by the backed up version, which will restore the system configuration, application settings, and security settings.
- If the machine is being recovered from hard disk failure, use Windows setup to partition and format the new disk during installation. Format the partitions with the same file system as before the failure.
- If the system was upgraded from Server 2000 as evidenced by a winnt folder with no windows folder in the restore selections, then this new OS must match. It must be upgraded from server 2000 prior to the restore attempt.
- For Windows 2003 only - apply service packs to the same level as before the disaster
- Do not join a domain, leave the computer in a workgroup
- Do not install Active Directory
- Note: If the server was previously joined to a domain, or was a DC, verify the Fully Qualified Domain Name (FQDN) is shown. To up the FQDN: Logon to the remote server to be restored, right click "My Computer" and select the Computer Name tab > Change > More > Primary DNS suffix of this computer and add the FQDN in the DNS suffix.
NOTE: This typically represents a few hours of work up to this point. If anything is misconfigured on the new OS, or if the restore fails for any reason, the work done thus far may be lost. It is highly suggested to take a Symantec System Recovery(SSR) backup of your clean operating system now. This can be done using SSR in trial mode and so does not require a key. If the restore goes bad, the clean OS can be recovered by booting from the Symantec System Recovery Disk (SRD)
3. Start Backup Exec for Windows Servers
5. From the Devices tab, Inventory the media containing the latest full backup of the computer to be recovered
- Restore security
- Preserve tree
- From the Advanced tab, select Mark this server as the primary arbitrator for replication when restoring folders managed by the File Replication Service, or when restoring SYSVOL in System State
- Click Run Now to start the restore
- Reboot the remote computer