立即与支持人员聊天
与支持团队交流

vRanger 7.8.5 - User Guide

Introduction vRanger overview Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring an encrypted VMware VM Performing a full restore for VMware VMs Performing a full restore for Hyper-V® VMs Performing a full restore for VMware vApps Performing a full restore of a physical machine Performing an FLR on Windows Performing an FLR on Linux Restoring from manifest
Replicate VMs Reports Integrating and monitoring vRanger Using the vRanger Console vAPI Cmdlet details

Installing vRanger

The installation of vRanger has several options. Unless you have a valid reason not to, Quest recommends that you accept the defaults wherever possible. Complete the steps in the following procedure to install vRanger.

To install vRanger:
1
Start the installer, and accept the vRanger license.
The install process does not continue until the license is accepted.
2
Choose an installation directory.
3
Enter the credentials under which the vRanger services should run.
The credentials used need to have local administrator privileges on the vRanger machine.
4
Select the vRanger database.
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.
The installation completes.

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
•
Adding repositories
•
Deploying virtual appliances (VAs)
•
Adding physical servers to inventory
•
Scheduling a backup job
•
Scheduling a replication job
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.
•
One or more VMware® vCloud Director® servers.
•
One or more physical servers.
•
Individual Hyper-V® or VMware® ESXi™ hosts not associated with a cluster or vCenter.

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.

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.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级