Hi all,
I recently preformed a full restore of a VM and it worked fine, but I need to turn on the old one to review the logs and other files. As long as I disconnect it from the network, are there any reasons why I shouldn't do this? As I understand it the restore is completely separate from the original VM, but I'd like to confirm that before I turn it on and end up breaking something on the restored version.
Thanks.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Nov 24, 2021 12:47 pm
- Full Name: Matthew Erb
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Booting up original VM after full restore
Hi Matthew,
Just make sure that two VMs are not "online" at the same time and this should be it. Disconnecting it from the network or connecting it to a separate network should be the steps you need to do.
Thanks!
Just make sure that two VMs are not "online" at the same time and this should be it. Disconnecting it from the network or connecting it to a separate network should be the steps you need to do.
Thanks!
-
- Veeam Software
- Posts: 688
- Liked: 150 times
- Joined: Jan 22, 2015 2:39 pm
- Full Name: Stefan Renner
- Location: Germany
- Contact:
Re: Booting up original VM after full restore
Hi,
I don't see any issue with what you are describing here. If you performed a full recovery we created a new VM which is not linked to the old one.
As you said the most important thing is to make sure you don't have all of a sudden both, the old and new VM running in the same network/AD as this will get you in trouble.
An alternative to booting up the old one would be to mount the VMDKs to a temporary, other VM and with that you can access the filesystem without having those issues. Of course only the filesystem would be accessible so this will not help if you need any config details of windows or so.
Thanks
I don't see any issue with what you are describing here. If you performed a full recovery we created a new VM which is not linked to the old one.
As you said the most important thing is to make sure you don't have all of a sudden both, the old and new VM running in the same network/AD as this will get you in trouble.
An alternative to booting up the old one would be to mount the VMDKs to a temporary, other VM and with that you can access the filesystem without having those issues. Of course only the filesystem would be accessible so this will not help if you need any config details of windows or so.
Thanks
Stefan Renner
Veeam PMA
Veeam PMA
Who is online
Users browsing this forum: Bing [Bot] and 27 guests