Updating from 3.3.1 MU5 (with most recent patches to 3.3.2
Posted: Mon Jan 15, 2024 5:27 am
Hi,
I've got a couple of customers of 3.3.1 MU5 (with most patches). One is an 8200 the other an 8450. Planning to move them over to 3.3.2 (EMU1) soon. Both are running primarily ESXi workloads on ESXi 7.x. No complex replication or anything like that so I am guessing it should be straightforward enough. My only concern is the customer on the 8200 who has been using both dedup and compression for much of their estate. As a result the nodes running pretty high from a saturation point of view. Typically over 90% most of the time. Not an issue in itself as it still runs within acceptable performance parameters but I know high loads can slow down updates considerably. I've done previous updates (with warnings about the utilisation) and they've completed ok. Just wondering if there are any things to be aware of going to 3.3.2 EMU1. They around 80% utilised from a storage standpoint.
Assume there will probably be node reboots for this one...
Any feedback appreciated.
I've got a couple of customers of 3.3.1 MU5 (with most patches). One is an 8200 the other an 8450. Planning to move them over to 3.3.2 (EMU1) soon. Both are running primarily ESXi workloads on ESXi 7.x. No complex replication or anything like that so I am guessing it should be straightforward enough. My only concern is the customer on the 8200 who has been using both dedup and compression for much of their estate. As a result the nodes running pretty high from a saturation point of view. Typically over 90% most of the time. Not an issue in itself as it still runs within acceptable performance parameters but I know high loads can slow down updates considerably. I've done previous updates (with warnings about the utilisation) and they've completed ok. Just wondering if there are any things to be aware of going to 3.3.2 EMU1. They around 80% utilised from a storage standpoint.
Assume there will probably be node reboots for this one...
Any feedback appreciated.