Topics | How To | Full System Restore | Related Topics
Restore Considerations for This Agent
Restoring Microsoft Virtual Server and Microsoft Hyper-V Virtual Machines
The following page describes the agent-specific restore options. Additional restore options are accessible from the Related Topics menu.
The Windows File System iDataAgent supports the following types of restores for Windows:
For the Windows File System iDataAgents, restore operations can be performed from the client, iDataAgent, and backup set levels in the CommCell Browser. The system state is restored, like other File System data, through a Windows File System iDataAgent subclient. For more information, refer to Restoring System State on the System State page.
For more information on the OCS restore, refer to the Office Communications Server.
To provide the automated rebuilding and restoration of Windows client computers, see the following for more information:
Before performing any restore procedures for this agent, review the following information:
When a file that is to be restored is locked, the system automatically writes the file to another file name within the same directory and records the instance in the Windows registry. The system then prompts you to restart the system. You can either restart the computer then or at a later time. Upon restart, the computer automatically overwrites the files with the restored data.
Do not set a quota for an object (such as a volume, directory, or user) that is lower than the amount already used. Doing so may cause improper results for data protection or recovery operations.
Full system backups of a created ADAM instance cannot be restored using full system restore.
Running an out-of-place Restore by Jobs for a Windows subclient will unintentionally restore Job Results-related folders and files.
A backup of Mount Points (volume junctions) can back up the data pointed by
the Mount Point using the Advanced Backup option, "Follow Mount Points".
On the other hand a backup of directory junctions do not backup the data pointed
to from the directory junction by design. This is to prevent undesired backup
and recovery results for system created directory junctions.
During a backup when a directory junction point is encountered, only the
junction point will be backed up. When the source directory and data linked to
the junction point is encountered, the data will be backed up To backup the
source data of a junction point that is not part of a subclient contents, the
source data must be explicitly added to a subclient's content.
An advanced restore option allows you to filter out mount points that are part of the backup data during the file system restore. This is useful in cases where you did not mount all the mount points and do not want to fill up the holding file system during the restore. Using this option will ensure that data belonging only to the restoring file system will be restored.
VSS and non-VSS system state restores require that the Job Result Path reside on the same drive as the data to be restored.
By default, the Windows File System iDataAgent restores data to the client computer from which it originated; this is referred to as an in-place restore. You can also restore the data to another Client computer in the CommCell. Keep in mind the following considerations when performing such restores:
The following section enumerates the types of restore destinations that are supported by the Windows File System iDataAgent. See Restore/Recover/Retrieve Destinations - Support for a list of Agents supporting each restore destination type.
Keep in mind that out-of-place restore operations are also subject to the conditions described in Cross-Platform Restores.
Restoring Windows Data to Unix Platforms
The following cross-platform restore operations for Windows data are supported:
NOTES:
Cross-platform file system restores from Windows to Unix of files encrypted by the Windows operating system are not supported.Besides restoring data to a client computer’s local drive, you can also restore data to a UNC path. (See Restore to Network Drive/NFS-Mounted File System for comprehensive information.)
You can restore Microsoft Virtual Server and Microsoft Hyper-V virtual machines that were backed up using the VSBackupUtil utility. See Restore Virtual Machines on Microsoft Virtual Server and Restore Virtual Machines on Microsoft Hyper-V for step-by-step procedures.