Chatta subito con l'assistenza
Chat con il supporto

vRanger 7.6.6 - Integration Guide for EMC Data Domain Boost (DD Boost)

Supported operating systems for installation

Previous Next


Installing vRanger > Hardware requirements > Supported operating systems for installation

Supported operating systems for installation

The following operating systems are supported for installation of vRanger.

Table 3. 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

2

3

Additional required software

Previous Next


Installing vRanger > Hardware requirements > Supported operating systems for installation > 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:
Updates for Windows Server 2012 R2: Before installing vRanger on Windows Server 2012 R2, ensure that the Windows updates listed below are installed:

Installing vRanger

Previous Next


Installing vRanger > Installing vRanger

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. The installation follows this sequence:

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

Use credentials that 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.

The installation completes.

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

Configuring vRanger

Previous Next


Installing vRanger > Configuring vRanger

Configuring vRanger

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 topics describe the primary configurations you need to make.

Adding vCenters or hosts: Before you can begin backups, you must add one or more VMware® vCenter™ or ESXi™ servers to the vRanger inventory. To add a vCenter, you must have credentials with Administrator access to the vCenter, along with root-level credentials for each host managed by the vCenter. vRanger provides the option to 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. For the purposes of this integration, an EMC® Data Domain® Boost (DD Boost™) repository should be used.

The DD Boost server must be fully configured and running before adding it as a vRanger Repository. For procedures on how to add a DD Boost server as a repository, see Managing repository replication.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione