HP Application Recovery Manager software Integration guide (March 2008)

recovery in cluster configurations, see the HP Application Recovery Manager software

administrator's guide.

Additional steps after restore of a CCR copy to the original database

In a CCR environment, after an instant recovery of a CCR copy to the original

database residing on the application system, perform the following steps to enable

normal operation of the original and copy databases:

CAUTION:

Do not move the clustered mailbox server without first performing the following steps. If

you move the server (using the Move-ClusteredMailboxServer cmdlet), you can

risk data loss.

1. Mount the restored store on the application system.

2. On the passive node, where the copy of the database exists, delete the

transaction logs.

3. On the passive node, use the Update-StorageGroupCopycmdlet to seed the

storage group copy or to re-synchronize the original and copy storage group.

4. On the passive node, use the Resume-StorageGroupCopy cmdlet to resume

the storage group copy.

You can now move the clustered mailbox server to other node by using the

Move-ClusteredMailboxServer cmdlet.

Troubleshooting

This lists problems you might encounter when using the Application Recovery Manager

Microsoft Volume Shadow Copy integration with ZDB integration.

For general Application Recovery Manager troubleshooting information, see the

online Help.

Before you begin

• Ensure that the latest official Application Recovery Manager patches are installed.

See the online Help index: “patches” on how to verify this.

Integrating the Application Recovery Manager ZDB integrations and Microsoft Volume

Shadow Copy Service