Chat now with support
Chat with Support

vRanger 7.8 - User Guide

Introduction Configuring vRanger
Configuration overview Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore Replicate VMs Reports Integrating and monitoring vRanger Using the vRanger Console vAPI Cmdlet details
Add-BackupGroupEntity 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-InventoryEntity 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

Adding Hyper-V System Center VMM, cluster, and host information

Previous Next


Configuring vRanger > Configuring vRanger through the Startup Wizard > Adding Hyper-V System Center VMM, cluster, and host information
The Hyper-V Cluster and Host Information page of the Startup Wizard appears. Before vRanger can add source objects to the My Inventory pane, you must configure a connection to a Hyper-V® System Center Virtual Machine Manager (VMM), cluster, or host.
To add a Hyper-V System Center VMM, cluster, or host, complete the following tasks as necessary:
•
Adding a Hyper-V System Center VMM
•
Adding a Hyper-V cluster
•
Adding hosts
Adding a Hyper-V System Center VMM
Complete the steps in the following procedure to add a Hyper-V® System Center VMM.
 
 
IMPORTANT: Before adding the System Center VMM connection, you must install the System Center VMM Administrator Console on the vRanger machine.
IMPORTANT: Only one version of the SCVMM Console may be installed on the vRanger machine. vRanger does not support simultaneous operations against two different versions of SCVMM from the same vRanger machine.
To add a Hyper-V System Center VMM:
1
In the Hyper-V System Center Virtual Machine Managers section, click Add.
2
In the DNS Name or IP field, enter the FQDN or IP address of the Hyper-V System Center VMM.
3
In the User Name field, enter the name of an account with domain administrator privileges on the System Center VMM.
4
In the User Password field, enter the password for the preceding account.
5
If this VMM is a new System Center VMM, or if you have removed the vRanger Hyper-V agent, select Install agent on host.
6
Configure the ports as follows:
▪
In the Agent Port Number field, enter the port you want vRanger to use to communicate with the vRanger agent installed on each Hyper-V host. This port must be open between vRanger and each Hyper-V server — the default is 8081.
▪
In the SCVMM Port Number field, enter the port you want vRanger to use to communicate with the System Center VMM server — the default is 8100. Click Connect.
 
 
IMPORTANT: This port is configured during System Center VMM installation. If you chose a port number different from the default, enter that value here.
7
Click Next.
The Hyper-V System Center VMM appears in the Hyper-V System Center Virtual Machine Managers section. The hosts managed by that VMM appear in the Hosts section.
Adding a Hyper-V cluster
Complete the steps in the following procedure to add a Hyper-V® cluster.
To add a Hyper-V cluster:
1
In the Hyper-V Cluster section, click Add.
2
In the DNS Name or IP field, enter the FQDN or IP address of the Hyper-V cluster.
3
In the User Name field, enter the name of an account with domain administrator privileges on the cluster.
4
In the User Password field, enter the password for the preceding account.
5
If this cluster is new, or if you have removed the vRanger Hyper-V agent, select Install agent on host.
6
In the Port Number field, enter the preferred port you want vRanger to use to communicate with the Hyper-V cluster on the source server.
This port must be open between vRanger and each Hyper-V server — the default is 8081.
7
Click Connect.
8
Click Next.
The Hyper-V cluster appears in the Hyper-V Clusters section. The hosts managed by that cluster appear in the Hosts section.
Adding hosts
If you have hosts that are not part of a cluster, you can add them individually.
To add hosts:
1
In the Hosts section, click Add.
2
In the DNS Name or IP field, enter the FQDN or IP address of the Host.
3
In the User Name field, enter an account for the host.
4
In the User Password field, enter the password for the preceding account.
5
If this host is new, or if you have removed the vRanger Hyper-V® agent, select Install agent on host.
6
In the Port Number field, enter the preferred port you want vRanger to use to communicate with the Hyper-V host on the source server.
This port must be open between vRanger and each Hyper-V server — the default is 8081.
7
Click Connect.
The host appears in the Hosts section.

Selecting hosts for licenses

Previous Next


Configuring vRanger > Configuring vRanger through the Startup Wizard > Selecting hosts for licenses
The Host Licensing Information page appears. It displays total licensed sockets, used sockets, and the remaining days left in a trial period.
 
 
NOTE: VM licenses include all VMs. Licenses for both VMware® and Hyper-V® VMs are drawn from the same socket count.
To select hosts for licenses:
1
View the CPUs Allowed value to confirm the number of sockets that are licensed for protection.
The number of licenses currently allocated is shown in the CPUs Used column.
The Licensed Hosts section lists the managed hosts, the number of sockets for each host, and the licensed features for that host.
The CPUs column indicates the license “cost” of each host.
2
In the Backup or Replication column, select or clear hosts until you have used all the available licenses, or until all your hosts are protected.
3
Click Save.
4
Click Next.

Adding a physical machine

Previous Next


Configuring vRanger > Configuring vRanger through the Startup Wizard > Adding a physical machine
The Physical Machine Information page appears. Before vRanger can add physical source objects to the My Inventory pane, you must configure a connection to a physical server.
To add a physical machine:
1
In the Physical Machines section, click Add.
2
In the DNS Name or IP field, enter the FQDN or IP address of the server.
3
In the User Name field, enter an account for the server.
4
In the User Password field, enter the password for the preceding account.
5
If this server is new, or if you have removed the vRanger agent, select Install agent on machine.
In the Agent Location field, enter the preferred directory — on the physical machine — to which the physical client should be installed. The default is C:\Program Files\Dell\vRangerPhysicalClient.
6
In the Port Number field, enter the preferred port for vRanger to use to communicate with the physical client on the source server.
This port must be open between vRanger and each physical server — the default is 51000.
7
Click Connect.
The server appears in the My Inventory pane. You may also create a backup group to combine multiple physical servers into one backup job. For more information, see Adding a custom backup group.

Selecting physical machines for licenses

Previous Next


Configuring vRanger > Configuring vRanger through the Startup Wizard > Selecting physical machines for licenses
Before you start this process, make sure that you have imported the license file and confirmed that it is adequate for managing the number of physical machines you want to protect. The Currently Installed Licenses section includes the total number of physical machine licenses available, and the number being used currently. These numbers increment and decrement based on the selections you make on this page.
To select physical machines for licenses:
1
In the Currently Installed Licenses section, view the Machines Allowed value to confirm the total number of physical machines licenses available.
The number of licenses currently allocated is shown in the Machines Used column. The Licensed Physical Machine section lists the physical machines in the vRanger inventory, and indicates whether each machine is licensed for backup.
2
In the Physical Backup column, select or clear machines until you have used all the available licenses, or until all your machines are protected.
3
Click OK.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating