Microsoft Data Protection Manager 2006 Writer Restore Specifics; Restore The Dpm Server First - HP Data Protector A.06.11 Integration Manual

• If an RSG for the storage group you are restoring already exists on some system
other than the target system, the RSG is not automatically deleted and so the
creation of an RSG on the target system fails. In this case, you should manually
delete the RSG on the other system.

Microsoft Data Protection Manager 2006 writer restore specifics

When restoring the DPM writer, you can:
• Restore the DPM server first and then use the DPM to restore clients.
In case of a disaster, when the entire DPM server is lost, perform a standard
disaster recovery procedure first and continue with restoring the DPM server. See
"Restore the DPM server
• Restore individual DPM clients directly, without using the DPM server (for example,
if you cannot restore the DPM server or if you want to avoid the additional step
of recreating the DPM snapshot). When restoring the DPM clients directly you
can select between component restore and file restore modes. See
DPM clients
NOTE:
Although the Data Protection Manager databases could also be restored using the MSDE
writer, this method is not recommended, because DPM is not shut down automatically
as with the DPM writer. If you really need to use this writer, shut down the DPM server
manually.
Limitations
• Restore to another server is not supported by the Data Protection Manager writer.
• Parallel restore to different clients is not supported.

Restore the DPM server first

1. Start the DPM administrator console and add disks to the storage pool so that
you have enough free space to restore the replicas.
Ensure that the DPM writer (service) is started.
2. Switch to the Data Protector Restore context. Expand Restore and Microsoft
Volume Shadow Copy Writers and select the client from which you want to
restore the data.
198 Integrating Microsoft Volume Shadow Copy Service with Data Protector
first" on page 198
directly" on page 201.
"Restore the