Jens Kupka Posted September 1, 2020 Share Posted September 1, 2020 Hello,the following initial situation:- vmware ESXi 6.5 with 2 running VMs ( we'll call them VM01 and VM02 here)- Restoring a VM (VM02) from the old backup (ghetto-VCB) and rename it to VM02r This means that there are now 3 VMs on the host system- VM01 (running)- VM02 (running)- VM02r (still switched off)The backup job that is still scheduled for the backup of the VM02 has now not backed up the VM02, but the VM02r. I haven't changed anything in the job. In the NAKIVO inventory of the ESXi host, only VM01 and VM02r can now be seen (see NAKIVO-pictures). The VM02 is no longer in the inventory and can therefore no longer be selected for a backup. What can be the reason for this phenomenon? How do I get back to the VM02 without deleting the VM02r from the host? Thx for HelpJens 1 Link to comment Share on other sites More sharing options...
Official Moderator Posted September 1, 2020 Share Posted September 1, 2020 Please let us know if you ran recovery in the "production" or "synthetic" recovery mode. In the "production" mode and all uuids from original VM are used for restored one, that could cause the described situation. 1 Link to comment Share on other sites More sharing options...
Jens Kupka Posted April 27, 2021 Author Share Posted April 27, 2021 Hi, I deleted the restore job because I "experimented" with the jobs But I believe that I did the restore in "Production mode". So the same vc.uuid was used in the vmx file and the backup found the wrong VM (Murphy says hello: ). I think the "Recovery mode" was the reason. Kind regards, Jens 1 Link to comment Share on other sites More sharing options...
Official Moderator Posted April 28, 2021 Share Posted April 28, 2021 11 hours ago, Jens Kupka said: Hi, I deleted the restore job because I "experimented" with the jobs But I believe that I did the restore in "Production mode". So the same vc.uuid was used in the vmx file and the backup found the wrong VM (Murphy says hello: ). I think the "Recovery mode" was the reason. Kind regards, Jens Hello, @Jens Kupka! Our support team would need more information to help with your issue. You may contact the support team directly via support@nakivo.com to provide a more detailed explanation. If there is anything else I can help you with, don't hesitate to contact me. Link to comment Share on other sites More sharing options...
Jens Kupka Posted April 28, 2021 Author Share Posted April 28, 2021 14 hours ago, Official Moderator said: Hello, @Jens Kupka! Our support team would need more information to help with your issue. You may contact the support team directly via support@nakivo.com to provide a more detailed explanation. If there is anything else I can help you with, don't hesitate to contact me. Hi, at the moment I can't recreate the "bug" and don't want to try. If the error occurs again, I will contact you again. Kind regards, Jens 1 Link to comment Share on other sites More sharing options...
Official Moderator Posted April 29, 2021 Share Posted April 29, 2021 10 hours ago, Jens Kupka said: Hi, at the moment I can't recreate the "bug" and don't want to try. If the error occurs again, I will contact you again. Kind regards, Jens @Jens Kupka, Of course, contact us when you need any assistance. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now