Backing up Hyper-V virtual machines from the command line

Backing up Hyper-V virtual machines from the command line

Rate This
  • Comments 23

Last week I posted about how you can now use Windows Server Backup in Windows Server 2012 to backup virtual machines.  One of the first questions that people had was “how do I do this from the command-line?”  So – let me show you!

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:<location to backup to> –hyperv:<list of virtual machines to backup>

Which will result in something like this:

image

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.

Once you have created the backup – you then need to know how to restore it.  This is, unfortunately, more complicated.  The first thing you will need to do is to find the version of the backup and the name of the virtual machine you want to restor.  You can find the version of the backup by running:

wbadmin get versions –backupTarget:<location where you backed up to>

 

image

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:<version string for the backup you want> –backuptarget:<location where you backed up to>

 

image

Once you have this information you can restore the backed up virtual machine by running:

wbadmin start recover –version:<version string for the backup you want> –itemType:hyperv –items:<list of virtual machines to restore> –backuptarget:<location where you backed up to>

image

Cheers,
Ben

Leave a Comment
  • Please add 6 and 3 and type the answer here:
  • Post
  • Excellent post, thanks for documenting this so simply :)

  • Is this backup completely independent of a Windows Server Backup scheduled through the GUI? I.e. if I already have scheduled host-level backups to external USB drives (these are incremental) will calling wbadmin command-line backup to a network share somehow interfere with those USB backups (e.g. confuse their incrementals) or is it completely independent and just allows me to do additional backups this way? Thanks.

  • Hi Ben, Thanks, good info.

    Is there a way to delete a backup taken by wbadmin?

  • I have tried this but am not able to backup Hyper-V Vm's

  • Thanks for this simple offering. Saves time, heartache and money.

  • This is separate from any other backups you are doing - just double-check in Windows Server Backup UI and also in Task Scheduler, to make sure you still have your other jobs. Having said that, you definitely don't want to run more than one backup at the same time, generally speaking - so, coordinate the times of any other jobs you have, so they do not overlap with this one.

  • I had posted that I think Ben may be wrong about the comment "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)."

    What it means - "saved state," is just that they are saying it is taking a "snapshot" of the system - Snapshot = "A saved state." So, it's not saying it puts the VM into a 'suspended state;' just that it takes a snapshot. Thanks.

  • DENNIS: What does "backing the Host Component" do?

    Is that like a full image backup of the Host machine?

    Or... what?

    And then, how to restore it?

Page 2 of 2 (23 items) 12