vRanger requires some basic configuration before data protection can begin. The bulk of this configuration is driven by the Startup Wizard which starts the first time the application is opened. For more information, see Configuring vRanger.
The following topics describe the primary configurations you need to make.
Before you can begin backups, you must add at least one of the following to the vRanger inventory:
To add a vCenter, you need to have credentials with administrator access to the vCenter, along with root-level credentials for each host managed by the vCenter. To add a Hyper-V cluster, you must have domain administrator privileges. You can exclude hosts from the vRanger inventory, which also excludes them from licensing.
Repositories are where vRanger stores the savepoints created by each backup job. You can create a repository from a standard Network File System (NFS)or Common Internet File System (CIFS). You may also deduplicate vRanger backups by sending them to a Quest DR RDA, EMC® Data Domain® (DD Boost™), or Quest NetVault SmartDisk repository. To add a repository, you need the name of the server and share, and an account with access to that share. If you are using Quest RDA or DD Boost repositories, you can also set up repository replication with another repository of the same type. For more information on replication, see Managing repository replication.
Deploying virtual appliances (VAs)
vRanger uses a VA for replication to and from VMware® ESXi™ servers, for Linux® FLR, and optionally for backups and restores. Before fully utilizing vRanger, you need to deploy and configure VAs to your ESXi servers. For more information, see the Quest vRanger Installation/Upgrade Guide.
Adding physical servers to inventory
vRanger includes the ability to back up and restore physical servers. Before you can back up a physical server, you must add it to the vRanger inventory and supply credentials with Administrator access to the server.