Hello.
I have installed the GA release of HPE VME (13.1.0.27).
VBR server is Veeam Software Appliance.
The installation of VME plugin was done over previous HPE VME Beta(13.1.0.222-0.el9.x86_64.BETA).
I did not find the way how to uninstall VME beta.
The HPE GA plugin installation was done without problem.
HPE VME is on supported version (as requested in user guide).
I try to perform restore of the Entire VM - new location or different setting. Only name and network is changed. Option "Power on target VM after the restoring" not selected.
I tried two different VMs. The result is always the same. I ge this error message.
Failed : Win22-130-1046 : Failed to perform restore. There must not be more than one service plan with the same code in the HPE VM Essentials manager
I have not found yet the root cause of the issue on the HPE VME side.
The same type of restore was working without problem with VME Beta(13.1.0.222-0.el9.x86_64.BETA) plugin.
Please, have anybody of you the same practice?
Have you any idea what could be the problem?
Thank you
Jan
-
jobhlidal
- Influencer
- Posts: 16
- Liked: never
- Joined: Mar 27, 2018 7:19 am
- Contact:
-
Mildur
- Product Manager
- Posts: 11546
- Liked: 3239 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: HPE VME GA (13.1.0.27) plugin - VM restore failed
Hi Jan
Since the plugin is now GA, please reach out to our Customer Support team for any technical issue. We can’t troubleshoot this over a forum topic, as this is not a technical support forum (explained in our forum policies ). I can only assume we’re trying to create a new Service Plan with the same code during restore—our Support will be able to confirm this from the logs.
Please also share the case number with us for reference.
Best regards,
Fabian
PS: Support can only help if you upload logs: https://www.veeam.com/kb1832
Since the plugin is now GA, please reach out to our Customer Support team for any technical issue. We can’t troubleshoot this over a forum topic, as this is not a technical support forum (explained in our forum policies ). I can only assume we’re trying to create a new Service Plan with the same code during restore—our Support will be able to confirm this from the logs.
Please also share the case number with us for reference.
This scenario is unsupported, and Support may not be able to provide a solution. Beta versions are not supported to be deployed on a production backup server and then upgraded later to GA. It’s also not supported to continue backup chains created with a Beta build using the GA version.The installation of VME plugin was done over previous HPE VME Beta(13.1.0.222-0.el9.x86_64.BETA).
I did not find the way how to uninstall VME beta.
Best regards,
Fabian
PS: Support can only help if you upload logs: https://www.veeam.com/kb1832
Product Management Analyst @ Veeam Software
-
jobhlidal
- Influencer
- Posts: 16
- Liked: never
- Joined: Mar 27, 2018 7:19 am
- Contact:
Re: HPE VME GA (13.1.0.27) plugin - VM restore failed
Hi Fabian.
Thank you for response.
My environment is for testing. So I am not sure if support will accept it.
Regarding beta and GA VME plugin version.
As I wrote, I would uninstall Beta before GA installation, but in documentation there is only the case when VBR server is on Windows platform.
How to do it in linux VBR is missing.
So I installed GA plugin over Beta.
Backup jobs working without problem.
BR
Jan
Thank you for response.
My environment is for testing. So I am not sure if support will accept it.
Regarding beta and GA VME plugin version.
As I wrote, I would uninstall Beta before GA installation, but in documentation there is only the case when VBR server is on Windows platform.
How to do it in linux VBR is missing.
So I installed GA plugin over Beta.
Backup jobs working without problem.
BR
Jan
-
EvgenyBaev
- Veeam Software
- Posts: 54
- Liked: 6 times
- Joined: Apr 11, 2019 11:06 am
- Full Name: Evgeny Baev
- Contact:
Re: HPE VME GA (13.1.0.27) plugin - VM restore failed
Hello @jobhlidal.
Fabian is absolutely right here - upgrading from a Beta version to GA without a clean uninstall is an unsupported configuration.
Unfortunately, there is no convenient way to remove plugins in Veeam Software Appliance. It can be done through the Linux console though — you can access the root shell via TUI (see
https://helpcenter.veeam.com/docs/vbr/e ... tml?ver=13) and remove plugin package with dnf there (package name is veeam-platform-service-hpemorpheusvme).
But even then, Beta artifacts may still remain in the VBR database. This is why we strongly recommend installing the RTM release either on a fresh VBR installation or against a clean VBR database, to fully exclude any potential impact from the Beta. If you are using our plugin purely for testing purposes and setting up a fresh VBR or migrating to a clean database feels too time-consuming, a lighter alternative would be to remove the HPE server from VBR and re-add it after reinstalling the plugin. This won't guarantee a fully clean state, but it may be enough to get things working in a test environment.
Additionally, we made significant changes to the service plan handling mechanisms between Beta and GA. Because of this, old Veeam service plans created by the Beta version on the cluster will need to be cleaned up manually before restore operations can work correctly.
Most likely, the issue will go away after reinstalling on a clean VBR and removing the old Beta service plans from the HPE manager.
Fabian is absolutely right here - upgrading from a Beta version to GA without a clean uninstall is an unsupported configuration.
Unfortunately, there is no convenient way to remove plugins in Veeam Software Appliance. It can be done through the Linux console though — you can access the root shell via TUI (see
https://helpcenter.veeam.com/docs/vbr/e ... tml?ver=13) and remove plugin package with dnf there (package name is veeam-platform-service-hpemorpheusvme).
But even then, Beta artifacts may still remain in the VBR database. This is why we strongly recommend installing the RTM release either on a fresh VBR installation or against a clean VBR database, to fully exclude any potential impact from the Beta. If you are using our plugin purely for testing purposes and setting up a fresh VBR or migrating to a clean database feels too time-consuming, a lighter alternative would be to remove the HPE server from VBR and re-add it after reinstalling the plugin. This won't guarantee a fully clean state, but it may be enough to get things working in a test environment.
Additionally, we made significant changes to the service plan handling mechanisms between Beta and GA. Because of this, old Veeam service plans created by the Beta version on the cluster will need to be cleaned up manually before restore operations can work correctly.
Most likely, the issue will go away after reinstalling on a clean VBR and removing the old Beta service plans from the HPE manager.
Who is online
Users browsing this forum: No registered users and 1 guest