KB Logo

TOLIS Group Knowledge Base

Browse KB by category:
Go to KB #:
Glossary
Email   Bookmark



Executing Tasks Before or After a Job Run

Views: 6739
Votes: 0
Posted: 27 Apr, 2011

If you have a task that should be performed before or after the BRU Server job is executed, there is a mechanism provided for both agents and the server. Such tasks include stopping and restarting a mail server, exporting a database to a flat file, warning users that a backup is about to occur, and many more. The files may be created using any programming of scripting language supported by your system including shell, python, perl, Applescript, or even compiled C/C++. The only requirement is that the resulting file be executable and return a zero for success or non-zero for any error condition.

On your agents, add executable files named 'pre' and 'post' to the agent install directory — "/usr/local/bru-server" on all OS X and Unix variants — 'pre.bat' or 'pre.cmd', and 'post.bat' or 'post.cmd' in "C:\Program Files\BRU Server Agent Configuration\" on Windows systems.

Additionally, there is a master 'pre' and 'post' capability on the server system. The file should be placed into the server application directory — "/usr/local/bru-server/" — and be named 'backup.pre' and 'backup.post'. The server sequences will be executed before any client backup operation is begun and after ALL client backup operations have completed for any backup job that is performed. The same rules apply for creating the server-specific jobs as for the client system 'pre' and 'post' sequences.

Others in this Category
document How do I control my tape library with the libctl (tm) command on Mac OS X?
document BRU Server Troubleshooting - Tape-Related Guidance
document SCSI Compatibility Issues Under Mac OS X
document Does BRU Server provide 64-bit support?
document How to automatically disable Time Machine during a BRU Server backup.
» More Articles



RSS
Powered by KnowledgebasePublisher
Page Load Time: 0.032098 seconds / 32.098 milliseconds.
Page File Size: 23233 bytes.