Performing restore operations
There are two available ways to restore your data using vRanger.
To perform restore operations, complete one of the following procedures:
Use the following steps to export a previously captured vRanger repository from tape.
On the Create Restore Job — Choose Saveset page, the saveset table provides a list of available savesets. The table shows the saveset name (Job Title and Saveset ID), creation date and time, and saveset size.
|On the Create Selection Set
page, select the archive, for example, vRanger_Sweep_to_Tape, that you want to restore, and click Next
This step restores the entire vRanger repository.
|On the Create Restore Job
page, specify a name for the job.
Assign a descriptive name that lets you easily identify the job when monitoring its progress or restoring data. The job name can contain alphanumeric and non-alphanumeric characters, but it cannot contain non-Latin characters. There is no length restriction; however, a maximum of 40 characters is recommended.
|In the Target Client
list, location to restore the file set from the list of available machines.
|In the Schedule
list, use the default, Immediate
, to run the job when it is submitted.
|In the Source Options
list, select the media from which to restore the archive.
to run the job.
You can monitor the job progress from the Job Status page and view the logs from the View Logs page.
The following steps detail the process of restoring data from a vRanger repository.
vRanger provides options to restore the complete VM, or individual files or folders.
A list of protected VMs display.
A file structure view of the selected VM appears.
to start the recovery, which extracts the files from the vRanger repository for immediate access.
After recovery is complete, you have access to the newly restored files.
Using deduplication with Quest NetVault SmartDisk and vRanger
NetVault SmartDisk delivers data de-duplication that significantly reduces storage costs. With powerful, byte-level, variable block de-duplication, and advanced data compression that packs more protected data in the same storage area than competing solutions, you can reduce your disk backup storage footprint by up to 90%.
vRanger versions 5.3 and later support the use of a NetVault SmartDisk server as a repository. Simply by adding a NetVault SmartDisk server to vRanger as a repository, backups written to that repository are automatically de-duplicated.
For more information about integrating vRanger and NetVault SmartDisk, see the Quest vRanger Integration Guide for Quest NetVault SmartDisk.
Using Data Domain and vRanger repositories
vRanger and EMC® Data Domain® appliances provide a simple and efficient method for backing up and recovering VMware® environments. vRanger provides significant enhancements regarding architecture, performance, and communications over traditional backup solutions. Data Domain provides superior data de-duplication capabilities. The combination of vRanger and Data Domain Technology dramatically reduces your backup and recovery time for VMs on VMware® ESXi™ hosts.
For more information about integrating vRanger and Data Domain, see the Quest vRanger Integration Guide for EMC® Data Domain® Boost (DD Boost™).
vRanger can be configured to log events to the Windows® Event Viewer on the vRanger machine. These events can be filtered and monitored using the Microsoft System Center Operations Manager to monitor replication functions in line with other IT operations. When monitoring is enabled, vRanger creates a vRanger Service node on the local Event Viewer.
The events currently monitored and logged by vRanger include:
Replication task failure: logged as an error, event ID 10001
VA not powered on: logged as an error, event ID 11001
VA connection failure: logged as an error, event ID 11002
VA credential failure: logged as an error, event ID 11003
VA unknown failure: logged as an error, event ID 11999
VA return to normal: logged as an Information event, ID 11998
Datastore threshold exceeded: logged as an error, event ID 12000
Datastore unknown failure: logged as an error, event ID 12099
Datastore return to normal: logged as an Information event, ID 12098