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

Performing Test Failover with networking disabled

Previous Next


Replicate VMs > Using replication failover > Performing Test Failover with networking disabled

Performing Test Failover with networking disabled

The Test Failover operation can be performed from the Scheduled Jobs and On Demand Jobs nodes of the My Jobs view.

The following describes the default Test Failover operation. To perform a test failover with networking enabled, see Performing Test Failover with networking enabled.

To perform test failure with networking disabled:
1
Click the Test Failover icon.

The test failover process begins, and a job is added to the Current Jobs node.

3
When testing is complete, select the Test Failover task in the Current Jobs node, and click Resume.

The snapshots made are reverted.

The network card is “Connect at Power On,” which prepares the replica VM for failover.

The VM returns to its dormant state.

Performing Test Failover with networking enabled

Previous Next


Replicate VMs > Using replication failover > Performing Test Failover with networking enabled

Performing Test Failover with networking enabled

Performing a test failover with the network enabled has the potential to negatively affect your production environment. For this reason, this method of test failover is not recommended. The recommended method is Performing Test Failover with networking disabled.

To perform network-enabled test failover, complete the following tasks:

Enabling network-enabled Test Failover

Previous Next



Enabling network-enabled Test Failover

This feature is enabled by way of the configuration file for the vRanger client, Vizioncore.vRanger.Client.Shell.exe.config. This file is located in the vRanger installation directory. The default is C:\Program Files\Quest\vRanger.

To enable network-enabled test failover:
1
Open the Vizioncore.vRanger.Client.Shell.exe.config file with your text editor of choice.
4
Change the value for ShowTestFailoverDialog from “false” to “true”, ensuring the quotation marks remain.

Performing a network-enabled Test Failover

Previous Next



Performing a network-enabled Test Failover

After it is enabled, you are prompted to perform a test failover; you can do so with or without networking enabled during the test.

To perform a test failover:
1
Click the Test Failover icon.
Continue with networking on the replica disabled: When performing a test failover with networking disabled, the replica VM is powered on with the network adapter disconnected. This option protects the production environment, but eliminates the ability of testing your replica VM as part of a larger environment.
Continue with networking on the replica enabled: When performing a network enabled test failover, your replica VM is powered on with the network adaptor connected.
3
4
When testing is complete, select the Test Failover task in the Current Jobs node, and click Resume.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating