>>>>> On Wed, 30 May 2007 17:41:09 -0700, Doug Breshears said: > > Hi All, > > I have successfully upgraded to version 2.0.3 and have implemented a > migration scheme where backups are first backed up to "File" storage and > then a migration Job is called to migrate them to tape. > > This will solve the issue of forgetting to insert tapes and having the > backup jobs run during the day, interrupting all manner of processes. > > The one problem I am having is that the "Volumes" on the file storage > are not getting removed after the migration is complete. > > The test runs that I have done verify that the volume does not get > migrated again so it is marked as already migrated, but the docs that I > read (www.bacula.org/dev-manual/Migration.html) say that "The original > Job is purged of its file records". I took that to mean that the > original data would be wiped. Maybe it just means the database records?? > > Is there a way to cause this to happen automatically? > If not is it safe to just delete the "Volume" files after a migration? > Or do we have to manually purge them in the console, then delete?
You must use the delete command from the console (which also purges the jobs) before any OS commands that delete the volume files. However, why do you need to delete them? It might be better to prune or purge the volumes (i.e. remove all the job records) so they can be recycled. Alternatively, give the volumes appropriate retention periods so the purging happens automatically. __Martin ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
