HPE 3PAR OS 3.3.1 MU2 Release

[l-53]

3.3.1 MU2 has been pretty solid on our 9450 for the past couple of weeks. Solved a few random node reboot bugs that were present in 3.3.1 MU1. Haven't had any metadata issues on the DECO volumes.

[Thustra]

no mu2 file was never available to download. The hpe support engineer will give you a link to download it.

But what if you do your own upgrades. We had planned to upgrade one of our customers next week but the damn file is still not available

[silenthill]

no mu2 file was never available to download. The hpe support engineer will give you a link to download it.

But what if you do your own upgrades. We had planned to upgrade one of our customers next week but the damn file is still not available

You can contact the SPS team to get the download, you will have to pry but you can get it.

Make sure you get the "OS-4.2.0.18-U013" download as well, as that is required on the 3par before you can go from 3.3.1 MU1 to 3.3.1 MU2

[JinSXS]

Make sure you get the "OS-4.2.0.18-U013" download as well, as that is required on the 3par before you can go from 3.3.1 MU1 to 3.3.1 MU2

what is "OS-4.2.0.18-U013" , i've already have the 3.3.1 MU2

im running on SP 5.03.1 , but i can't find how to upload the 3.3.1MU2 for deployment

[Nikolay_K]

Hi All,

if anyone got 3.3.1 MU2 on 7400 updated with dedup volumes? or without dedup?

HPE refusing my request to update 7400 to 3.3.1 MU2, suggesting 3.2.2.MU6 but I have 3.2.2 MU4.

[Patrick]

...
HPE refusing my request to update 7400 to 3.3.1 MU2, suggesting 3.2.2.MU6 but I have 3.2.2 MU4.

Same here, I may update to MU6 but have no real need for it...the arrays have been stable on MU4 for me and they are only hosting a few select workloads.

[godosh]

I am upgrading my two 8200s to 3.3.1 MU2 right now. I did one yesterday and the second one will be done today. They are not all-flash, its ssd + fc.

So far so good.

Release version 3.3.1 (MU2)
Patches: None

Component Name Version
CLI Server 3.3.1 (MU2)
CLI Client 3.3.1
System Manager 3.3.1 (MU2)
Kernel 3.3.1 (MU2)
TPD Kernel Code 3.3.1 (MU2)

If you have any question feel free to ask me !

[rbird97]

I am upgrading my two 8200s to 3.3.1 MU2 right now. I did one yesterday and the second one will be done today. They are not all-flash, its ssd + fc.

So far so good.

Release version 3.3.1 (MU2)
Patches: None

Component Name Version
CLI Server 3.3.1 (MU2)
CLI Client 3.3.1
System Manager 3.3.1 (MU2)
Kernel 3.3.1 (MU2)
TPD Kernel Code 3.3.1 (MU2)

If you have any question feel free to ask me !

Are you doing the update or is HPE?

Are you also updating the service processors?

[elesus]

Hi guys,

do you see any improvement in dedupe and/or compression ratios?

We are currently on 3.2.2.612 MU4 (20450) and our dedupe ratios are not that high:
1.2 for DBs and 1.3-1.4 for other data. We are thinking to go 3.3.1 MU2 mostly due to availability of compression feature.

Is it worth it? What are your ratios? Does anyone do dedupe+compression?

I understand that MU2 consumes less CPU, do you see that on all your systems?

[Chris212]

No improvements on compaction ratios (dedup or compression) from 3.3.1 GA.
CPU consumption, it depends. From 3.3.1 GA we have seen a huge improvement on CPU consumption but this could not be the case for those having 3.3.1 MU1 or 3.2.x.

But MU2 is a must have for those having 3.3.1 because it corrects a huge number of critical bugs.

About compaction ratio on 3.3.1 :
On DB : compression ratio between 1.5 and 2.5 (database are not compressed software side (SQL/Oracle)) we do not use dedup as it is not recommended.

On other : dedup ratio between 6 and 20. We use VM with thick eager zeroed disks on those thin provisionned LUN's. Majority of this ratio comes from the dedup of the free space (zeroed) on the VM's. We do not use compression on those LUN's as it stress 3par CPU too much.