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

Configuring email notifications

Previous Next


Replicate VMs > Creating a replication job > Configuring email notifications
The Email Notification Selection page lets you select the email addresses to which notifications should be sent for this job. You can also request that a report be sent to the recipients identified after the job is complete.
To add or edit email addresses, see Setting up the SMTP server.
To configure email notifications:
1
On the Email Notification Selection page, in the Selected column, select the address to which notifications should be sent.
 
 
TIP: To select all email addresses, select the check box in the Selected column header.
2
Click Next.

Starting the replication job

Previous Next


Replicate VMs > Creating a replication job > Starting the replication job
The final page in the Replication Wizard displays a summary of the selections you made for the job.
 
 
NOTE: The most common configuration error is configuring a Transport Failover sequence that does not match your hardware. For example, if you have VA-HotAdd selected in the Transport Failover section, but one of your hosts does not have a VA configured.
To start the replication job:
1
On the Summary page, review the data displayed in the tree view.
2
If you want to begin the job automatically after completing the wizard, select Run the Job after Finish is clicked.
 
 
NOTE: If this option is not selected, the job is saved and begins at the time determined during the Setting the Recurrence Schedule procedure.
3
Click Finish.
4
If you did not opt to begin the job automatically after clicking Finish, and this job is an on-demand job, do the following:
 
 
NOTE: If this job is not an on-demand job, the job begins at the scheduled time.
a
In the main vRanger UI, in the My Inventory view, select the server or host for the server you want to restore, and then select the job from the Working Inventory pane.
b
On the View toolbar, click Run.
c
In the Confirm Run Job dialog box, click Yes.
5
To check progress or confirm completion, click My Jobs, and then click Recent Jobs.

Using replication failover

Previous Next


Replicate VMs > Using replication failover
There are two kinds of replication Failover: Test Failover and Failover.
•
Test Failover: This function disables the replication job, snapshots the replica VM, and powers it on. You have the option of performing a test failover with or without networking enabled on the replica VM. There are two methods for performing failure:
▪
Performing Test Failover with networking disabled
▪
Performing Test Failover with networking enabled
•
Failover: This method simplifies the action of failover to a replica VM. You can perform a final synchronization or fail over immediately. The vReplicator process gracefully and safely powers down your production VM, and boots your replica VM with a single click.

Performing Test Failover with networking disabled

Previous Next


Replicate VMs > Using replication failover > 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.
2
When the confirmation message appears, click Yes.
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.
4
When the confirmation message appears, click Yes.
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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating