Chat now with support
Chat with Support

vRanger 7.7.1 - User Guide

Introduction Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring a physical server 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
Add-BackupJobTemplate Add-CIFSRepository Add-DdbReplicationRepository Add-DdbRepository Add-EsxHost Add-HypervCluster Add-HypervHost Add-HypervRestoreJobTemplate Add-NFSRepository Add-NVSDRepository Add-PhysicalMachine Add-RdaRepository Add-ReplicationJobTemplate Add-RestoreFromManifestJobTemplate Add-RestoreJobTemplate Add-VirtualAppforLinuxFLR Add-VirtualAppforLinuxFLRVA Add-VirtualCenter Disable-Job Dismount-LinuxVolume Enable-Job Get-AddressBook Get-BackupGroupEntity Get-CatalogSearchData Get-CatalogStatus Get-ConfigOption Get-Connection Get-CurrentTemplateVersionID Get-Datastore Get-GlobalTransportFailover Get-InventoryEntities Get-IsInventoryRefreshing Get-Job Get-JobTemplate Get-MonitorLog Get-Network Get-PhysicalMachineDiskMap Get-Repository Get-RepositoryJob Get-RepositorySavePoint Get-RestoreDiskMap Get-SavepointDisk Get-SavepointManifest Get-Savepoints Get-TransportFailover Get-VirtualApplianceConfig Get-VirtualApplianceDeploymentStatus Get-VirtualApplianceReconfigStatus Get-VirtualMachinesUnderInventory Get-VmDisk Get-VMDKVolume Install-VirtualAppliance Mount-LinuxVolume New-BackupFlag New-BackupGroupMember New-Daily Schedule New-EmailAddress New-IntervalSchedule New-MonthlySchedule New-ReplicationFlag New-RestoreFlag New-SMTPServer New-TransportConfiguration New-VirtualAppliance New-WeeklySchedule New-YearlySchedule Remove-AllMount Remove-BackupGroupEntity Remove-BackupGroupMember Remove-Catalog Remove-DdbStorageUnit Remove-JobTemplate Remove-LinuxVolume Remove-Repository Remove-SavePoint Remove-VirtualAppliance Remove-VirtualApplianceConfiguration Run-JobsNow Run-ReplicationFailover Run-ResumeReplicationFailover Run-TestReplicationFailover Set-Cataloging Set-CBTonVM Set-LinuxVolume Set-MountPath Set-Resources Stop-vRangerJob Update-BackupJobTemplate Update-GlobalTransportFailover Update-HypervRestoreJobTemplate Update-Inventory Update-ReplicationJobTemplate Update-RestoreJobTemplate Update-VirtualAppliance Update-VirtualApplianceConfiguration
About us

Configuring the VA IP address

Previous Next



Configuring the VA IP address

On the VA IP Address Configuration page, you must configure the network configuration for the VA’s primary network interface card (NIC).

To configure the VA IP address:
Use DHCP for IP assignment automatically assigns IP settings to the VA if a DHCP server is available.
Use Static IP lets you deploy the VA with a manual IP configuration.
Obtain the DNS server address automatically uses the DNS settings provided by your DHCP server.
Use the following DNS server address lets you specify DNS settings manually.
3
Click Next.

Confirming VA deployment selections

Previous Next



Confirming VA deployment selections

Complete the steps in the following procedure to confirm the VA deployment options displayed are correct.

To confirm VA deployment selections:
1
2
[Optional] Select the option to Power on the VA after deployment is complete, and then see Creating a template.
Creating a template

Optionally, if you need to deploy the vRanger VA to multiple hosts, it may be helpful to create a VM template from the configured VA.

To create a template:
1
From the VI Client, right-click the configured VA, select Template, and then click Clone to Template.
5
In the Disk Format dialog box, select Same format as source, and click Next.

About deploying multiple VAs

Previous Next



About deploying multiple VAs

The VA must be deployed to any VMware® ESXi™ host that you want to configure for replication — either as a source or a destination. For hosts in a cluster, you may deploy the VA to just one host in the cluster; the VA is shared among the cluster’s hosts.

In addition, replication by way of a VA requires that if a VA is used on one host or cluster in a replication job, a VA must be used on both the source and destination host or cluster. In other words, VAs, when used for replication, must be used in pairs.

For a few VAs, using the vRanger UI to deploy the VAs is sufficient. To streamline the process of deploying a high number of VAs, Quest recommends that you deploy and configure the VA once, and save it as a template to be used for additional deployments using the VMware vSphere® PowerCLI™. The Creating a template procedures include an optional step for creating a template from the configured VA.

Changing the VA configuration

Previous Next



Changing the VA configuration

After a VA is deployed, you may change its configuration from the vRanger UI.

To change the VA configuration:
In the My Inventory view, right-click the VA you want to change, and then click Virtual Appliance Configuration.
a
Click Tools, and then click Options.
b
In the Configuration Options dialog box, select Virtual Appliance.
c
Under Configure Existing Virtual Appliances, select the VA to change, and then click Edit.

The Modify Virtual Appliance Configuration dialog box appears.

2
In the Virtual Appliance Properties section, do the following:
a
Next to VA Name, confirm the name of the VA.
b
Next to IP Address, confirm the IP vRanger uses to connect to the VA.

By default, vRanger connects to the vRanger VA using the first IP address reported by the VMware vSphere® API. This IP is displayed under Virtual Appliance Properties in the IP Address field. If you have only one NIC configured on the VA, continue to the next step.

If you have more than one NIC configured on the VA, you may not want vRanger to connect to the first NIC. Select Override IP Address to configure vRanger with the IP address for the NIC to which vRanger should connect.

For example, if you have two NICs configured on the VA, and want vRanger to connect to the second NIC, select Override IP Address to enable the IP Address field, and then enter the IP for the second NIC in the IP Address field.

3
In the Virtual Appliance Options section, use the Select an option drop-down list to change the resources allocated to the VA as needed.

You may select from one of the following options:

Minimum Requirement: This setting allocates one CPU and 512 MB of RAM. This entry is sufficient for two concurrent tasks per VA.
Quest Recommended: This setting allocates two CPUs and 1 GB of RAM. This entry is sufficient for four concurrent tasks per VA.
Custom Setting: Select this value to configure the VA with your own preferred settings; for example, higher resources for more concurrent tasks per VA.
NOTE: If you are using a VMware® vCenter™ version lower than 5.0, the ability to change the datastore of the VA scratch disk used for replication is not available.

Select Use this virtual appliance for replication and configure the scratch disk size using the up-and-down arrows and the drop-down list. For more information about sizing a scratch disk, see Strategies for sizing the scratch disk.

6
[Optional] Enter a new password for the VA in the VA Password field, and then re-enter it in the Confirm password field.
7
If you want to perform FLR from backups of Linux® VMs, select Use virtual appliance for Linux File Level Restore to configure a VA to use for Linux FLR.

If you select this option for a different VA in the future, that VA is used for Linux FLR.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating