サポートと今すぐチャット
サポートとのチャット

vRanger 7.8.5 - User Guide

Introduction vRanger overview Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring an encrypted VMware VM 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

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.

 
* 
NOTE: When using the Full Backup Days option, ensure that the selected recurrence schedule causes backup tasks to run on the configured Full Backup Days.
To set the recurrence schedule:
1
On the Recurrence Schedule Selection page, select from the options described in the following table.
 
* 
NOTE: To replicate more frequently than once per day, use the Interval recurrence pattern.
 

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.
NOTE: Configure a value sufficient to let the previous replication pass to continue.

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.
 
* 
TIP: To select all email addresses, select the check box in the Selected column header.
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.

 
* 
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

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

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.

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.

 
* 
NOTE: Due to this option’s potential for negatively impacting your production environment, it is disabled by default.

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

•
Enabling network-enabled Test Failover
•
Performing a network-enabled Test Failover
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択