Hi, 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.
Would you regard that as a bug? 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 -- Collax GmbH . Burkheimer Straße 3 . 79111 Freiburg . Germany p: +49 (0) 761-45684-28 f: +49 (0) 761-45684-10 www.collax.com Geschäftsführer: Boris Nalbach AG München HRB 158898 . Ust.-IdNr: DE 814464942 \ "Womit verhüten Emanzen - mit dem Gesicht." \ Oskar Lafontaine ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users