Serviceguard Disaster Recovery Products Compatibility and Feature Matrix (Metrocluster with 3PAR Remote Copy) - Linux and HPUX

4
1 Note: This table represents what has been certified and is supported. If other storage, firmware or software versions are available but not indicated in this table, it is currently
not supported by Metrocluster with 3PAR Remote Copy. The table will be updated when new versions are certified.
2 Note: Support life for specific storage models (and associated microcode/software) may end sooner and will take precedence.
Note: Metrocluster supports mixed clusters, where the cluster nodes can be HP 9000 and HP Integrity servers. The same restrictions/guidelines as Serviceguard will apply. Refer to
the White Paper “Configuration Rules for a Mixed HP 9000 / Integrity Serviceguard Cluster” at www.hp.com/go/hpux-serviceguard-docs -> Serviceguard.
3 Note: 3PAR arrays currently allow a maximum of 16 SSH connections. Due to this, the number of Metrocluster packages that can be simultaneously started is restricted to a
maximum of 16. Refer to the section “Managing SSH Connections to 3PAR array” in the manual for more information.
4 Refer to 3PAR documentation to get information on supported versions of HP 3PAR Inform OS CLI on respective Operating Systems.
5 VM/vPar as a Serviceguard Package: It is not recommended to replicate Guest’s/vPar’s boot disk across sites as the boot disk on recovery site will have different WWID. So, it
is recommended to have a separate boot disk image at each site with same Guest name. Any changes to the root disk must be manually synchronized between sites.
6 Note: HP Metrocluster 3PAR package will have impact if the HP 3PAR storage system is upgraded to any of the following 3PAR OS versions
· 2.3.1 MU5 Patch35
· 3.1.1 MU3 Patch27
· 3.1.2 MU3 Patch16
Please refer the respective release notes for more details.