• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 780
  • Last Modified:

wbadmin syntax/options

Hi guys,  

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
1 Solution
Dirk MareSystems Engineer (Acting IT Manager)Commented:
I would recommend using the include c switch

If I recall correctly the system state only will not help in a bare metal recovery and this is one of your requirements seeing that you are doing DR test and backups
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now