Hi.

I create a wbadmin backup with (volumes edited) this batch file.

@echo off
setlocal

TITLE Saving OS image

set SOURCE=\\?\Volume{faa99c3f....}\
set TARGET=\\?\Volume{42f9fc72....}\

wbadmin start backup -allCritical -include:%SOURCE% -backuptarget:%TARGET% -quiet

exit

[strike] The problem is that I can't seem to see the images when I try to restore. I can see 1 image with an earlier timestamp that I think is the image I created through the GUI. [/strike]

The problem seems to be that it is not updating the image folder name, or making the old versions available.

Since then I have created 2 additional images using the above batch file, so I believe there should be at least 3 restore images/versions available.

Of note is that on both the GUI run and the first run of the batch file it took a long time, so appeared to be a full backup, whilst on the second run it was blazingly fast :), so I presume an incremental backup occurred.

I have run (D: is the same volume as the target GUID in the above code)

wbadmin get versions -backuptarget:D:

and this also only shows the timestamp from an earlier date.

Do I need to include the -vssFull option in my image creation script?

I have just noticed that the timestamp seems to be coming from the folder name nested inside the "D:\WindowsImageBackup\[PC NAME]\Backup 2015-02-26 151909", whilst the modifed dates on all the files represent the last time the batch file was run.

Another note is that there is more free space on the target (even with the existing backup) than used space on the source, so I can't see it needing to delete an old image for space.

So can you think how I may be able to create the images with multiple restore options like the GUI provides?

• Edited by Nicholas Rodie Thursday, February 26, 2015 10:29 PM

Seems it was mostly working as it should. Although I think on the first batch run it removed/overwrote a previous image, and didn't rename the folder to match the timestamp. I was slightly confused by the timestamps in the PE restore, because the timestamp offset meant it showed the image as being from a different day.

So there is still one issue that I have to resolve. When I initiate a restore from the OS the images are all shown with UTC-00:00, and not UTC+10:00 as per my timezone and system settings.

• Edited by Nicholas Rodie Friday, February 27, 2015 1:34 AM