지금 지원 담당자와 채팅
지원 담당자와 채팅

vRanger 7.6.3 - 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

Replication modes

Previous Next


Replicate VMs > Replication modes

Replication modes

vRanger offers Replication with Changed Block Tracking (CBT) or standard Differential replication. Each of these replication modes has the option of ABM. VM replication in general starts with replicating the source VM to the target host. Changes are applied to the target VM at user designated intervals to keep the target in sync with the source. Thus the key difference between the replication modes is how vRanger identifies VM changes to replicate. For more information, see the following topics:

Replication with Changed Block Tracking (CBT)

Previous Next


Replicate VMs > Replication modes > Replication with Changed Block Tracking (CBT)

Replication with Changed Block Tracking (CBT)

Replication with CBT is the recommended method of replication whenever possible.

CBT tracks the disk block changes made by the source VM. When enabled on the source host, CBT records the blocks that have changed since the last replication pass and transfers them to the target host without scanning the VMDK. CBT only identifies these disk-sector changes when VMware® ESXi™ version 5.0 or later is installed on both of the hosts being used for replication.

The following configurations are required for CBT to be available:

For CBT to identify disk sectors in use with the special change ID, the following configurations are also required:

NOTE: CBT must be enabled for each VM that you want to replicate. VMware vSphere® supports CBT, and most VMs running in this environment can use it.

Differential replication

Previous Next


Replicate VMs > Replication modes > Differential replication

Differential replication

In differential replication, vRanger compares the data blocks on the source VM to a data map to identify blocks that have changed since the last replication pass. These changed blocks are sent to the target VM and committed to disk, and the data map is updated to reflect the current state of both VMs.

When using differential replication, consider the following:

Configuring transport failover options

Previous Next


Replicate VMs > Replication modes > Configuring transport failover options

Configuring transport failover options

Replication transport actions occur through HotAdd — LAN-free or network. If one transport method is not available, vRanger attempts to perform the replication task using one of the other transport methods. You may configure the order in which vRanger attempts the transport options with the Transport Failover node of the Configuration Options page. For VMware® ESXi™ hosts, configure the transport order to VA-based HotAdd > VA-based Network.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택