Item n: Option to purge job on successful migration Origin: Blake Dunlap (bl...@nxs.net) Date: 07/06/09 Status: Request
What: It would be nice if there was an option to purge the source migration job in addition to just the file records whenever it is completed successfully. Why: When trying to maintain a pool of scratch volumes, which are reusable once jobs are migrated off, but must be maintained until they are clean, is not a good use of a low retention time based pruning. Once all the jobs are successfully migrated, the volume is immediently opened for reuse, thus requiring fewer volumes in the pool. Notes: I realize this is scriptable, but its much cleaner to have the native functionality, and more maintainable / less prone to failure conditions. I have accomplished this internally in production (attached), and it seems to be working well, but I am not sure how safe my implementation is, as I am not very familiar with the code base at the moment. It probably should also check to see if any volumes have been fully purged in the process and mark them so. The reason for this format is preference to see any positive non specific internal changes included in mainline whenever possible, and this format serves well as both a request, and a suggestion.
bacula-3.0.1-migratepurgejob.patch
Description: bacula-3.0.1-migratepurgejob.patch
------------------------------------------------------------------------------
_______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
