I did a lot of research before providing this solution to public and I think that the combination of the script I wrote with some registry modifications and the limitation of Windows Backup Schedule to store the backup to a remote network share or external drive with automatic date creation to store the backups, inspired me to share a solution around this.
First of all make sure that you applied the registry modification to support Hyper-V VSS Writer. Instructions on how to do so you can find in this post:
2008/11/windows-server-backup-hyper-v-support/
Create a batch file with the following code:
@echo off
:: set variables
set remote=\\remoteip\remotefolder
set folder=%date:~7,2%-%date:~4,2%-%date:~10,4%
set localC=C:
set localD=D::: do not modify below
echo Backup Started..
mkdir “%remote%\%folder%”
wbadmin start backup -backupTarget:”%remote%\%folder%” -include:%localC%,%localD% -quietecho Backup Complete Succesfully
@pause
In the variables area we define: set folder=%date:~7,2%-%date:~4,2%-%date:~10,4%” which a dated folder directory will be created on the remote location in the format of d-m-Y (ex: 05-11-2008).
Then we execute the wbadmin command with -backupTarget: option to select our destination backup folder. That could be a second local drive, an external usb drive or a network share.
After that we are using the -include: option to select the local drives or paths that we want to backup, which in our case is two volumes called C: and D:. You are not limited to backup the whole volumes but you could easily decide to backup only specific folders from each volume but you will have to define them in the script above.
I had tested a full backup and restoration of Hyper-V images and they are booting succesfully.
To create a scheduled backup
1) Create a new folder on C: drive named BackupSchedule
2) Place the backup script to BackupSchedule Folder
3) Create a backup account that will run the schedule (ex: backup)
4) Create a Schedule Task to run on daily basis the time and hour you wish to backup your server. Remember while you create your task to assign the backup account and select Run whether user is logged on or not option. Also be sure to have the same account details on the remote network location to avoid asking for a password.
Sample Output of the batch script running:



















































drcliff








March 30, 2009
Why the “Full Windows Backup” all the time and not the changes backup or some similar???
[Reply]
Alcor Reply:
February 3rd, 2010 at 9:14 pm
Because the incremental backup did not work on share folder or mapped drive, only on local drive.
[Reply]
Alcor Reply:
February 3rd, 2010 at 9:37 pm
Because incremental backup work only on local disks (on same machine or SAN)
[Reply]
February 4, 2010
Thanks for the answer.
[Reply]