HOWTO: Use NetBackup to perform a restore for a total and complete recovery of Windows client(s) that include C: (and other system) drive(s), Shadow Copy Component, and/or System_State from a reliable full MS-Windows backup without IDR or BMR in the event of a Disaster (or need to fall back to a known working state).
How to use this guide:
This guide is provided as a general/generic template that would be applicable for most restores, and may require trial-and-error and multiple attempts. Most of the time using the following steps the way it is, will result in good bootable system.
The guide is intended for restore back to the original machine. If the machine is damaged and replaced with another machine (regardless of being 99.999% identical make/model) this is no longer considered the original machine. You may attempt to treat it like an original restore (using w2koption), but there is a risk that restore will result in a non-bootable system (if this is the case, retry without w2koption). For non-original system restore do not use w2koption. If target is not the original, the larger the difference from the original machine, the lower the success rate of a bootable system.
This guide is NOT intended for system cloning. It is intended for Disaster Recovery of a client back to original hardware, or a near identical new hardware should the original no longer be available.
- This is for a client system restore only.
- This procedure will restore your computer's system files and data files to a pre-disaster state except those protected by one of the NetBackup database agents, such as the Exchange agent or SQL agent. If any of your data is protected by NetBackup agents, refer to the section on restoring the data protected by the agent before beginning disaster recovery.
- This procedure does NOT utilize NetBackup Bare Metal Restore (BMR) or NetBackup Intelligent Disaster Recovery (IDR) but instead makes use of standard Windows-NT backups of all local drives including System_State (Windows 2000 and earlier AND NetBackup 4.5 and earlier) or Shadow Copy Components (Windows 2003 and later AND NetBackup 5.1 and later).
- Any Windows 2003 (or later) client backed up previously by NetBackup client 4.5X would not support Shadow Copy Components restore. You must select only System_State. This is true trying to restore from an OLDER version 4.5X backup even if the client has been upgraded to 5.X or later.
- The success of a full restore will depend on a "reliable" full system backup. So if System State or Shadow Copy Components backups complete with a Status 1, then it is not reliable for a Disaster Recovery Scenario.
- This procedure requires Windows installation media from Microsoft in order to perform reinstallation of the operating system. The same version/suite must be used. For example, if the original version is Windows Server 2012 Standard Edition with Service Pack 2, that same version must be installed for disaster recovery. In some cases, critical hotfixes provided by the operating system vendor will be required to perform a successful restore. e.g., VSS rollup patches. All related hardware drivers that are required to reinstall Windows and configure networking must be available and ready. Network functionality after windows is booted up is a requirement. NOTE: For a higher success rate, install the same drivers (and applications which install drivers) the system had when the backup was made. Failure to do so can result in a post-restore reboot loop.
- For Windows 2003 clients (any variants e.g. SP1, SP2, R2, x86, x64), make sure it already has Microsoft VSS patch KB940349 installed prior to restore. If not, download the patch from http://support.microsoft.com/kb/940349, install and then reboot the server before proceeding.
NOTE: You may have to [re]install drivers even after a successful restore and reboot.
NOTE: When using an imaging software to rebuild the box, please verify it is supported by Microsoft.
Other options to consider:
- NetBackup Bare Metal Restore (BMR) protects client systems by backing them up with a policy configured for BMR protection. For a complete description of BMR backup and recovery procedures, see the Bare Metal Restore System Administrator's Guide.
- If you installed and configured NetBackup Intelligent Disaster Recovery (IDR) on the client system, refer to the NetBackup Administrator's Guide, Volume II, for recovery procedures instead of the instructions below.
1. Setup and Install Windows.
Install the original version of Windows. This basic Windows installation is necessary to provide NetBackup with a target to which it can restore the system. The computer name, Windows directory, and the file system type (such as NTFS) must be the same as it was on the previous Windows installation. This installation will be overwritten by the recovered version, which will restore your original system configuration, application settings, and security settings. After setup, install the necessary service packs to bring Windows to the same level as was previously installed.
NOTE ABOUT HARDDRIVE PARTITIONS: If you are recovering from a disk failure, use Windows Setup to partition and format the new disk during installation. Use the same partition layout or larger as was on the previous drive. If smaller partition sizes are configured, this can cause a restore failure and or BSOD on boot post-restore. Format the partitions with the same file system type as before the failure.
- If the system was in a specific domain or workgroup, do not join the domain or workgroup at this time.
- If you are recovering a domain controller, do not perform the domain controller installation process at this time.
2. Configure Network.
Reinstall Network Interface Card (NIC) drivers (same version) if Windows does not have built-in support for the NIC. The same IP and hostname must be used.
NOTE: Consult your Windows administrator, network administrator, NIC hardware/installation manual and/or NIC vendor support channel for additional information regarding driver support and configuration under Windows.
3. Install NetBackup Client.
Install the same version of the NetBackup Client for Windows as it was during the backup, including any necessary patches. Do not install a newer (higher) version than the master server.
If the client version is not known, the version file (<install_path>\VERITAS\NetBackup\version.txt) can be restored from the backup image of the client to an alternate location on the master or a media server and examined.
RECOMMENDATION: Perform a custom installation where NetBackup is not installed to the same drive as Windows. If you have to reformat and perform a Windows installation again, you will not lose access to NetBackup client logs.
4. Enable NetBackup client logs:
5. Start the restore process.
NOTE: For this procedure to work, the restore must not be initiated from the Client. Rather, initiate the restore from the Master Server or Remote Admin Console.
Prior to NetBackup 7.7.1: If multiple images are selected (for example, a full and two incrementals), the restore will ONLY use the latest image. BMR won't restore the full image followed by the incrementals because overlapping System State / Shadow Copy Components restoring is not allowed.
At NetBackup 7.7.1 and above: If multiple images are selected, the restore will pick the full image first followed by any subsequent incremental images. Do not attempt to restore the same image twice (or restore another full image after restoring a full image) as it is still not allowed.
Double-check to see if there is any System data on other drives that needs to be restored. At this time, if there is any, restore it.
7. [Optional] Restore other data.
Perform restores of other drive letters (non-system Drives) before rebooting. (Alternatively, you could perform this step after the reboot.)
8. Stop the service named "NetBackup Client Service" or "NetBackup Legacy Client Service".
NOTE: If the Windows DR restore is being run remotely using the Windows 'Remote Desktop' (or 'RDP') utility to connect to the target Windows server, the NetBackup 'bpinetd.exe' process sometimes does not terminate 'gracefully' when the restore of the Windows Volumes (for example: C: or D:) and the 'Shadow Copy Components' (or just the 'System State') are ran from the same RDP session, thus preventing the post-restore 'registry-merge' tasks to from being ran; usually resulting in a BSOD (blue-screen-of-death) when the target Windows server is rebooted.
However, in-house testing of Windows DR restores using the Windows 'Remote Desktop' utility have found that this issue can be avoided by using one RDP session to restore the Windows volumes (C:, D:, E:, etc..); and then closing the first RDP session (after all Windows volumes have been restored) and opening a new RDP session to run the 'Shadow Copy Components' (or just the 'System State') portion of the DR restore, and to then 'gracefully' stop the NetBackup 'bpinetd.exe' process after the 'System State' restore (as detailed below) before rebooting the target Windows server.
To verify the post-restore registry manipulation is completed there are 3 options:
NOTE: The log specific to steps 8.1 and 8.2 is ...\NetBackup\logs\bpinetd
net stop "NetBackup Client Service"
net stop "NetBackup Legacy Client Service"
9. Transfer logs from restore before rebooting!
Transfer the client's NetBackup logs to an area where you can access them if the post-restore reboot fails.
After the reboot, if a blue screen occurs while the client is starting Windows, attempt to boot using Safe Mode (or Safe Mode with Networking). If a Safe Mode Boot succeeds, take a look at the Windows event logs, and export them. Transfer them to another partition (or network location if Networking is enabled and working under Safe Mode). If there is no alternate method to access and transfer data, reinstall the operating system again and set up Networking so evidence can be sent to the Technical Support of various vendors, including Symantec for NetBackup support.
NOTE: If you took a chance and restored to a non-original machine with w2koption, retry this procedure again (reinstall/rebuilding Windows also) and skip over w2koption. If it still fails to boot and this is Windows 2003, retry again without w2koption AND only restore System_State from Shadow Copy Components.
NOTE: The first boot after doing a full OS restore of Windows 2008 or Windows 2008 R2 may take 5-10 minutes or longer. It may show a blank screen during this time. The machine is not hung. Do not reboot forcefully during this time, as it may corrupt the OS causing it not to boot up. The slow boot is due to a bulk file-rename for files which were restored with temporary file names because their production counterparts were active and locked at the time of the restore. This also happens with Windows 2003, but the file-set is much smaller and the boot-lag is therefore much shorter in duration.