[BETA] [HPE] HPE VME and backup vme-manager itself

[ajari]

Hello,

just installed quick B&R test for HPE VME and VM backup / restore works just fine.
But then I have to ask this one question: Is it possible to backup vme-manager via B&R same way, as rest of the VM's? Like you could backup vcenter in v*ware.

Vme-manager seem to have its own backup function, which contains db dump. Yes, if you don't have functionally vme-manager, maybe you can't restore anything anyways. Hence this silly post.

Br,
Jari

[ajari]

Sorry, forgot those [BETA] [HPE] tags from subject.

[EvgenyBaev]

Hello, ajari

Our rescan procedure is intentionally designed to exclude the HPE Manager from backup targets. However, we recently discovered a bug that allows the manager to remain visible among backup targets. This issue is scheduled to be fixed in 1.0 released version.

In a recent case, another customer attempted to back up the HPE Manager, and the operation failed with the error: “VM-NAME: Sequence contains no matching element.” You can find further details in this thread:
rhv-olvm-sc-hypercore-xcp-ng-hpe-vme-f6 ... 2e1f7475e3

During backup and restore operations, our plugin interacts with the HPE Manager via its REST API. Even if backing up the manager were technically possible, the process would likely not be reliable.

If support for backing up the manager is required, we would need to consider an alternative approach, different from the standard procedure. It's worth noting that a similar feature is supported in VMware, so we will continue to explore this possibility. However, I don't believe it will be feasible in version 1.0 of the HPE plugin. Additionally, implementing such functionality might require further changes on the HPE side as well. Perhaps this could be considered for future releases.

[ajari]

Hi EvgenyBaev,

Thank you for very promt reply!
Let see what happens with HPE plugin in future.

Br,
Jari

[dcolpitts]

Hi Evgeny - honestly I think there needs to be an investigation into backing up the VME Manager once the beta is concluded and the code is out the door in v1.0. It has the potential to just be too darn complex to rebuild, especially in a multi-cloud environment. And yes I do realize that it has it's backup functionality, but the issue is that is probably not included within any Veeam backup that a SMB would be doing by default. The standard has already been set by being able to backup vCenter, and I think may folks would expect VME Manager to be the same, even if the underlying infrastructure / software is significantly different.

dcc

[EvgenyBaev]

Hello, Dean

Thank you for raising this point. I recognize that the ability to restore the HPE Manager could be valuable in certain scenarios. We plan to revisit this topic after the 1.0 release, but at this stage, it's difficult to estimate the level of effort required to implement such functionality.

By comparison, backup and restore of VMware environments have been a standard feature for a very long time. However, if we look at another similar products - such as Nutanix AHV - they still do not officially support backup of Nutanix Prism Central and instead recommend using the native Nutanix snapshot capabilities.
https://community.veeam.com/discussion- ... l-vm-11116

[dcolpitts]

Just something to keep in your mind set during this process. HPE and it's partners are pushing VME as a direct VMware replacement, and the community that will be moving to VME are looking for feature parity with VMware, and this includes the entire ecosystem, which VBR (and VeeamOne for that matter) falls under. So it would be the next logical step. And a snapshot is not a backup.