HP StorageWorks Application Recovery Manager Administrator's Guide (T4395-96004, February 2008)

Appendix B
Known Application Recovery Manager Issues and Workarounds
Appendix B B-7
Integration Related Issues
Disk Array Integrations
• When running a ZDB on EVA, the process can hang under the
following condition: The source disks involved in the backup session
have control distributed between 2 or more EVA SMI-S Providers.
The processes must be manually stopped.
Workaround: Disks involved in an EVA ZDB must be controlled
through one HP StorageWorks SMI-S EVA provider only. Multiple HP
StorageWorks SMI-S EVA providers may be configured and active in
the environment, but disks in a specific ZDB cannot be controlled by
more than one of these HP StorageWorks SMI-S EVA providers.
Cluster Related Issues
• If backup server is in a cluster environment and the backup is
performed using the actual hostname, instant recovery fails when you
try to recover using the secondary host.
Workaround: Use a virtual hostname for the backup.
• When restoring the Cluster Database on a Microsoft Cluster Server,
you should stop the cluster service on all inactive nodes before
starting the restore. If cluster service is active on any other node at
the time of the restore, the restore API will fail and may cause a
failover.
• Sequential restores of the same database may cause a cluster
resource instability. If you need to restore the same database multiple
times, it is recommended to wait 10 minutes between the restores to
let the writers and services stabilize.
• If a backup session hangs during a cluster failover (all session agents
fail), a timeout will be reported (by default, after 7200 seconds) but
the session does not abort. As long as the session is hanging, the same
backup cannot be started.
Workaround:
Abort the session manually at any time and restart the backup
session.