3PAR OS 3.2.1
-
- Posts: 142
- Joined: Wed May 07, 2014 10:29 am
3PAR OS 3.2.1
Anyone been brave enough to test it?
Re: 3PAR OS 3.2.1
I was not even aware it was out, do you have a link to release notes?
-
- Posts: 142
- Joined: Wed May 07, 2014 10:29 am
Re: 3PAR OS 3.2.1
I have not seen that, just that HP released some docs friday:
HP 3PAR OS 3.2.1 Concepts Guide
HP 3PAR OS 3.2.1 CLI Administrator's Manual
Updated pre-planning guide with upgrade path to 3.2.1
3PAR OS 3.1.2 MU3 Patch 41 as a pre-requisite for upgrade
3PAR Management Console 4.6 release notes
It is in controlled release, and I suspect it might have been for a week or two?
( IMC 4.6 docs was released 5. Sept)
I found it when one of the product managers, Ivan Iannaccone posted a link to HP 3PAR Adaptive Flash Cache solution brief:
http://h20195.www2.hp.com/V2/GetDocumen ... c=us&lc=en
Flash Cache + dedupe is going to be freaking awesome, but I am a bit reluctant to be the first to dip our toes in...
HP 3PAR OS 3.2.1 Concepts Guide
HP 3PAR OS 3.2.1 CLI Administrator's Manual
Updated pre-planning guide with upgrade path to 3.2.1
3PAR OS 3.1.2 MU3 Patch 41 as a pre-requisite for upgrade
3PAR Management Console 4.6 release notes
It is in controlled release, and I suspect it might have been for a week or two?
( IMC 4.6 docs was released 5. Sept)
I found it when one of the product managers, Ivan Iannaccone posted a link to HP 3PAR Adaptive Flash Cache solution brief:
http://h20195.www2.hp.com/V2/GetDocumen ... c=us&lc=en
Flash Cache + dedupe is going to be freaking awesome, but I am a bit reluctant to be the first to dip our toes in...
Re: 3PAR OS 3.2.1
I have no desire to beat test their code. We did "Controlled Release" of 3.1.3 and will never to that again. Honestly I won't touch one of their releases util MU2+
Also you would think for a"Controlled release" support would be tuned in and be able to expedite and escalate issues encountered during those upgrades, but no way. We had issues with 3.1.3 "controlled release" and had sev 1 open for 6-8 hours before anyone that knew what was going on got involved and then went without replication for 14 hours.We plan on staying at 3.1.3 MU1 until RC features are released and then an MU past that.
Also you would think for a"Controlled release" support would be tuned in and be able to expedite and escalate issues encountered during those upgrades, but no way. We had issues with 3.1.3 "controlled release" and had sev 1 open for 6-8 hours before anyone that knew what was going on got involved and then went without replication for 14 hours.We plan on staying at 3.1.3 MU1 until RC features are released and then an MU past that.
Re: 3PAR OS 3.2.1
I too did the GA release of 3.1.3 (we are still on it), and i think i'll wait a while to upgrade again.
not that we had huge issues, the array has been running perfectly, but we do not use that many functionalities except for AO and basic array functions.
not that we had huge issues, the array has been running perfectly, but we do not use that many functionalities except for AO and basic array functions.
Re: 3PAR OS 3.2.1
I did 3.2.1 RTM upgrade the day after it got released it includes SP upgrade as well and it went smoothly. As per our test requiremnet we need this update but sadly we can't make use many functionalities as we dont have flash drives
-
- Posts: 142
- Joined: Wed May 07, 2014 10:29 am
Re: 3PAR OS 3.2.1
"Software upgrades to HP 3PAR 3.2.1 GA for systems that use Remote Copy and CLX are currently not supported."
I must say HP keeps disappointing. Is the pace of change in the industry too quick these days?
There certainly are major new features in this release,
but the old HP would not accept a feature creep to meat some arbitrary deadline.
We were without support for Peer Persistance on vSphere 5.5 for almost half a year,
and now a major feature is suddenly not supported for a new minor release?
Can someone please explain how HP can bring in Peer Persistance support for windows and not support remote copy at the same time?
It might not be such a loss, as AFC seems sort of half baked anyway.
I'll let the rest of the world do the bug squashing in this release...
Do anyone have any info on HP 3PAR Express Writes Software?
I must say HP keeps disappointing. Is the pace of change in the industry too quick these days?
There certainly are major new features in this release,
but the old HP would not accept a feature creep to meat some arbitrary deadline.
We were without support for Peer Persistance on vSphere 5.5 for almost half a year,
and now a major feature is suddenly not supported for a new minor release?
Can someone please explain how HP can bring in Peer Persistance support for windows and not support remote copy at the same time?
It might not be such a loss, as AFC seems sort of half baked anyway.
I'll let the rest of the world do the bug squashing in this release...
Do anyone have any info on HP 3PAR Express Writes Software?
Re: 3PAR OS 3.2.1
I think they mean "RemoteCopy and CLX together" - as in the Win-based file servers for 3PAR. They use CLX and SMI-S to do a transparent failover, because PeerPersistence was not supported for Windows prior to 3.2.x. And perhaps this concept changes with PP being supported now.
So, as I understand it, RemoteCopy is of course supported witht 3.2.1...
So, as I understand it, RemoteCopy is of course supported witht 3.2.1...
When all else fails, read the instructions.
-
- Posts: 142
- Joined: Wed May 07, 2014 10:29 am
Re: 3PAR OS 3.2.1
That would make more sence...
But isn't CLX dependent on remote copy?
So putting the two together is sort of redundant?
I think I'll ask HP about this, could be a documentation error...
But isn't CLX dependent on remote copy?
So putting the two together is sort of redundant?
I think I'll ask HP about this, could be a documentation error...
Re: 3PAR OS 3.2.1
CLX manages transparent failover for windows-based file servers. CLX uses SMI-S to directly manipulate the 3PAR storage controller (exporting the secondaries and failover the remote copy group).
With Peer Persistence for Windows, CLX is not needed any more, because PP with quorum device manages the transparent failover.
With Peer Persistence for Windows, CLX is not needed any more, because PP with quorum device manages the transparent failover.
When all else fails, read the instructions.