HP P6000 Continuous Access Implementation Guide (T3680-96431, August 2012)

You can use switches to create zones and work around some fabric limitations. For example:
• Unsupported hosts and incompatible arrays can be on a fabric with HP P6000 Continuous
Access if they are in independent zones. For compatibility with operating systems and other
software, see the HP P6000 Enterprise Virtual Array Compatibility Reference.
• A fabric can include multiple HP P6000 Continuous Access solutions.
For more information about zoning, see “Creating fabrics and zones” (page 58).
Basic configuration rules
The following rules apply to the basic HP P6000 Continuous Access configuration:
• Each array must have dual array controllers.
• Host operating systems should implement native or installed multipath software. For compatible
multipath solutions, see the HP P6000 Enterprise Virtual Array Compatibility Reference.
• Local and remote arrays must be running compatible controller software. For information about
supported replication relationships between arrays with VCS and XCS controller software,
see the HP P6000 Enterprise Virtual Array Compatibility Reference.
• A minimum of two HBAs (or one dual-port HBA) is recommended for each host to ensure no
SPOF between the host and the array. For maximum HBA ports, see the HP SAN Design
Reference Guide.
• All virtual disks used by a single application must be in a single DR group; only one application
per DR group is recommended.
• All members of a DR group will be assigned to the same array controller.
• Each site must have at least one management server. Two management servers are
recommended for high availability after a disaster.
• It is highly recommended that you use dedicated HP P6000 Command View management
servers with HP P6000 Continuous Access. Although you can install HP P6000 Command
View on an application server that is accessing the array, care should be taken if you decide
to do so. If LUN presentation is not managed properly, a shared HP P6000 Command View
management/application server may have access to LUNs on both the source array and the
destination array. This is undesirable and could result in two servers simultaneously performing
I/O to a common LUN, resulting in an undesirable data state.
In addition, copies of HP P6000 Continuous Access and array/operating system support
documentation should be accessible at each site. The documentation facilitates disaster recovery,
rebuilding, or repair of the surviving system if access to the other site is lost.
Extended fabric using long-distance GBICs and SFPs
Adding long-distance and very-long-distance GBICs and SFPs to simple Fibre Channel links increases
the possible distance between sites. For more information about the use of long-distance fiber and
supported GBICs and SFPs, see the HP SAN Design Reference Guide.
Extended fabric using WDM
Adding dense or coarse WDM to basic Fibre Channel allows greater distances between sites than
long-distance GBICs and SFPs. The difference between WDM and basic fiber configurations is the
addition of a multiplex unit on both sides of the intersite link.
24 Planning the remote replication fabric