On Dec 24, 2012, at 12:31 PM, nkir <tsm-forum AT BACKUPCENTRAL DOT COM> wrote:

> Thank you! I know about these options. But how exactly I can apply them?
> How to check that DB backup was successful and I can proceed next task?
> 
> +----------------------------------------------------------------------
> |This was sent by knikonor AT gmail DOT com via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------

I'm not sure what you mean by "these options," so I'll start with the obvious 
ones and let you tell us if these are what you already know. 

Presumably you're talking about running a script as an administrative schedule. 

Scripts can run in two modes: parallel and serial. If you want to make sure one 
command finishes before another starts, you must be in serial mode. Also, my 
observations make me doubt that serial mode is honored if a script calls 
another script. 

A script can branch based on the return code from a command. One way to do it 
would be to branch for a successful backup, where the non-branch code-path 
would be a very general error routine. Alternately, you could branch on various 
return codes you expect to get and have different error routines for each 
error, but that is more than I do. 

Finally, remember that many commands by default run in the background. BACKUP 
DB by default only tells you that it started. If you want to wait for it to 
finish and check its return code then, you need to use the WAIT=YES option on 
it. This is true for many long-running administrative commands. 

Nick