지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault Bare Metal Recovery 13.1.1 - User Guide for Plug-ins

Introducing NetVault Bare Metal Recovery Plug-ins Deploying NetVault Bare Metal Recovery Using the Plug-in Offline Client
Plug-in Server: an overview Installing and removing Plug-in Server Configuring Plug-in Server for use with Plug-in Offline Client Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client Backing up data with Plug-in Offline Client Restoring data with Plug-in Offline Client
Using NetVault Bare Metal Recovery Plug-in Live Client
Plug-in Live Client overview Configuring Plug-in Server for use with Plug-in Live Client Installing and removing Plug-in Live Client Backing up data with Plug-in Live Client Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client Restoring data with Plug-in Live Client
NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery  Troubleshooting

Using Plug-in Offline Client to restore data to a physical machine

Using Plug-in Offline Client to restore data to a physical machine

This option lets you recover backups of the client to a physical machine that has the same hardware specification as the machine that was used for backup. It includes the following:

CAUTION: Even if there is no difference between the system devices in a backup and a restore, the order of the disks might be different. If the restored data is started without performing a rename, any data that exists on the disks is lost. To compare the information of the physical disk at backup and restore, note the Disk Geometry and Device Size at backup. For more information, see Performing a restore in which Disk Numbers are different from the backup.

For version 1.1.6 and later, also compare the Disk ID of the targeted disk on the Create Selection Set page to the Disk ID of the same disk on the NetVault Selections page.

Quest strongly recommends that you disconnect all disks that contain critical data from the server before you boot the Plug-in Offline Client.

Prerequisites for restoring data with Plug-in Offline Client to a physical machine

Prerequisites for restoring data with Plug-in Offline Client to a physical machine

A DR restore procedure is a delicate operation. Before setting up and running a DR restore, the prerequisites covered in the following topics must be met.

The target device name on the NetVault Bare Metal Recovery Client, for example, Disk 0 (IDE), must be the same as it was at the time of backup.

Boot the target NetVault Bare Metal Recovery Client with the Plug-in Offline Client to prepare it for the restore of a DR image. To complete the boot routine, perform the steps covered in Booting a NetVault Bare Metal Recovery Client with Plug-in Offline Client.

This information should have been noted before the backup — see Verifying Disk Geometry and Device Size. Have this information handy to complete the restore correctly.

Sometimes, the restored Windows system might require reactivation. Verify that you have the necessary license key for reactivation.

The NetVault Bare Metal Recovery Client machine that is to serve as a target for the restore must be accessible to the Plug-in Server. To check access, perform the following steps.

1
With the NetVault Bare Metal Recovery Client booted with Plug-in Offline Client, access the NetVault Server, and start the NetVault WebUI.
2
Access the NetVault Selections page to verify that the applicable client machine has been added as a NetVault Bare Metal Recovery Client.
a
Open the Plug-in Server to reveal existing clients.
c
When the Edit Bare Metal Recovery Client dialog box is displayed, verify that the data is correct or change it as required.

Restore procedure for using Plug-in Offline Client to restore data to a physical machine

Restore procedure for using Plug-in Offline Client to restore data to a physical machine

The procedure for restoring a DR restore to a physical machine includes the steps outlined in the following topics:

2
On the Create Restore Job — Choose Saveset page, select Plug-in Server from the Plugin Type list.
When you select a saveset, the following details are displayed in the Saveset Information area: Job ID, job title, server name, client name, plug-in name, saveset date and time, retirement setting, Incremental Backup or not, Archive or not, saveset size, and snapshot-based backup or not.
5
Click Next.
6
On the Create Selection Set page, select the data that you want to restore.
The Dos Compatibility Region is the first 32k to 512 bytes from start of the disk that immediately follows the Master Boot Record (MBR). NetVault Bare Metal Recovery backs up this region to support GRUB Stage 1.5. However, this region is always backed up and restored regardless of the existence of GRUB Stage 1.5. This option is not selectable.
1
On the Create Selection Set page, click , and select Physical Machine (the default) as the Restore Type to restore the backup of a client to a physical machine.
When Physical Machine is selected, the Physical Recovery Options frame containing the Restore Name field is shown. The default value of this field is the NetVault name for the NetVault Bare Metal Recovery Client from which this backup was originally performed, based on the backup saveset selected. This name is associated with a specific IP address that was previously configured. If this value is left at its default setting, selected data is restored to the machine that was originally backed up. You can use this field to relocate restored data to a standby NetVault Bare Metal Recovery Client, if necessary. For complete details on this procedure and its use of this option, see Using Plug-in Offline Client to recover data to a standby NetVault Bare Metal Recovery Client.
If you are using the Windows PE-based Plug-in Offline Client, selecting Physical Machine also makes the driver-related fields available. These options support using different hardware during a restore.
2
If you are using the Windows PE-based Plug-in Offline Client, complete the applicable options:
Inject Boot-Critical Device Driver: If you are restoring to different hardware that also uses a different mass storage controller, select this option. After you select this option, the Boot-Critical Driver Directory and Driver Injection Only options become available.
Boot-Critical Driver Directory: If you selected the Inject Boot-Critical Device Driver option, enter the complete path to the local drive where the drivers for the mass storage controller are stored.
Driver Injection Only: If you previously completed a restore but pointed to an incorrect location in the Boot-Critical Driver Directory field, select this option to run the driver-injection portion of the restore process again. This option eliminates the need to restore the data again, but lets you inject the correct drivers. Check that you enter the correct path in the Boot-Critical Driver Directory field. By default, the Inject Boot-Critical Device Driver option remains selected; do not clear it as this option prevents the Driver Injection Only option from working.

The final steps include setting additional options on the Schedule, Source Options, and Advanced Options pages, submitting the job, and monitoring the progress through the Job Status and View Logs pages. These pages and options are common to all NetVault Plug-ins. For more information, see the Quest NetVault Administrator’s Guide.

1
To save the settings, click Ok, and then click Next.
2
In Job Name, specify a name for the job if you do not want to use the default setting.
3
In the Target Client list, select the machine on which you want to restore the data.
TIP: You can also click Choose, and then locate and select the applicable client in the Choose the Target Client dialog box.
4
Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options.
5
Click Save or Save & Submit, whichever is applicable.
You can monitor progress on the Job Status page and view the logs on the View Logs page. For more information, see the Quest NetVault Administrator’s Guide.
If selecting individual partitions for a restore, also select the Master Boot Record and System Partition item. Failure to do so results in a failed restore.
When performing a restore of a Plug-in Server backup, options available in the Target Client list should be left at their default settings. If a target other than the intended is selected from this list the restore fails.
If you are using the Linux-based Plug-in Offline Client with IDE/Parallel Advance Technology Attachment (PATA) disks and the backup was created using Plug-in Offline Client v5.6.4 or earlier, use the Rename feature to force the system to reexamine and map the disk correctly. Partitions backed up before v5.7.1 are named using an “hd<x>” format, while v5.7.1 and later use an “sd<x>” format. Failure to use the rename feature causes the restore to fail with a “Error: All disk name requested from client is not equal to the backup disk name /dev/hda” message.
If you are using the Linux-based Plug-in Offline Client and you are migrating a physical server to a virtual environment in which the Client is Windows-based, install the disk drivers on the OS before you back up the machine. For more information, see NetVault Bare Metal Recovery physical-to-virtual (P2V) recovery.

Post-restore for using Plug-in Offline Client to restore data to a physical machine

Post-restore for using Plug-in Offline Client to restore data to a physical machine

After restoring a backup to a different machine, review following points and take the applicable action:

Network connection renamed: Because a different network card is in use, the Network Connection is automatically renamed to local area connection 2.
Physical address: Because a different network card is in use, the physical address, Media Access Controller 9MAC), is different. If you use applications that rely on this address, work with the application’s vendor to address the change.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택