[Veritas-bu] Starting a job from command line
2011-11-29 15:23:09
You would have to write a wrapper script to tweak and then untweak the include
list and feed the database name as a command line argument or have a separate
policy for each database that only gets ran in the event that database failed.
(or write your script in a manner that runs a backup of all databases unless it
is provided a database name as a command line argument. Using the -w option you
could block until the job completes and react to the status code accordingly)
Why don't you just specify "Microsoft Information Store:\*" in your policy
include list and then only re-run the failed client jobs? (using bpdbjobs)
-CC
+----------------------------------------------------------------------
|This was sent by chuck.carson AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Veritas-bu] Starting a job from command line,
rhugga <=
|
|
|