Chat now 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

The VA scratch disk

Previous Next



vzmap files: Block maps — in the form of a vzmap file — for the VMs replicated to the destination host. This file contains block map information, and not actual data blocks. These maps are compared to the source VM during each replication to identify the data blocks that have changed since the last replication. The vzmap files make differential replication faster as they remove the need to scan the destination VM blocks for comparison with the source VM.
vzUndo files: As data is sent to the destination host, by using the VA, blocks in the destination disk are written to the undo file before they are overwritten by the changed data. If replication fails and an undo becomes necessary, the original destination disk blocks are read from the undo file and written to the destination disk to roll back the failed replication. This process is a key function designed to provide resiliency in the face of a network failure; if there is a network failure during the replication pass, the destination VM is not corrupted by incomplete data.
While the vzmap files are trivial in size, in the order of a few MB, the undo file can potentially be as large as the VM itself. While the scratch disk needs to be configured to a size sufficient to handle the data of concurrent replication tasks, making it too large wastes valuable storage space. Use the following topics to guide you in determining the proper size for the scratch disk.
The scratch disk needs to be large enough only to hold the permanent vzmap files and the temporary vzUndo files, plus a small margin for safety. How large that is depends almost entirely on the amount of changed data you are replicating. The amount of changed data is itself a function of the number of VMs you are replicating, their total disk size, replication frequency, and the data change rate per VM. It is important to understand all this data when sizing the scratch disk.

Deploying the VA by using the Virtual Appliance Deployment Wizard

Previous Next


Configuring vRanger > Supplemental instructions: additional repository types > Deploying the VA by using the Virtual Appliance Deployment Wizard

vRanger uses a virtual appliance (VA) for replication to and from VMware® ESXi™ hosts, for FLR from Linux® machines, and optionally for backups and restores. The VA Deployment Wizard offers a simple method to deploy VAs one at a time. You can run the wizard for each VA that you need to deploy, or alternatively deploy multiple VAs at once as described in About deploying multiple VAs.
In the Tools menu, click Virtual Appliance Deployment Wizard.
In the My Inventory view, right-click the host to which the VA should be deployed, and click Deploy Virtual Appliance.
In the Virtual Appliance Configuration node of the Configuration Options dialog box, click Deploy Virtual Appliance.
2
When the Virtual Appliance Deployment Wizard appears, click Next.
1
Select Deploy VA on Cluster.
3
Select Deploy VA on specific host.
5
Click Next.
In the VA Deployment Options dialog box, you can configure the VA’s name and allocated resources. Also, you can configure the size of the VA’s scratch disk. For more information, see The VA scratch disk.
1
In the Virtual Appliance Properties section, confirm the VA Name — edit as required.
2
In the Virtual Appliance Option section, configure the resources allocated to the VA.
Minimum Required: 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.
Quest Recommended (with RDA repository): This setting allocates four CPUs and 2 GB of RAM. This entry is sufficient for running tasks going to RDA repositories.
Custom Setting: Select this value to configure the VA with higher resources for five or more concurrent tasks per VA.
3
In the VA Datastore field, select the datastore for the VA’s primary disk.
4
In the Network Assignment field, select the network for the VA’s primary NIC.
Select Use this virtual appliance for replication and configure the scratch disk size and datastore location. Use the information in Strategies for sizing the scratch disk to guide you.
In the VA Password and Confirm password field, enter a new password for the VA. If you change the password, this password becomes the default for subsequent VA deployments performed during this session.
7
If you want to perform FLR from backups of Linux® VMs, configure a VA to use for Linux FLR.
Select Use virtual appliance for Linux File Level Restore.
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.
1
2
[Optional] Select the option to Power on the VA after deployment is complete, and then see Creating 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



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.

Changing the VA configuration

Previous Next



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.
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.
関連ドキュメント