3PAR StoreServ Storage
Showing results for 
Search instead for 
Did you mean: 

3PAR Active Active Cluster

Occasional Visitor

3PAR Active Active Cluster


I have a question about Hp 3par peer persistence,  Can this feature writes data in a  same time with active active in both storage ?  I mean each  host can read and write actively on same lun in both storage.

When I check from Hpe website, What I see, In peer persistence documentations,  Two storages are working like active and passive mode, because it looks one of them is primary and the other is secondary.

I need to know, If it is not working active active cluster. I will  push customer to continue HP XP7 or ıf you recommend other solutions to me, please let me know.





Occasional Visitor

Re: 3PAR Active Active Cluster


Hp peer persistence technology is working little bit different,  It is working one storage primary and other one is secondary. This is not real active active cluster.

In that architecture one storage is primary and all data read and writes transactions directly come primary than it is copying to secondary.  In real active active clusters,  There is no primay and secondary.

 İn real active active storage cluster scenario both storages are working actively and each writes and reads requests from hosts to storages in same time. There is no backround replication.

 For that reason, If you are competing other vendors with active active storage cluster, your choice must be HP XP7. 3par is good product and but ıt does not have real active active storage cluster option.

If you have any question about, please let me know

Best Regards,

Hpe Consultant

Zalina Ramanova


Re: 3PAR Active Active Cluster


Could you explain more for what task you need Active-Active? What scenario for use?


Best regards,

Sheldon Smith
Honored Contributor

Re: 3PAR Active Active Cluster

Peer Persistence is layered on top of (synchronous) Remote Copy. Logically, data is written to both systems at the same time. The host writes to the primary system, the primary replicates the write to the secondary. The host write completes. Reading is done from the local (primary) system for performance.
Again: what problem are you trying to solve?

Note: While I work for Hewlett Packard Enterprise, all of my comments (whether noted or not), are my own and are not any official representation of the company.
If my post was useful, click on my KUDOS! thumb below!