Full System Recovery: Windows File System Agent
Full system recovery of a Windows file system client includes the following phases:
Preparing for a Full System Recovery
- Perform regular backups of the file system data. These backups can be scheduled to run at convenient intervals.
- If you have excluded any critical system state component from the backup, you cannot use that backup for the system restore. Ensure that the following critical system state components are not excluded from the backup:
- System Protected Files
- Active Directory
- Cluster DB
- Sysvol (For 2000 or 2003 domain controllers level)
- DFSR (Windows 2008 Domain controller level)
What Gets Restored
You can restore any one or all of the following components during full system restore:
- File System
- System State
- Office Communications Server
What Does Not Get Restored
By default, the SnapProtect files and registry entries are excluded from the restore. After the full system restore, when you install SnapProtect, all the latest patches will be available.
If the backup contains all the latest patches, create the nDisableGalaxyMerge additional setting and set the value to 1 to restore the registry entries for SnapProtect.
Full System Recovery Methods
Based on the client environment, you can recover the file system data using one of the following methods:
- Recovering a Non-Domain Controller
- Recovering a Domain Controller
- Recovering RIS Server with SIS Common Store
- Recovering a Cluster on Windows Server 2003
- Recovering a Cluster on Windows Server 2008 and Later
Use the 1-Touch recovery process to rebuild and recover the operating system and file system data on a single or multiple clients with same or different hardware configurations. You can recover systems with defective components such as inaccessible volumes or crashed disks, without installing the individual software packages or operating systems manually.
For more information, see Overview -1-Touch.