Hi,
I created a scheduled backup of my server using wbadmin.msc. This is a simple server - just a domain controller with two drives, and the second drive (D:) is the destination for the backup job. The command line is the usual:
wbadmin start backup -templateid:blahblah -quiet
I went into Task Scheduler and added an action after wbadmin to run a batch file that copies the WindowsImageBackup directory to another server. What I noticed is that wbadmin seems to fork itself off into the background, and return control to Task Scheduler, which then runs the batch file to copy WindowsImageBackup to the other server. Of course, that fails because wbadmin hasn't finished making the backup yet.
So I created a single batch file that runs the wbadmin command and then copies the files, and I get the same result - wbadmin exits quickly and the copy starts but there's nothing to copy yet.
I've looked around for switches to tell wbadmin to wait until the backup is finished before it exits, but haven't found any yet. Is there any sort of switch that will do this? Or some other way to make things run sequentially?
Thanks,
Dave
