Foreword this has been posted to user mailing, but I believe dev mailing would be more correct. Happy to remove one of the 2 post if you ask me to do it.
Currently the default setting of the BackupCataliog job is doing a "full" backup every day (which semantically makes sense). However, when using autochanger with different pools, this has a very negative impact: After every incremental or differential backup, the autochanger will unload the "incremental" or "differential" tape and load the "full" tape, backup the catalog, and next backup will have to reload the "incremental" or "differential" tape (with all the rewind and fast forward for each tape). As anyway, the backup catalog consists of just one file, in case of restore of the catalog (hopefully a lot less frequent than the backups ;-) ), having the catalog on the Incremental, Diff or full pool will likely not cause any issue. So I would propose to either document the changes in the autochanger documentation, or (better in my opinion as I have an autochanger ;-) ) have the default backup job definition changed for everyone. What is your thought? Thierry -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-devel/0056c9b7-4a74-492b-8787-349a4bcbda54n%40googlegroups.com.
