Chat now with support
Chat mit Support

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

Pre-seeding replication jobs

Previous Next


Replicate VMs > Replication modes > Pre-seeding replication jobs

Pre-seeding replication jobs

vRanger replication is intended to replicate changes from a source VM to a remote target. It is often not practical to perform the first replication pass — which sends the full VM) to a remote site over a WAN link. You may use vRanger to “seed” a replication job locally to reduce the amount of data sent over the WAN.

To pre-seed replication jobs, complete the following tasks:

Backing up the source VM

Complete the steps in the following procedure to back up the source VM.

To back up the source VM:

You can complete this step by shipping a USB drive or some other media containing the backup archive.

Savepoints are named using a VMname_date_time_UUID format. Copy the entire directory, which contains a .var file and two .metadata files, for the savepoint in question.

5
Using the Restore from Manifest function documented in Performing a full restore from manifest for VMware VMs, restore the backup to the target VMware® ESXi™ Server at the DR site.

Replicating the changes

Complete the steps in the following procedure to replicate the changes made to the VM.

To replicate the changes:
2
5
In the Select Target Host dialog box, next to Preseed VM UUID, click the browse button, and select the pre-seeded VM.

Only the data changes pass over the WAN as opposed to the full VM.

Creating a replication job

Previous Next


Replicate VMs > Creating a replication job

Creating a replication job

vRanger uses a simple wizard to guide you through the process of creating a replication job. At a high level, the process includes the following steps. Each of the steps is explained in more detail in the topics that follow.

To create a replication job, complete the following tasks:

Selecting the source VM

Complete the steps in the following procedure to select the source VM.

To select the source VM:
1
Click My Inventory.
3
Enter the Job Name and Job Description, and click Next.

Selecting a target host

On the Select Target Host page, complete the following steps to select a target host.

To select a target host:
Choose a Target Host from the list, and click Next.
If you have pre-seeded the VM on the target host, select the host on the target side to which the source VM has been restored. For more information, see Pre-seeding replication jobs. When selecting the target VM name, ensure that you are using the same name as the source VM. vRanger appends “_VzReplicate” to the VM name on the target side.
2
[Optional] In the Select Target Host dialog box, next to Preseed VM UUID, click the browse button, and select the pre-seeded VM.
IMPORTANT: After a replication job has been saved, you cannot change the target host. If you want to replicate to a different host, you may either use VMware vSphere® vMotion® to migrate the VM to the preferred host, or create a replication job for the preferred target. If you vMotion the VM, the existing replication job should identify the change in host and adjust automatically.

Selecting the replication mode

On the Replication Mode page, you can select between differential replication and hybrid replication. For more information, see Replication modes.

To select the replication mode:
1
On the Replication Mode page, under Replication Type, select Differential Replication.
NOTE: Hybrid replication is not supported when replicating to or from VMware® ESXi™. This feature is deprecated for vRanger 7.2 and later.
2
Click Next.

Selecting replication network mapping

On the Replication Network Mapping page, you specify the network on the target host to which the VM nics should connect.

To select replication network mapping:
1
Select the Network Mapping you want to use for this job.
2
Click Next.

Selecting hard disks

The Select which Hard Disk(s) to replicate page lets you include or exclude specific disks from replication.

To select hard disks:

You may select a Primary Datastore, which is used as the default for all disks in this job, letting you configure only the exceptions.

2
In the Target Datastore column, verify that the Primary Datastore has been populated.
4
On the Select Primary Storage page, review the list of datastores.

This page lists all datastores associated with the selected host. Datastores are first grouped based on whether they are governed by a storage policy. Datastores are also grouped based on whether they reside in a DRS cluster. You can expand or collapse groups as needed.

6
When the Select which Hard Disk(s) to replicate page appears, click Next.

Selecting replication options

The Replication Options page lets you configure additional operations performed during the replication job. You may also view the transport failover preferences, and modify them as needed.

To select replication options:

Option

Description

Check destination for free space.

This option prompts vRanger to check the destination location to ensure that there is enough space available for the replica VM.

Update notes with latest replication results.

If this flag is selected, vRanger updates the VM Notes in VC with the most recent replication task status.

NOTE: vRanger maintains the existing VM notes in VMware® vCenter™, appending the replication status to the end.

Enable guest quiescing.

This option enables the VMware® Tools when creating a snapshot. Use this flag if you are replicating a database server. During this process, vRanger freezes or pauses writes on supported applications to provide a consistent image of VSS-enabled databases. For more information, see Physical backup transport options.

Enable Active Block Mapping (ABM).

Selecting this option enables ABM, which lets vRanger skip data that recognized as removed on Windows® NTFS — including junk data in recycle bin.

The following ABM settings options are also available:

If you want to change the Transport Failover order, click Modify. For more information, see Configuring transport failover options.

3
Click Next.

Setting the recurrence schedule

Previous Next


Replicate VMs > Creating a replication job > Setting the recurrence schedule

Setting the recurrence schedule

The Recurrence Schedule Selection page lets you indicate whether the job should be done on demand — at this moment — or at a future time. To schedule a future occurrence, you must define the start time, recurrence pattern, and range of recurrence.

To set the recurrence schedule:
1
On the Recurrence Schedule Selection page, select from the options described in the following table.

This will be an On Demand job…

There is no need to define a schedule. The job runs on demand.

Start Time

The time of day at which to run the job.

Recurrence Pattern

In this section, you establish how often the report should be generated. There are five options within this section:

Daily: The daily option can be scheduled to run the report every weekday or every x number of days.
Weekly: vRanger can be configured to run on weekly intervals, from every week to every 99 weeks. The day of the week on which to run reports can be configured.
Monthly: The monthly option offers the following configurations:
Day [x] of every [y] month:

x can be any value from 1 to 31. This value determines the day of the month on which the job occurs.

y can be any value from 1 to 99. This value determines the monthly interval — for example, every two months sets the job to run every other month.

The [f] [d] of every [y] month(s):

f can be either: first, second, third, fourth or last.

d can be: weekday, weekend day, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

y can be any value from 1 to 99. This value determines the monthly interval — for example, every two months sets the report to run every other month.

Yearly: The yearly option offers the following configurations:
Every [m] [x]:

m is any month of the year. This value determines the month of the year in which the report occurs.

x can be any value from 1 to 31. This value determines the day of the month on which the report occurs.

The [f] [d] of [m]:

f can be either: first, second, third, fourth, or last.

d can be: day, weekday, weekend day, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

m is any month of the year. This value determines the month of the year in which the report occurs.

Interval: The Interval option offers the following configurations:
Day(s). The default is 0, which lets you replicate more frequently than daily.
Hour(s). The default is 1. To replicate more frequently, change to 0 and configure a Minute(s) value.
Minute(s). The default is 0. The minimum interval is five minutes.

Range of Recurrence

Select the starting date and ending date.

No end date: The job recurs until it is stopped.
End after: Select the number of occurrences.
End by: Select the date by which to end the recurrence.
2
Click Next.

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.
2
Click Next.

Starting the replication job

The final page in the Replication Wizard displays a summary of the selections you made for the job.

To start the replication job:
1
On the Summary page, review the data displayed in the tree view.
3
Click Finish.
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.
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

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:
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.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen