Am 03.09.2018 um 19:54 schrieb Tilman Schmidt: > Am 03.09.2018 um 16:52 schrieb Sebastian Suchanek: >> Hi everyone, >> >> last night I encountered the following situation: a scheduled backup >> started, using a certain backup pool (a set of tapes). From that pool, >> Bacula (v7.4.4) selected an empty volume X, but since this was not in >> the tapelibrary, Bacula kept asking for it. (Since I was ~250km away, I >> couldn't do that.) However, another volume Y, which was also totally >> empty, would have been available in the tapelibrary. >> >> Basically, I have two question about this: >> 1. Why does Bacula prefer an empty volume which is not available over >> another empty volume that would have been available? > > Because Bacula's idea of available is different from yours or mine. :-) > To sort out the specifics you'd have to share the precise state of the > volumes involved at the time, which is probably not available anymore.
The state is still available because I canceled the abovementioned job: *list media pool=LTO11 Automatically selected Catalog: MyCatalog Using Catalog "MyCatalog" +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------------------+-----------+ | MediaId | VolumeName | VolStatus | Enabled | VolBytes | VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten | ExpiresIn | +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------------------+-----------+ | 14 | SU1102L1 | Full | 1 | 106,528,859,136 | 55 | 1,209,600 | 1 | 12 | 1 | LTO-1 | 2018-05-06 23:50:03 | 0 | | 15 | SU1103L1 | Full | 1 | 114,858,390,528 | 58 | 1,209,600 | 1 | 13 | 1 | LTO-1 | 2018-08-05 21:31:25 | 0 | | 16 | SU1104L1 | Full | 1 | 109,644,788,736 | 54 | 1,209,600 | 1 | 14 | 1 | LTO-1 | 2018-09-02 22:28:53 | 1,128,832 | | 17 | SU1105L1 | Append | 1 | 64,512 | 0 | 1,209,600 | 1 | 0 | 0 | LTO-1 | 0000-00-00 00:00:00 | NULL | | 18 | SU1101L1 | Append | 1 | 64,512 | 0 | 1,209,600 | 1 | 11 | 1 | LTO-1 | 0000-00-00 00:00:00 | NULL | | 19 | SU1106L1 | Append | 1 | 64,512 | 0 | 1,209,600 | 1 | 0 | 0 | LTO-1 | 0000-00-00 00:00:00 | NULL | | 20 | SU1107L1 | Append | 1 | 64,512 | 0 | 1,209,600 | 1 | 0 | 0 | LTO-1 | 0000-00-00 00:00:00 | NULL | | 21 | SU1108L1 | Append | 1 | 64,512 | 0 | 1,209,600 | 1 | 0 | 0 | LTO-1 | 0000-00-00 00:00:00 | NULL | | 22 | SU1109L1 | Append | 1 | 64,512 | 0 | 1,209,600 | 1 | 0 | 0 | LTO-1 | 0000-00-00 00:00:00 | NULL | | 23 | SU1110L1 | Append | 1 | 64,512 | 0 | 1,209,600 | 1 | 0 | 0 | LTO-1 | 0000-00-00 00:00:00 | NULL | +---------+------------+-----------+---------+-----------------+----------+--------------+---------+------+-----------+-----------+---------------------+-----------+ * (Hopefully this works without broken linebreaks...) The job in question actually started on volume "SU1104L1" and when that volume had filled up, Bacula asked for "SU1105L1" instead of using "SU1101L1". Maybe that's because of the lower MediaId of SU1105L1 instead of SU1101L1? >> 2. Is there any way to sort of re-direct an already running job to >> another (available) volume? > > What I do in similar situations is > > 1. purge the volume I want Bacula to use > 2. update the volume status of the volume I don't want Bacula to use to > "Used". > > Sometimes the process has to be repeated because Bacula would still > recycle a different volume than the one I purged for it, but eventually, > after re-setting all volumes to "Used" which Bacula chose, it will end > up using the volume you want it to use. How can I set a volume manually to "used" (and un-set it aftwards)? Best regards Sebastian ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
