The vRanger VA can process backup and restore tasks in addition to replication tasks. This setup allows you to scale backup, restore, and replication activity across multiple hosts or clusters, while maintaining central scheduling and reporting control from a single vRanger server.While the deployment and configuration of the VA are covered in the Quest vRanger User’s Guide, the following information might help you understand the usage of the VA.
The vRanger VA can be used to perform the following operations. For each of these operations, the processing activity occurs on the VA.
• Linux® file-level restore
The locations to which the vRanger VA or VAs should be deployed depend on the specifics of the virtual environment in question. Some general guidelines for VA deployment are:
• You must have a VA deployed on any VMware® ESXi™ host or cluster that is used for replication and backup. This requirement is true regardless of whether the host or cluster is used as the source or target of the replication task.
NOTE: The vRanger VA is now bundled with vRanger, and can be found in: C:\Program Files\Quest\vRanger
Designed for ease-of-use in recovery operations, repositories eliminate the need for countless backup locations and endless configurations. With vRanger, you can configure a repository once, and use it forever.
• EMC® Data Domain® Boost (DD Boost™)A repository is essentially a directory on a supported file system that vRanger uses to store savepoints — backup archives. When viewed from outside vRanger, through Windows® Explorer, for example, a repository consists of a configuration file — GlobalManifest.metadata — and directories for each savepoint.Any time you add a repository in vRanger a GlobalManifest.Metadata XML file is created in the selected folder. It is the presence of that manifest file that tells vRanger that a repository exists in that folder.