It is assumed that a file system path policy that creates repository snapshots has been implemented and that at least one snapshot has been created in the designated repository store. See How to batch backup a file system path to a repository for an example of how to do this.
This task describes the steps to follow when restoring a file system path snapshot from a repository store to a node other than the one from which the backup originated, as shown:
- Identify the destination where the data set is to be restored. Here we will restore the snapshot to a different machine to the one from which the data originated.
Depending on the scenario, you can restore data to its original node and directory, its original node in a different directory or to a different node entirely.
- Ensure that the restore location is prepared to receive the restored data set by locating the node in the Nodes Inventory and checking it is authorized and online.
The restore location must have Protector Client software installed. We will assume that no applications are accessing the restore location since the restored data doesn't yet exist.
- In this example we will assume that there are no backup policies currently active on the location where the data set is being restored, so there is no need to suspend any data flows. The existing backup policy can continue to run while we perform our restore.
- Locate the data set to be restored by navigating to the Repository Snapshot Details (Storage) - File System for the repository store snapshot in question.
- Check that the target restore location (identified in the previous steps) has enough free space to accommodate the restored snapshot.
The Logical Size of the snapshot is shown in the Analysis Details area of the Repository Snapshot Details (Storage) - File System. It may be necessary to click Analyze if these details have not yet been evaluated.
- Click Restore Snapshot to open the Restore Repository Snapshot Wizard - File System.
CAUTION:The process of restoring data may result in the overwriting some of the original data that exists on the restore location.In this example we will restore to a different destination node but use the original file paths. No routing is required since the Repository and Restore target are connected to the same LAN.
Ensure that any critical data is copied to a safe location or is included in the data set being restored.
The Restore Repository Snapshot Wizard - File System - Select restore options page provides numerous File Name Collision Policy options to help manage potential file overwrite situations.
- From the Restore Repository Snapshot Wizard - File System, choose whether to restore the Entire Snapshot or a User Selection of files. Click Next.
- If restoring a User Selection, select the files and folders to be restored. Click Next.
- Set the Destination Node to the one identified in the previous steps above.
- Set Restore To to Original Location so that the files are placed on the same path as the originals.
- Set File Name Collision Policy to Rename any colliding files so that any existing files of the same name are preserved.
This has no effect when initially creating the restored files in a new location, but if the restore is repeated then it will preserve any existing files from previous restore jobs.
- Review the restore options carefully to ensure that everything has been specified correctly, then click Finish to initiate the restore job.
A Processing message will appear briefly, then the wizard will close and the Jobs Inventory will be displayed. A new Restore Job will appear at the top of the Jobs list, with the Progress entry initially indicating processing and finally indicating successful completion.
- Once the restore process is complete, further steps may be needed to fix-up the data set before using it. In this example we will assume that no additional work is required other than inspecting the restored data on the target machine.
The amount of fix-up work required depends on the applications accessing the restored data.Note: This example restores data created using a Path classification. If you are backing up one of the application types directly supported by Protector, then you should use one of the Application classifications and refer to the appropriate Application Guide listed in Related documents).
- Restart any applications that access the restored data.
For supported applications, these additional steps are described in the appropriate Application Guide (see Related documents). For other applications, consult the vendor's documentation.
- Resume any backup policies for the restored data set. If you have restored data to a new location for repurposing (test and development work for example), you should consider if it is necessary to implement a new backup policy to protect this new instance.
Data flows can be reactivated via the Data Flows Inventory.