Redeployment of upgraded Omnistack 4.1.3 -> 5.0.0

[kletool1]

Hi there!

We had an upgraded Federation with 2 Simplivity 380 Gen10 G (R2G96A) nodes. (before 4.1.3 with vCenter 7 - after 5.0.0 with vCenter 8 and ESXi

then 2 of the Disks in the RAID10adm were replaced due high latency issues.

In the Redeployment with ESXi 8 and Simplivity Omnistack 5.0.0 the Support protection against two drive failures is gone. - Now the Storage Space has different Size ~3,5TB.

Does anyone know, how a redeployment can take place with  protection against two drive failures?
From the Interoperability Guide ESXi 8 is not supported with Omnistack 4.2.0, vCetner 8 may work.

Thanks in advance, Klemens

[Steven Clementi]

I have not done much with OmniStack 5.0.0 yet, I.E. a fresh installation, so I cannot validate what you are saying... however, if you are in a position to do an actual redeployment of a node or the cluster, you might be able to follow a four step process:

1. Deploy the node in a new single node cluster with an older version of Omnistack/ESXi

2. Migrate all VMs to the newly deployed node.

3. Rinse and repeat on the evacuated node.

4. Upgrade to ESXi 8 and Omnistack 5.0.0 again

Will take a little longer than you were expecting, but should get you back to what you seem to want.

[Sanika]

Hello @kletool1 

It seems like you've got a complex situation with your SimpliVity Federation and RAID configuration.

According to my understanding, I would recommend you some general steps which might help in redeployment with protection against two drive failures:

1. After replacing the disks, reconfigure the RAID10adm setup to ensure it's properly configured for dual-drive failure protection. Incorrect configuation can impact data protection & capacity.
2. Confirm that the replaced disks are healthy and compatible.
3. Review the OmniStack 5.0.0 settings to ensure that the protection against two drive failures is enabled.
4. Rebalance data across the disks to ensure even distribution and optimal performance.
5. Check how storage space is allocated across virtual machines and datastores. A significant change in storage consumption could explain the reduced capacity.

Additionally, you may create a backup of your configuration before attempting any redeployment or reconfiguration.

If you have further doubts regarding this, I would recommend you to contact HPE support team for more assistance.

Hope this helps!

Regards,
Sanika.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.

[kletool1]

Hello Steven, hello Sanika!

since the 16 Disk Deployment with Dual Disk Resiliency happend under 4.1.3 the Upgrade to vSphere 8.0 and Simplivity  5.0.0 worked fine.

Then 2 Disks were replaced, and we redeployed 1 Node with DM 5.0

In DM 5.0 the option for Dual Disk Resiliency was gone.

One first have to buy "HPE SimpliVity 380 Gen10 G Expansion Kit (R6U13A)"

Add the new 2 Disks per Node and redploy with DM 5.0 as a 18 Disk RAID6 Deployment.

Have Fun with Omnistack and have a nice Day, Klemens

[Sanika]

Hello @kletool1 

Thanks for sharing this information.

Regards,
Sanika.

[kletool1]

@Sanika Now we´re ready to install the new Upgrade Kit

HPE SVT 380G 2P 1.92T 16-18 disk Upgrade kit R6U13A and redeploy the Nodes.
Does anyone  have an idea about how the Disks have to be populated over the 3 Bays?