Hi to all: I'm currently working on the integration with bacula and rman, the tool to make backups/restores of Oracle databases.
Reading bacula documentation, seems that some releases before, the admin was able to define environment variables inside bacula ( and use them as parameters for the scripts called on before/after jobs ) but now this method seems deprecated in favor of python scripting. My idea is to make standard scripts ( less maintenance and advantages on adding new databases to backup ) that 'point to' the database/catalog to backup using parameters, like this example: /home/oracle/bin/full_backup_rman10g.sh <rman catalog connection chain> <ORACLE_SID_TO_BACKUP> <ARCHIVELOG_MODE_OF_DATABASE_TO_BACKUP> Then should be called in bacula like this: Client Run Before Job="/home/oracle/bin/full_backup_rman.sh sys/[EMAIL PROTECTED] ORCL NOARCHIVELOG" With this approach we could be able to deploy a set of identical scripts ( no internal modification for each host with Oracle to be protected and of course, no changes lost if we need to upgrade this scripts) in the same way even if we use rman locally in the host with the oracle database ( or databases ) to back up or if we use the same machine where bacula-dir relays or if we use a third machine to consolidate all rman procedures, etc... I'm a completely python ignorant, and before spend time trying to understand how to translate this behavior to python way of life, I prefer ear from you. Thanks in advance D. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
