Using database availability groups (dags), E in, Revealing secondary – HP XP P9000 Command View Advanced Edition Software User Manual
Page 386: Volumes prior to a remote restore operation
5.
Select the copy group, start the Change Pair Status Wizard, and select create.
6.
Select the copy group, start the Change Pair Status Wizard, and select swap.
7.
In the Replica History tab of the SQL Server subwindow, select the replica created before the
failure occurred and click Delete Replicas.
8.
Use the disk management function to mount the primary volume connected to the database server.
9.
Start SQL Server on the database server.
Revealing secondary volumes prior to a remote restore operation
Prior to a restore operation to a remote site, if the secondary volumes are concealed, you must first
reveal them as described here.
1.
Start the Windows Command Prompt on the backup server.
2.
Change directory to the following folder:
Application-Agent-installation-destination\DRM\bin\
3.
Execute the following command:
drmappcat
4.
Obtain the appropriate backup ID from the displayed list by comparing the
END-TIME
for the
backup ID and the creation time displayed in the Replica History tab. Here is an example of the
command output:
NOTE:
If some replicas have identical creation times, run the command again with the following
additional arguments:
drmappcat -hostname database-server-name
Where
database-server-name
is the name of a particular database server. This
command filters out the replicas for other hosts.
5.
Execute the following command to reveal the volumes:
drmdevctl backup-ID -attach
Where
backup-ID
is the value obtained in the previous step.
Using Database Availability Groups (DAGs)
Replication Manager supports Exchange Database Availability Groups (DAGs). In a DAG configuration,
data mirroring occurs between the DAG active node and passive nodes. (The target server can be
an active or passive node.)
Managing application replicas
386