vRanger 7.7 - Integration Guide for DR Series Disk Backup Appliance

Additional requirement for repository replication

Additional requirement for repository replication

If you set up repository replication, increase the Task Timeout setting beyond the default 24 hours for the initial synchronization. If the initial synchronization involves the transfer of many terabytes of data, you might need to increase the task timeout to over a hundred hours.

1	On the Main toolbar, click Tools > Options.

2	Under the My Jobs node, click Configuration.

3	In the Timeout section, change the Task Timeout field to 100 or more, depending on the size of the environment.

After the initial synchronization of the repositories is finished, you can update this field to an appropriate number.

4

Click OK.

Supported operating systems for installation

Supported operating systems for installation

The following operating systems are supported for installation of vRanger.

 

Table 4. Supported operating systems

Operating system	Service pack level	Bit level
Windows Server 2008 R212	SP1 or later	x64
Windows Server 2012b	All service packs	x64
Windows Server 2012 R2b3	All service packs	x64
Windows Server 2016b	All service packs	x64

---

1

Windows 2008 R2 SP1 requires Windows Management Framework 3.0. Refer to Known Issue VR-177 in the vRanger Release Notes for more information.

2

The Windows Storage Server edition is not supported as an installation platform for vRanger.

3

Before installing vRanger on Windows Server 2012 R2, the updates listed in Additional required software must be installed.

Additional required software

Additional required software

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 2008 R2 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.

▪	File-level restore (FLR) from Linux machines.

▪	Optionally for backups and restores.

•	Updates for Windows Server 2012 R2: Before installing vRanger on Windows Server 2012 R2, ensure that the Windows updates listed below are installed:

▪

KB2939087

▪

KB2975061

▪

KB2919355

▪

KB2999226

Installing vRanger

Installing vRanger

The installation of vRanger has several options. Unless you have a valid reason not to, accept the defaults wherever possible. The installation follows this sequence:

1	Launch the installer, and accept the vRanger license.

The install process does not continue until the license is accepted.

2	Enter the credentials under which the vRanger services should run.

The credentials used need to have local administrator privileges on the vRanger machine.

3	Choose an installation directory.

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.

5	Configure the runtime credentials for the vRanger Database.

6	[Optional] Install the vRanger Catalog Service.

The installation completes.

For more information, see the Quest vRanger Installation/Upgrade Guide.