Topics | How To | Full System Restore | Related Topics
Restore Considerations for this Agent
Maximum Filename Length for Unix File System iDataAgent Restores
Restore VMware Virtual Machines
Restore Data to Trusted Solaris 10 Systems
The following page describes the agent-specific restore options. Additional restore options are accessible from the Related Topics menu.
Each Unix File System iDataAgent except for the IRIX File System iDataAgent supports data recovery operations for the appropriate Unix File System (UFS) data. In some cases, operations for some other File System data (e.g., CD-ROM File System [cdfs]) may be also supported. Also, some iDataAgents can recover additional file systems. For more information, see File Systems supported by the Unix File System iDataAgents.
In addition, depending on the specific Unix File System iDataAgent(s) and perhaps particular scenarios, data recovery support may or may not be available for the following items, among others:
See Effect of Data Types on Restores by Unix File System iDataAgents for more information.
For the Unix File System iDataAgents, restore operations can be performed from the client, iDataAgent and backup set levels in the CommCell Browser.
When the root file system is lost, a full system restore is required. See the following as appropriate for more information:
To recover a VMware ESX Server using the Linux File System iDataAgent, see the following for more information:
For some Unix platforms, to recover a system that has defective components without having to reinstall operating system files and other file types, see the following as appropriate for more information:
Try to avoid the unconditional overwrite of the root directory on a live file system. This is a mechanism that allows an unconditional overwrite of open files in the root directory (/) on a live file system. Performing such a restore can result in an inconsistent system that may also fail to boot. Use this option AT YOUR OWN RISK. |
You can restore Unix File System data to any Unix client computer regardless of the specific Unix operating system that is installed on the client. For example, you can restore data backed up from a Solaris client to a Linux client. You can also restore to any Unix client.
When restoring any Unix File System data, keep the following in mind:
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.
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.
When restoring any Unix File System data other than HP-UX File System data, keep the following in mind:
When restoring any Solaris File System data, keep the following in mind:
Finally, see Effect of Data Types on Restores by Unix File System iDataAgents for more information.
The names of files (including the path) to be restored by any Unix File System iDataAgent except the AIX File System iDataAgent cannot contain more than 1024 characters. For the AIX File System iDataAgent, the names of such files (including the path) cannot contain more than 1023 characters.
The AIX, HP-UX, Linux and Solaris iDataAgents allow you to restore raw device files, including block and character, for their respective file systems.
Raw devices can be restored either in place or out of place. Also, best performance can be obtained using the character device.
The individual guest operating systems of the Virtual Machines running under the VMware ESX Server Can be restored using the appropriate iDataAgent. These operating systems can be Unix operating systems as well as other operating system types (e.g., Windows, NetWare, etc.) Also, you can use Command Line Interface to perform restores. For more information and procedures, see Restore a VMware ESX Server 2.5.x Virtual Machine.
For a VMware ESX Server using Consolidated Backup, you can restore individual files backed up from a Virtual Machine. Based on the particular type of backup you performed (see Back up a VMware ESX Server 3.x Virtual Machine) select one of the following:
In addition, you can restore a Disk Image for a VMware Virtual Machine which was backed up using VMware Consolidated Backup, whether the backup was performed from a VCB Proxy Server, or from the Service Console. For more information and procedures, see Restore a VMware ESX Server 3.x Virtual Machine Disk Image.
You can restore MAC File System data to any Unix client computer regardless of the specific Unix operating system that is installed on the client. For example, you can restore data backed up from a MAC client to a Linux, AIX or other Unix client.
You can restore AppleDouble-encoded Macintosh files that contain resource fork data to a Unix File System. Ensure that the Recover Apple Resource Fork Data option is selected in the Browse/Recovery Option dialog box from the Control Panel and in the Advanced Restore Options dialog box for your iDataAgent before you run a restore of this data.
You can control restoring data to zones on Trusted Solaris 10 systems by using the Enforce Label Checking on Trusted Solaris option in the Advanced Restore Options dialog box. This is useful if the data should be included only in a single zone (e.g., a "restricted" zone) or in multiple specified zones and should therefore be available only to authorized users.
Hard links that have been backed up with registry key HLINK set to Y and the appropriate hard link updates applied can be restored using Browse and Restore or Restore by Jobs. This includes hard links that are missing before the restore.
See the Service Pack documentation for more information on hard link updates. |
Browse and Restore can be used to restore missing hard links as part of a link group. To restore hard links as part of a link group, you must select the Unconditional Overwrite option in the Restore Options (General) dialog box.
When you use Browse and Restore to restore hard links as part of a link group, the following happens:
The first file is the first one selected in the Browse windows or the first one that it is backed up.
Missing hard links that are restored using Restore by Jobs are linked together in their own link group (that is, in a link group separate from that for files that are not missing).
By default, the Unix 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:
Note that when you perform restores other than in-place restores, the restored data assumes the rights (i.e., permissions) of the parent directory.
Even if the file name itself is within the character limit, an out-of-place restore will fail if the resulting directory path to which the file is restored exceeds the character limit. |
The following section enumerates the types of restore destinations that are supported by the Unix File System iDataAgent. See Restore/Recover/Retrieve Destinations - Support for a list of Agents supporting each restore destination type.
For in-place restores involving symbolic links to a raw device, all the symbolic links leading to the raw device as well as the parent directories of these symbolic links are restored. Also, the destination raw device node is created automatically, and the associated data is restored in that raw device.
An in-place restore to directories with existing (e.g., identical) files will invariably result in the job completing with errors. These errors are usually the result of "skipped" files. This condition will also occur when restoring data to "/", and it will potentially yield many errors. The results of the restore can be viewed using View Restore Items with options "successful", "failed", "skipped", and "all". |
Keep in mind that out-of-place restore operations are also subject to the conditions described in Cross-Platform Restores.
Symbolic links to raw devices that are included in the target directory for an out-of-place restore are restored in place.
Restoring Unix Data to Windows, Macintosh and Other Unix Platforms
When you backup the ACLs in the binary format in Solaris Sparc, you cannot restore them to Solaris x64. Similarly for HP-UX, when you backup the ACLs in the binary format in HPUX PARISC, you cannot restore them to HP IA64. |
Restoring Unix to Windows Issues
Restoring Windows to Unix Issues
Besides restoring data to a client computer�s local drive, you can also restore data to an NFS-mounted file system. (See Restore to Network Drive/NFS-Mounted File System for comprehensive information.)
Even if the file name itself is within the character limit, an out-of-place restore will fail if the resulting directory path to which the file is restored exceeds the character limit. |