In addition to a supported version of Windows® and a supported VMware® Infrastructure, you may need some additional software components, depending on your configuration.
• |
Microsoft® .NET Framework: vRanger requires the .NET Framework 4.5. The vRanger installer installs it if not detected. |
• |
SQL Server: [Optional] vRanger utilizes two SQL Server® databases for application functionality. vRanger can install a local version of SQL Express 2014 SP3 or you can choose to install the vRanger databases on your own SQL instance. |
• |
Windows PowerShell 3 or above.If you are installing vRanger on Windows 2008 R2 SP1, you will need to install Windows PowerShell 3 or above before installing vRanger |
• |
vRanger virtual appliance (VA): The vRanger VA is a small, pre-packaged Linux® distribution that serves as a platform for vRanger operations away from the vRanger server. vRanger uses the VA for the following functions: |
• |
Replication to and from VMware® ESXi™ hosts. |
• |
Updates for Windows Server 2012 R2: Before installing vRanger on Windows Server 2012 R2, ensure that the Windows updates listed below are installed: |
For more information, see the Quest vRanger Installation/Upgrade Guide.
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 the Quest vRanger Installation/Upgrade Guide.
The following lists the primary configurations you need to make.
• |
Add source servers: Before you can begin backups, you must add one or more source objects to the vRanger inventory. Source objects can include VMware® vCenter™ or ESXi™ hosts, Hyper-V® clusters or hosts, or physical machines. |
• |
Add vRanger virtual appliances (VAs): vRanger VAs allow you to distribute the backup workload and gain direct access to target VM’s storage for improved performance. |
• |
Add repositories: Repositories are where vRanger stores the savepoints created by each backup job. For the purposes of this integration, a Quest Rapid Data Access (RDA) repository should be used. |
For more information about QoreStor, see the QoreStor documentation at support.quest.com/qorestor.
• |
• |
• |
• |
• |
1 |
2 |
In the Add Quest Rapid Access Repository dialog box, complete the following fields: |
• |
Repository Name: Enter a descriptive name for the repository. |
• |
Description: [Optional] Enter a long-form description for the repository. |
• |
DNS Name or IP: Enter the DNS name or IP address of the QoreStor server. |
• |
RDA Username: Enter a user account that can be used to log in to the device. The default account is backup_user. |
• |
• |
Logical Storage Unit: Enter the name of the storage container. Ensure that the container is created before you add the device. You cannot add the device if the specified container does not exist on the device. When creating the storage container, use the options: |
• |
Port Number: Leave this value at 0 to use the default. |
3 |
Click OK. |
• |
Import as Read-Only: To import all savepoint data into the vRanger database, but only for restores, click this button. You cannot back up data to this repository. |
• |
Import: To import all savepoint data into the vRanger database, click this button. vRanger is able to use the repository for backups and restores. vRanger requires read and write access to the directory. |
• |
Overwrite: To retain the savepoint data on the disk and not import it into vRanger, click this button. vRanger ignores the existence of the existing savepoint data and treats the repository as new. |
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center