Remote copy between 3.1.3 and 3.2.1

[woodunn]

We have T,F,V and 7000 class arrays that are at 3.1.3. We are looking to upgrade to 3.2.1 due the fixes and new features. We have been advised that (from HP)

"3PAR OS release (OS 3.2.1 MU1) does NOT support the legacy F-class and T-class 3PAR systems"

Yep. we were aware of that

"If you have this array in remote copy relationship with another 3PAR array, the allowed delta between major versions of the HP 3PAR OS release is limited to adjacent major release levels—for instance, from HP 3PAR OS 3.1.2 to 3.1.3."

So, be warned that if you have F and T class systems using RC to V and 7000 series, you will need to keep your newer arrays at 3.1.3 for now.

We will be pushing HP for some more clarification around the support ability of legacy arrays RC'ing to new series arrays.......
Have any other users come across this conundrum?

[Gerson]

Hi,

A message from the 3PAR team:

Remote Copy issues are fixed in 321 MU1.



G.

[hdtvguy]

Hi,

A message from the 3PAR team:

Remote Copy issues are fixed in 321 MU1.


G.

That is funny, I have been told in every release RC issues are fixed/improved.

[ailean]

Remote copy has always only been supported between adjacent major versions, usually with a warning that it should only be for transitory periods and not part of a long term strategy. There are plenty of legacy 'features'/limits I'll be glad to see gone from the code base in future.

[woodunn]

We have an interesting conundrum in that we still have 18 months of support on our T800s which we have RC to our V800s. With RC not being "allowed" between more than one major release difference will mean no more upgrades to the V800s after 3.2.1 until we retire the T800s in July 2016. Frustrating to say the least