I have a somewhat related question.
I can create a backup job via the GUI that very specifically backs up various data/directories/users/Libraries.
I can also use wbadmin as a brute-force tool to backup *everything* on a Windows 7 host.
What I'm looking for is the best of both worlds here - I want to use wbadmin (so these jobs can be scripted and pushed to hosts) but I also want the utter flexibility that the GUI provides when setting up a job.
My question is: when setting up a GUI job, are your choices/inputs recorded in a config/initialization/xml file somewhere so I can review EXACTLY what is going on beneath the covers?
OR:
Would it make more sense to heavily customize the USMT xml files and use ScanState for backups if I want very granular control? I don't really care about a system image since our build process is heavily customized (we use the Windows Deployment Toolkit
2010) - I only care about user data - unfortunately our users place some data outside of their user profile, so I need to be able to fairly dynamically select other locations on disk.
Thanks.