HP Application Recovery Manager software A.06.10 - Product announcements, software notes, and references (March 2008)

In such cases, a ZDB to the high performance disks and subsequent instant
recovery will reverse the situation.
• Routine maintenance, including (but not limited to) hot-swapping HBAs/SCSI
controllers, disk array controllers, FC switches, and/or online firmware upgrades
during backups are not supported. Backups are a high-IO activity and should not
be done at the same time as routine maintenance.
Limitations on database integrations
See the HP Application Recovery Manager software integration guide for integration
specific limitations.
Limitations on clusters
MC/ServiceGuard limitation
• When adding components on MC/ServiceGuard, add the component(s) on the
active node. Then start the package on the other node, and add the component(s)
on this node too.
Other limitations
• Dynamic disks are not supported.
• Application Recovery Manager does not support hostnames with non-ASCII
characters.
• The name of a backup specification should not exceed 64 characters.
• The - (minus) symbol must not be used as the first character in any Application
Recovery Manager labels or descriptions.
• The word DEFAULT is a reserved keyword and must not be used in backup
specification names.
• When changing the omnirc file, it is required to restart the Application Recovery
Manager services/daemons on the system. This is mandatory for the crs daemon
on UNIX and recommended for Application Recovery Manager Inet
and CRS services on Windows. On Windows, restarting is not required when
adding or changing entries, it is required only when removing entries.
• If you use quotes ("") to specify a pathname, do not use the combination of a
backslash and quotes (\"). If you need to use trailing backslash at the end of the
pathname, use double backslash (\\).
Product announcements, software notes, and references 23