The tool you will want to use is “wbadmin.exe”
Backing up a virtual machine is fairly straight forward. Your command will look like this:
wbadmin start backup –backupTarget: –hyperv:
Which will result in something like this:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/8715.image_thumb_52713A10.png)
Some things to be aware of:
wbadmin get versions –backupTarget:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/5684.image_thumb_4432C120.png)
If the backup was taken a while ago – you may have forgotten the name(s) of the virtual machines that you backed up. You can find this by running:
wbadmin get items –version: –backuptarget:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/7725.image_thumb_1CF877EB.png)
Once you have this information you can restore the backed up virtual machine by running:
wbadmin start recover –version: –itemType:hyperv –items:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/5265.image_thumb_3CA751B3.png)
Backing up a virtual machine is fairly straight forward. Your command will look like this:
wbadmin start backup –backupTarget:
Which will result in something like this:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/8715.image_thumb_52713A10.png)
Some things to be aware of:
- Wbadmin will always warn you that the virtual machine will be put into a saved state for backup. This is wrong. The virtual machine will only be put into a saved state if it is not running the latest virtual machine additions (or is not a Windows virtual machine).
- You will be prompted before the backup starts. You can get around this by adding –force to the end of the command.
- You can use either the virtual machine name or the virtual machine ID when selecting virtual machines.
- You can list multiple virtual machines to backup.
- If you are backing up to a SMB share – new backups will automatically overwrite old backups (i.e. there will only be one backup kept on the share). This will not happen if you are backing up to a local disk.
wbadmin get versions –backupTarget:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/5684.image_thumb_4432C120.png)
If the backup was taken a while ago – you may have forgotten the name(s) of the virtual machines that you backed up. You can find this by running:
wbadmin get items –version:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/7725.image_thumb_1CF877EB.png)
Once you have this information you can restore the backed up virtual machine by running:
wbadmin start recover –version:
- –backuptarget:
![image image](https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/41/22/metablogapi/5265.image_thumb_3CA751B3.png)
No comments:
Post a Comment