Hi, I am planning to use multiple catalogs for different pools. While creating the needed databases, I realised three points, what would be a real pushup in usability.
1. I have to start three scripts to create a catalog. Every script itself starts another script, depending on the DBMS I use. I usually skip the first script, and start directly the scripts for my DBMS. But it would be much easier to have one script, maybe called "create_catalog.sh", which checks for the used DMBS and then starts the three scripts in a row. 2. The databasename "bacula" is hardcoded in the scripts for creating the database. It is useful to have a default, but when want to I create another database for a different catalog, I have to change the scripts. Giving the database name as parameter is IMHO more useful. 3. Making backups of the database. I can give the database-name as parameter to the delivered make_catalog_backup.sh-script. To create a generic way of backing up a catalog, it would be useful to extract the parameters databasename, databaseuser, etc from the given catalog for the backupjob. In that case I don't have to worry about keeping the credentials up to date in two places. Any comments? Regards Daniel -- Daniel Bloemer - BusinessCoDe GmbH Systemadministration and Support Phone: +49 (0)228 / 28925-43 http://www.business-code.de Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
