Restore Data - ProxyHost

In-Place Restore
Out-of-Place Restore
Cross-Platform Restores
Restore to Network Drive/NFS-Mounted File System

Overview

The following page describes the agent-specific restore options. Additional restore options are accessible from the Related Topics menu.

The ProxyHost iDataAgent can restore:

File allocation table (FAT) file systems
New Technology file systems (NTFS)
Unix File System (UFS)
Journal File System (JFS) for AIX

When restoring ProxyHost data, you can, if desired, restore the data to a file system type that differs from the type in which it originated. For example, you can restore NTFS data to a FAT file system and restore FAT data to an NTFS file system. FAT file systems do not support Discretionary Access Control Lists (DACL); therefore, any NTFS data that you restore to a FAT partition loses its original access privileges. Conversely, when FAT file system data is restored to an NTFS file system, the restored data inherits the DACL of the destination directory.

Restore Considerations for this Agent

Before performing any restore procedures for this agent, review and verify the following information.

Review the general restore requirements described in What You Need to Know Before Performing a Restore.
It is recommended that you restore data to the same type of operating system from which it was backed up.
The production server and backup host computers are powered on.
The snapshot system configuration is complete. All software required by the snapshot systems has been installed on the production server and backup host.
All batch files have been created and tested.
You have installed the ProxyHost client software on the production server.
You have installed the File System client software on the backup host.
It is important to note that when performing a restore, the Job Controller will show the source machine even though the destination machine may be different.
When restoring data that was backed up from Exchange using the Log truncation feature in combination with a VSS hardware provider snapshot, and the *.chk file was located on a different volume, it must be manually deleted before attempting to mount Exchange Stores after a restore procedure. This will ensure that you will not have a *.chk file which does not match the logs and database being restored, and thus be unable to bring up the Exchange Stores after the restore. Exchange will create a new *.chk file based on the log you restore.
Example:
The System path location of the storage group is: C:\Program Files\Exchsrvr\mdbdata, and not on the volume where the snapshot was taken.

Restore Destinations

By default, the ProxyHost iDataAgent restores data to the client from which it originated; this is referred to as an in-place restore. If desired, you can also restore the data to a different ProxyHost client. Keep in mind the following considerations when performing such restores:

The destination client must reside in the same CommCell as the client whose data was backed up.

The following section enumerates the types of restore destinations that are supported by the ProxyHost iDataAgent. See Restore/Recover/Retrieve Destinations - Support for a list of Agents supporting each restore destination type.

In-Place Restore

Same path/destination

Out-of-Place Restore

Cross-Platform Restores

Same Operating System - Different Version
Refer to Cross-Platform Restores for Windows for considerations when performing these types of restores with Windows file system data.

For Unix File System data, Cross-Platform restores can only be performed between different versions of the same Unix (e.g., Solaris 8 data can be restored to Solaris 9, but cannot be restored to AIX).

Restore to Network Drive/NFS-Mounted File System

Besides restoring data to a client computer’s local drive, you can also restore data to a UNC path (Windows) or NFS-mounted file system (Unix). (See Restore to Network Drive/NFS-Mounted File System for comprehensive information.)