Chatee ahora con Soporte
Chat con el soporte

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

Performing a full restore of a physical machine

Like the restore process for a VM, the restore process for a physical machine uses the vRanger Job Wizard. While the process of restoring physical machines is similar to the VM restore process, some of the preliminary preparations are different.

For information about performing a full restore from a savepoint manifest, see Restoring from manifest.

To perform a full restore of a physical machine, complete the following tasks:

•
Creating the boot media
•
Booting the target server
•
Selecting a savepoint
•
Mapping disks
•
Mapping disks
•
Setting the recurrence schedule
•
Configuring email notifications
•
Starting the restore job

Creating the boot media

Performing a full restore of a physical machine

Like the restore process for a VM, the restore process for a physical machine uses the vRanger Job Wizard. While the process of restoring physical machines is similar to the VM restore process, some of the preliminary preparations are different.

For information about performing a full restore from a savepoint manifest, see Restoring from manifest.

To perform a full restore of a physical machine, complete the following tasks:

•
Creating the boot media
•
Booting the target server
•
Selecting a savepoint
•
Mapping disks
•
Mapping disks
•
Setting the recurrence schedule
•
Configuring email notifications
•
Starting the restore job

Creating the boot media

To restore a savepoint to a physical machine, you must first boot the target server into the vRanger restore environment using the vRanger Restore images — ISO for CD, IMG for a bootable USB drive. You can download the restore image files — vzRestore-<version>.iso and vzRestore-<version>.img — from the Quest website.

To create the boot media, complete one of the following procedures:

•
Creating a bootable CD
•
Creating a bootable USB drive
Creating a bootable CD

Complete the steps in the following procedure to create a bootable CD.

 
* 
IMPORTANT: The procedures for creating a bootable CD differ widely depending on the operating system and software used. The following procedures show how to use the native Windows® 7 utility to create a bootable CD. If you have a different image burning application, follow the instructions for that application.
 
* 
NOTE: This procedure requires a blank CD/DVD and a writable CD/DVD drive.
To create a bootable CD:
1
Insert the blank CD/DVD into the writable drive.
2
Download the vRanger BMR Restore Image (ISO CSD) file from http://support.quest.com/vranger/
3
If necessary, copy the vzRestore-<version>.iso file to the machine with the writable CD/DVD drive.
4
Right-click the ISO file, select Open with, and then click Windows Disk Image Burner.
5
From the disk burner drop-down list, select the drive containing the blank disk.
6
Click Burn.
Creating a bootable USB drive

Complete the steps in the following procedure to create a bootable USB drive.

 
* 
NOTE: There are no native Windows® utilities for creating a bootable USB drive from an IMG file. The following procedure was created using a freeware application, Image Writer for Windows. Follow the instructions for your application.
To create a bootable USB drive:
1
Insert a blank USB drive into your USB port.
2
Download the vRanger BMR Restore Image (IMG Bootable USB Drive) file from http://support.quest.com/vranger.
3
If necessary, copy the vzRestore-<version>.img file to the machine with the blank USB drive.
4
In the Image Writer for Windows UI, browse to the vzRestore-<version>.img file.
5
In the Device drop-down list, ensure that the correct USB drive is selected.
6
Click Write.
7
Click Exit.

Booting the target server

* 
IMPORTANT: The vRanger restore CD is not compatible with UEFI. Please ensure that the target server is not configured to boot into UEFI.

For vRanger to detect the target server, the target server must be booted into the vRanger restore environment and have a valid IP address. The vRanger Restore image is configured to use Dynamic Host Configuration Protocol (DHCP) by default. If you are using static IP, some additional steps are required.

To boot the target server, complete one of the following procedures:

•
Booting into the restore environment using DHCP
•
Booting into the restore environment using static IP
Booting into the restore environment using DHCP

Complete the steps in the following procedure to boot into the vRanger restore environment using DHCP.

To boot into the restore environment using DHCP:
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.
2
Do one of the following:
•
If a DHCP server is available, the restore environment obtains its IP configuration automatically, and a prompt appears with the IP information. Record this information to use during the restore job creation process.
•
If no DHCP server is detected, each Ethernet device shows as “Disconnected.” Select the preferred network device. If only one device is present, it is automatically selected. 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.
3
[Optional] If the vRestore environment does not contain the correct drivers for your hardware, enter a Linux® command prompt by pressing F1, and add them manually.
 
* 
IMPORTANT: Do not reboot the target server or the IP configuration is lost.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación