About the dissimilar disk restore process

In a standard restore, BMR uses the current client configuration to recreate the original system. Little or no intervention is required because the original system is moved onto the original disk configuration.

In a dissimilar disk restore, intervention is required because you have to map the volume configuration from the protected client to the new disks. (Disk refers to a physical disk, and volume refers to a logical division of disk space on one or more physical disks.)

Mapping occurs as follows:

Before the restore. You can create a configuration you can edit (an editable restore configuration) and initialize that configuration with the new disk layouts. Then map the original volume configuration to the new disks. After you finish mapping, you restore the client using the restore configuration. This method requires a record in BMR of the following:
- Layouts of the new disks on the client, which is necessary, for example, when you perform a discovery operation.
- Whether another protected client has the same disks
During the restore. You perform a standard restore and BMR detects that the disks are different. BMR enters DDR mode and creates an editable restore configuration so you can map the disks. You map disks as follows:
- For UNIX and Linux clients, use the BMR disk mapping utility in the NetBackup Administration Console on the master server.
- For Windows clients, you can map on the client or on the master server using the BMR disk mapping utility in the NetBackup Administration Console.

You should use dissimilar disk restore in the following circumstances:

A physical disk is replaced.
The size of one or more disks has decreased and cannot contain the same volume arrangement.
The location of one or more disks changes.
The number of disks has decreased and the required volume arrangement cannot be restored.
You need to change the layout and volumes for the restored system.
You want to restore only some of the disks in a system.

Warning:

Changes in disk locations may prevent a clustered resource from going online after a restore. BMR does not attempt to adjust clustered resource attributes to account for a dissimilar disk restore.