-
- Novice
- Posts: 4
- Liked: never
- Joined: May 04, 2010 3:59 pm
- Full Name: Scott Barnett
- Contact:
Difference between Full restore and VMK,VMDK
What is the difference between a Full Restore from a Veeam Backup and a VMK,VMDK File retore from Veeam Backup?
Thanks in advance
Thanks in advance
-
- Chief Product Officer
- Posts: 31753
- Liked: 7258 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Difference between Full restore and VMK,VMDK
Hello, please refer to the User Guide page 65 onwards for description of all restore types.
-
- Novice
- Posts: 4
- Liked: never
- Joined: May 04, 2010 3:59 pm
- Full Name: Scott Barnett
- Contact:
Re: Difference between Full restore and VMK,VMDK
doesn't really answer my question..To me they look as there both doing the same kind of restore. Is a full restore better then a VMK,VMDK?
-
- VP, Product Management
- Posts: 6032
- Liked: 2858 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: Difference between Full restore and VMK,VMDK
A full restore restores the entire VM and registers the VM in vCenter. This is usually the correct choice if the VM has been deleted and you need to restore it.
A VMK,VMDK restore allows you to restore the underlying files that makeup a VM individually. For example, assume you have a VM with a C: and D: drive each using separate VMDK files. The C: drive is the OS, and the D: drive is for data. Perhaps the D: drive become corrupt for some reason. You can stop the VM and restore just the VMDK file for the D: drive rather than the entire VM. Also, you can restore a VMDK file to another host and attach it to a new VM, etc.
We typically use the "Full" restore only in cases when the entire VM has been deleted. Otherwise we restore the VMDK files individually. The main advantage of restoring the VMDK files rather than the entire VM for our environment is that a "full" restore looks like a new VM, it has a new UID, and we have to remember to move it into the proper folder so that it gets backed up. Also this will create "shadow" instances of the VM in your Veeam jobs that won't be cleared until you run a full. Restoring individual VMDK files doesn't create this behavior since the VM keeps the same UID.
A VMK,VMDK restore allows you to restore the underlying files that makeup a VM individually. For example, assume you have a VM with a C: and D: drive each using separate VMDK files. The C: drive is the OS, and the D: drive is for data. Perhaps the D: drive become corrupt for some reason. You can stop the VM and restore just the VMDK file for the D: drive rather than the entire VM. Also, you can restore a VMDK file to another host and attach it to a new VM, etc.
We typically use the "Full" restore only in cases when the entire VM has been deleted. Otherwise we restore the VMDK files individually. The main advantage of restoring the VMDK files rather than the entire VM for our environment is that a "full" restore looks like a new VM, it has a new UID, and we have to remember to move it into the proper folder so that it gets backed up. Also this will create "shadow" instances of the VM in your Veeam jobs that won't be cleared until you run a full. Restoring individual VMDK files doesn't create this behavior since the VM keeps the same UID.
-
- Novice
- Posts: 4
- Liked: never
- Joined: May 04, 2010 3:59 pm
- Full Name: Scott Barnett
- Contact:
Re: Difference between Full restore and VMK,VMDK
Thank you!! That is what I was looking for...
Who is online
Users browsing this forum: Dima P., JamesNT, pmichelli, Semrush [Bot] and 108 guests