The blocked IO on the primary volumes becomes unblocked and a sense error is created indicating a change of target port group to the secondary volumes.

Target port groups on the primary site become passive and the secondary site become active.

When you switch over, the primary volumes are blocked and any ‘in flight’ I/O is trained and the group is stopped and failed over.

The Remote Copy volumes are created on both arrays and exported to the hosts at both sites using the same WWN’s in Read/Write mode, however only one site has active I/O, the other site is passive.

Asymmetric Logical Unit Access (ALUA) is used to define the target port groups for both primary and secondary 3PAR StoreServ.

I mentioned above that Peer Persistence has been included to allow support for vSphere Metro Storage Cluster so how does it work?

Asynchronous Remote Copy – 2400 Volumes.

A few of the commands that I have used on a regular basis are:

My overall experience with Remote Copy in Inform OS 3.1.1 has been that of frustration, a lot of the work has to be done via the CLI as the GUI has a nasty habit of not sending the correct commands or for some reason Remote Copy Links not establishing.

Supports replication from one StoreServ to two StoreServ for added redundancy.Supports up to eight FC or IP links between 3PAR StoreServs.I’m sure it won’t be long and 3PAR will have something like the Failover Manager (FOM) that StoreVirtual uses.Ī few of other points to know about Remote Copy are:

Should always be used with Enterprise Plus licenses so you can instigate should Storage DRS rules to ensure that VM’s should always use the datastores they are in the same site as.įrom a 3PAR StoreServ perspective the Virtual Volume is exported with the same WWN to both arrays in Read/Write mode, however only the Primary copy is marked as Active, the Secondary copy is marked as Passive.Īt the time of writing this post, the failover is manual, as a quorum holder has not been created yet.If a VM’s datastore is at the other end of the ISL then you are using very ineffective routing.Think of the intersite link (ISL) usage, would enough bandwidth be available to continue synch replication?.

You can vMotion between sites, however a few things to consider when doing this:

3par ssmc change vmware ip