Installing vRanger
To install vRanger:
The install process does not continue until the license is accepted.
The credentials used need to have local administrator privileges on the vRanger machine.
You may choose to install vRanger with a new instance of SQL Server® Express or on an existing SQL Server. You also need to configure DB credentials now.
For more information, see the Quest vRanger Installation/Upgrade Guide.
Configuration overview
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.
Adding inventory for protection
Before you can begin backups, you must add at least one of the following to the vRanger inventory:
• One or more VMware® vCenter Servers™.
• One or more Hyper-V® clusters.
•
•
Adding repositories
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.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center