...
The nature and capacity of our backups has been evolving, from incremental overnight tape backups to full nearline near line storage of complete VMs. We have many instances of Server 2008 R2, and thus I am coming to rely heavily on Windows Server Backup. Lately I have been creating a number of scheduled task calls to wbadmin. I have opted for scheduled tasks in order to have multiple WSB backups to a variety of remote UNC targets. The tasks will invoke full backups of whatever I put into -include and will be pointed at whatever UNC I put into -backuptarget.
...
So eventually I got back around to running it manually. I had done this successfully days earlier when ironing out the basic commands. Aha! When triggering the backup to a remote UNC you will ALWAYS get the prompt pictured, warning about lack of protection at the UNC location. You have to click Y/N to proceed. Hence you will not be able to schedule a task, a script execution, or any other automation you might dream up, without responding to the warning, or including the -quiet switch to surpress suppress it. Simple but deadly if you forget, like I did, and leave it out.