Posted on 2013-12-05
In my efforts to create multiple levels of backup for my network systems I am learning to use wbadmin to use a vsscopy along side using BackupExec, and Symantec Backup Exec System Recovery because I am always paranoid about my backups and wanting to regularly take them off-site to test DR situations.
I see you can use the GUI, but it has the limitation when using scheduled backups to a network share of overwriting the old which to me is an uber no no. So I am now creating a shared folder to schedule backups for each day of the week using wbadmin. My question is for a DC that only has one volume C: do I need to include the -allCritical switch or is having the -include:C: and -allCritical redundant if I follow it up with -systemState.
wbadmin start backup –backupTarget: \\Target-Server\Share_Name\ -include:C: -allCritical -vssCopy -systemState
or should I ditch the -Include:C:?
wbadmin start backup –backupTarget: \\Target-Server\Share_Name\ -allCritical -vssCopy -systemState