> when manually recycling a (used) volume with > "update volume=xxx VolStatus=Recycle" > this volume will be accepted for overwriting. Nonetheless, Jobs that have > been written to that volume will NOT be removed from the catalog. This > results in invalid data, as the catalog will still contain data about > volume > content that is no longer there.
I see "update volume" command as an "expert tool" that does a spesific requested operation at an "atomic" level, it updates a requsted volume attribute to requested value. So, I wouldn't call this operation as "manual recycle" like you did, it's not supposed to do anything but to update volume status. To force a recycle I would consider either reducing the volume retention period, and then applying prune, or using purge (be cautious with it!) > Would you regard that as a bug? > I don't. > Or is it a PEBKAC, as I should not use the update command to recycle > volumes? Or ist it "just wait for these jobs to expire via their retention > period"? Any recommendations on how to handle these cases? > > dbcheck is not able to find these jobs, btw; they look absolutely valid > in the database, except for the fact that possibly two entries exist that > point to the same region on a tape. > > Thx/best regards > Bastian Friedrich -- TiN ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
