SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Starting a job from command line
Author Message
Post Starting a job from command line 
I’ve had to split up our Exchange backups into 3 different policies for various reasons. In each policy, I list the names of the databases to back up. Even doing it like this, I get some occasional failures when backing them up. Is it possible to run a backup using bpbackup and specify the individual database I want to back up?

For example, if a backup fails for Exchange database XDB01, will bpbackup allow me to specify just this specific database to back up...or would it be easier to create a copy of my Exchange backup and enter the specific database into that policy? I’m leaning towards doing it with a policy, but wondered if there were alternatives.


Howard Graylin | System Administrator III | C Spire Wireless
6019747719 office

Cellular South is now C Spire Wireless
Please note that my new email address is hgraylin < at > cspire.com

Post  
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

View user's profile Send private message
Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB