Simplivity Omnistack backup

[Alexandrealmeid]

Hello

I'm trying to make a backup of my simplivitys virtual controllers (Omnistack) with veeam backup and replication but the vcenter allays reply with the error

The operation is not allowed in the current state.

Any help on this?

[DeclanOR]

Hi @Alexandrealmeid 

Thanks for using the forum. i would recommend removing the OVC's from your VEEAM backup policies. The OVC VM is not something we should backup. It's not restorable as such. if anything untoward happens the OVC, we would redeploy the node or perform an in-place reset.

The failures are expected. Most likely due to hardware passthrough on the RAID controller and TIA card.

Hope this helps,

DeclanOR

[Henchman67]

So, your reply is clear that, Not taking a backup of the OmniStack is  okay, but me being very long in the tooth, not taking a backup of something being upgraded in production is not something I could bring myseld to do. So does the Software Update App take a WMWare snapshot prior to upgrading the OmniStack Appliance? and I note at v5.0.0 it mentions ugading the ESX software as well? and again when my change management team ask me what the back out plan is, what am I telling them please?

[franke1]

Hi Henchman67
the OVC is "just" the managing part of simplivity. even if you would make it to create a backup of the vm you would not be able to use it. 

for example if you have 2-node+ cluster, the ovc manages the NFS storage, right. So the second you do the bkp, it's alreay outdated ....if you would restore it (it is not possible) you would have a outdated OVC....wich would be useless...

so the answer you give your change mgmt team is : "roll back plan = redeploy the destroyed host with its OVC via the deploymetn software.
of course you do a backup of all the VMs u are running on this host in advance any update. also you probably have a 2nd node where you migrate your vms while doing upgrades....
I do it for 44 sites in 6 federations....never had an issue ....once hat to redeploy a node in a 2 node cluster (no big deal). byside had a dozen of issues while update it but all with solutions via HPE support (no add )