The auto-provisioning can be enabled on any Remote Copy group through the SSMC interface. The auto-provisioning will simplify the process and the chance for human error. Previously, administrators performed this using the 3PAR Command Line Interface, and early adopters had to manually lookup and assign the WWN on the secondary array. When an administrator adds the volume it into a remote copy group, the group auto-provisions and assigns the same World Wide Name (WWN) to the target, secondary volume and that is required for Peer Persistence. This addition to SSMC brings a simple three step process for provisioning new Peer Persistence volumes in the management GUI: Create a new volume, add it to Remote Copy and then Export the volume from both arrays. Add a quorum witness server to the switchover magic and you have a ALUA allows the OS to recognize and redirect IO. At a high level, when a switchover command is issued, the path states change from active to standby and vice-versus.
The source array provides open paths while the replication target shows its paths in standby. HP 3PAR Peer Persistence relies on operating systems which can use the ALUA command set of of the SCSI bus to recognize open and closed paths to a single volume. Peer Persistence is the HP branding for transparent LUN failover between storage arrays with no downtime – a concept VMware administrators will recognize is Metro Storage Clustering in the VMware vernacular. With the 2.1 release of the HP 3PAR StoreServ Management Console, HP has enabled the creation and control of Peer Persistence configurations within the management tool.
0 kommentar(er)
