Chat now with support
Chat with Support

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

Booting into the restore environment using static IP

Complete the steps in the following procedure to boot into the vRanger restore environment using a static IP address.

To boot into the restore environment using static IP:
1
Using the boot media created in the previous steps, boot the target server into the vRanger restore environment.
When the boot is complete, a list of available network devices and their connection status appears. If no DHCP server is detected, each Ethernet device shows as “Disconnected.”
2
Select the preferred network device.
If only one device is present, it is automatically selected.
3
Press Enter to select the highlighted network interface.
You are then prompted to select either Use DHCP, which attempts to obtain an IP address again, or Configure Static IP.
4
To configure a static IP address, select Configure Static IP.
5
In the Setting Static IP dialog box, enter the IP address, subnet mask, and gateway information, and then select Submit.
The target server is configured with the selected IP information.

Selecting a savepoint

The savepoint is from where the data for the physical machine is restored.

To select a savepoint:
1
In the main vRanger UI, click My Repositories.
2
Select the repository in which the savepoints for the server you want to restore are stored.
3
In the Working Repository pane, select a savepoint to restore.
 
* 
NOTE: For the procedures on restoring from a manifest file, see Performing a full restore from manifest for VMware VMs.
4
You can automatically restore the machine to the latest savepoint. To do so, right-click on the machine row and click Restore Latest.
To select a different savepoint, expand the machine row and select the desired savepoint. Right-click the savepoint, and click Restore, or click Restore on the vRanger toolbar. The Restore Wizard starts.
5
On the Job Information page, enter the Job Name and Job Description.
Click Next.

Mapping disks

The Disk Mapping page of the wizard lets you map the protected disks in the savepoint to the existing physical disks on the target server.

To map disks:
1
On the Disk Mapping page, in the Restore Machine IP Address field, enter the IP for the target server; for more information, see Booting the target server.
2
Click Map Disks.
The page lists the disks in the chosen savepoint.
3
For each disk you want to recover, select the appropriate target disk in the Restore to Disk drop-down menu; for disks that you do not want to recover, select Skip this Disk.
4
Click Next.
The Recurrence Schedule Selection page appears.

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 lets you select the number of days, hours, and minutes that should pass between jobs.
NOTE: The interval selected must be greater than or equal to 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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating