HP Data Protector A.06.11 Recovery Manual page 101

UNIX Cell Manager only: The mmerge.cmd command works only on Windows
systems with Data Protector Automatic Disaster Recovery component installed. If you
are using a UNIX Cell Manager, copy the P1S files to a Windows client which has
Automatic Disaster Recovery component installed and merge the files. Rename the
merged P1S files back to the original name and copy them back to the Cell Manager.
Example
Example for merging P1S files for MSCS with 2 nodes: mmerge
Data_Protector_home\Config\server\dr\p1s\node1.company.com
Data_Protector_home\Config\server\dr\p1s\node2.company.com.
Enclose the path in quotes on Windows if the path contains a space character. The
merged files will be node1.company.com.merged and
node2.company.com.merged. Rename the files back to their original names (you
will have to rename the source P1S files first): node1.company.com and
node2.company.com.
Restoring hard disk signatures on Windows
The MSCS service uses a hard disk signature written into the MBR of every hard disk
to identify physical disks. If the shared cluster disks have been replaced, this means
that the disk signatures were changed during Phase 1 of disaster recovery. As a
consequence, the Cluster Service will not recognize the replaced disks as valid cluster
resources, and cluster groups depending on those resources will fail. This applies
only to the restore of the active node, since shared cluster resources are operational
as long as at least one of the nodes is up and running and claims ownership of the
resources. This problem does not apply to EADR and OBDR critical disks because
the original disk signatures of all EADR/OBDR critical disks are automatically
recovered. In case you have replaced any other disks, you will have to restore their
hard disk signatures as well.
The most critical shared disk is the cluster quorum resource. If it has been replaced,
than the original disk signature must be restored, or the cluster service will not start.
During Phase 2, the MSCS Database is restored into the \TEMP\ClusterDatabase
directory on the system volume. After the system is restarted, the cluster service will
not be running, because the quorum resource will not be identified due to the changed
hard disk signature in Phase 1. This can be resolved by running the clubar utility
(located in the Data_Protector_home\bin\utilns), which restores the original
hard disk signature. After clubar successfully finishes, the cluster service is
automatically started.
Disaster recovery guide 101