Hi, according to the script, make_catalog_backup expects a database password, if used, to be supplied as Argument $3, which will make catalog backups work in case one is using a password. But, this means one will have the database password showing up in backup logs, which might be available to a wider audience than the BackupCatalog part of the director configuration. I've thought about multiple ways to change this, but so far all consisted of hacking the make_catalog_backup script, which would of course be lost on upgrades.
I also thought about adding a readonly database user for doing the backups, but I'm afraid in the long term this would risk having things missing in the backup, due to potential sql permission issues. has one of You found a nice way of handling the password here? -- 'Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen' ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
