Hi,
This issue was worked on as case #07964161.
When we restore a Nutanix VM using restore mode 'Restore to the original location' the VM restores ok but there is a Warning :
Failed to restore the following categories: Prism Central is unavailable: {"api_version": "3.1", "code": 409, "kind": "mh_vm", "message_list": [{"message": "Edit conflict: please retry change.", "reason": "CONCURRENT_REQUESTS_NOT_ALLOWED"}], "state": "ERROR"}
Apparently we can not have that fixed. The workaround to we don't get a warning on the restore job is to use restore mode 'Restore to a new location, or with different settings'
There I need to uncheck the option to 'Restore VM Categories'. Side note about that, is that this workflow will not delete the VM on the Nutanix cluster before restoring it, it will restore it side by side. The other workflow does delete the VM on the Nutanix cluster.
My question is, will the category restore be fixed? An ok fix for me is that the 'restore to the original location' would just not try to restore categories since the categories will populate automatically anyway.
Regards,
Jóhannes
-
johannesk
- Expert
- Posts: 183
- Liked: 38 times
- Joined: Jan 19, 2016 1:28 pm
- Full Name: Jóhannes Karl Karlsson
- Contact:
-
HannesK
- Product Manager
- Posts: 16014
- Liked: 3618 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Error restoring VM with categories
Hello Johannes,
as I cannot see a bug number the the support case, it's hard to say whether it gets fixed.
I asked support whether this limitation is documented anywhere and if not, whether there is a bug tracked for that. Depending on the outcome, I will hopefully be able to answer your question
Best regards
Hannes
as I cannot see a bug number the the support case, it's hard to say whether it gets fixed.
I asked support whether this limitation is documented anywhere and if not, whether there is a bug tracked for that. Depending on the outcome, I will hopefully be able to answer your question
Best regards
Hannes
-
HannesK
- Product Manager
- Posts: 16014
- Liked: 3618 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Error restoring VM with categories
Hello,
I asked internally and the same operation works fine in our test environment. So, we assume something in your environment is not working as expected.
Best regards
Hannes
I asked internally and the same operation works fine in our test environment. So, we assume something in your environment is not working as expected.
Best regards
Hannes
-
johannesk
- Expert
- Posts: 183
- Liked: 38 times
- Joined: Jan 19, 2016 1:28 pm
- Full Name: Jóhannes Karl Karlsson
- Contact:
Re: Error restoring VM with categories
ok, so we should be able to fix it.
Our VBR and Nutanix has been upgraded since I posted this in February. VBR is 13.0.1.2174 and Prism central 7.3.1.5.
We still get the same error when using the 'Restore entire VM' - Nutanix AHV - Restore to the original location.
30.3.2026 08:49:18 Succeeded : Session started at 3/30/2026 8:49:18 AM
30.3.2026 08:55:37 Warning : Failed to restore the following categories: Prism Central is unavailable: {"api_version": "3.1", "code": 409, "kind": "mh_vm", "message_list": [{"message": "Edit conflict: please retry change.", "reason": "CONCURRENT_REQUESTS_NOT_ALLOWED"}], "state": "ERROR"}
We already debugged this with case #07964161. I guess I should have another go with it.
Regards,
Jóhannes
Our VBR and Nutanix has been upgraded since I posted this in February. VBR is 13.0.1.2174 and Prism central 7.3.1.5.
We still get the same error when using the 'Restore entire VM' - Nutanix AHV - Restore to the original location.
30.3.2026 08:49:18 Succeeded : Session started at 3/30/2026 8:49:18 AM
30.3.2026 08:55:37 Warning : Failed to restore the following categories: Prism Central is unavailable: {"api_version": "3.1", "code": 409, "kind": "mh_vm", "message_list": [{"message": "Edit conflict: please retry change.", "reason": "CONCURRENT_REQUESTS_NOT_ALLOWED"}], "state": "ERROR"}
We already debugged this with case #07964161. I guess I should have another go with it.
Regards,
Jóhannes
Who is online
Users browsing this forum: No registered users and 6 guests