Running FC5 with Bacula 1.38.5. I use two pools to hold DDS-4 and DDS-3 tapes respectively. All tapes have been labeled and registered in their respective pools. I use normally DDS-4 tapes for daily back-ups and the DDS-3 for special purposes like manually initiated back-ups of VMware vertual machines.
I usually keep the current DDS-4 tape loaded and yesterday I had to reboot in order to work on the next Linux (and Bacula) version. When I booted back to FC5 Bacula started as expected and mounted the loaded DDS-4 tape. However, what I didn't see was that it assumed it belonged to the DDS-3 pool. The consequence was that the daily back-ups failed with error messages which ment absolutely nothing to me. It was not till I issued the "status storage" command that I saw the error. An "unmount DDS-3" and a subsequent "mount DDS-4" cleared the problem. I have several questions to this experience: 1. Was it a bug? 2. Could I have avoided it? 3. Is the way I use the two pools unreliable? 4. Why doesn't Bacula know which pool and storage a specific volume belong to? I hope someone can shed some light on this to me strange behaviour, -- Erik. ------------------------------------------------------------------------- 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
