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 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.
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.
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.
6 Click Burn.
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.
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.
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.Complete the steps in the following procedure to boot into the vRanger restore environment using DHCP.
▪ 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.
Complete the steps in the following procedure to boot into the vRanger restore environment using a static IP address.
1 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.”
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.
6 [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.
1 In the main vRanger UI, click My Repositories.
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 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.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.
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.
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 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.
1 On the Recurrence Schedule Selection page, select from the options described in the following table.
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.
• 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 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.
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.
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.
3 Click Finish.
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.
You can restore a file from a savepoint by accessing the File Level Restore command in the My Repositories view. FLR is accessible regardless of how the savepoints are sorted. You can right-click the savepoint in the Working Repository pane to select the command or you can click to select the savepoint and then click the FLR icon on the toolbar.There is no need to copy or recreate the contents of the disk. The data remains compressed. When you make an FLR request, only the relevant files are moved from the repository to the designated computer.A key component of the vRanger FLR is the vRanger catalog functionality. While you can use FLR without cataloging enabled, it is much easier to find a preferred file by using a catalog search than through manual browsing of savepoints.
NOTE: If the volume was created on Windows Server ® 2012 or later, the vRanger machine must also use Windows Server 2012 or later to complete FLR. Older systems may not show data on GPT disks.
VMs with dynamic disks are not supported for FLR.
Cataloging lets you search and browse savepoints for files inside the backup archives. Cataloging must be enabled at the start of the backup job to function, and also enabled globally in the Configuration Options dialog box.
1 On the main vRanger UI, navigate to the My Repositories pane, and then select the repository in which you want to search.
▪ Click the Catalog Search Icon .
▪ On the Menu Bar, click the Tools menu, and then click Catalog Search.The Catalog Search & Browse dialog box appears.Entering a search string in the Catalog Search Criteria field searches all repositories and savepoints for the string.
3 The Advanced option lets you limit the search to a repository or VM (savepoint).
5 Select the preferred savepoint, and click FLR for File Level Restore, or Restore for the Full Restore.
NOTE: Catalog searching supports the traditional wildcard character (*) in any position. The search string can be as short or as long as you prefer; however, the shorter the string, the longer the search takes. SQL Server® Express is limited to one CPU and 1 GB of RAM; a short search string — for instance, “dot” — could result in very slow searching, and SQL Server Express could run out of memory. To minimize performance issues during Catalog Search, make the search string as specific as possible.