Arno Lehmann wrote: > Hi, > > On 5/31/2007 2:41 AM, Doug Breshears wrote: > >> 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, >> > > Not quite... Bacula does not migrate volumes, but jobs. Consequently, > volumes are not marked as 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". >> > > It better would, because Bacula currently has no idea what to do when > multiple copies of the same file from the same job exist. > > >> I took that to mean that the >> original data would be wiped. Maybe it just means the database records?? >> > > It definitely means that. > > >> Is there a way to cause this to happen automatically? >> If not is it safe to just delete the "Volume" files after a migration? >> > > No, you have to delete the corresponding catalog records, too. > > >> Or do we have to manually purge them in the console, then delete? >> > > Yes. Although it might be simpler to leave them and reuse them for > future jobs. > > Arno > Arno, Martin: Thank you both for the help, you are great.
My only issue with leaving them there is file space. If I run out of space on the HD partition due to old migrated jobs, the backup will stop until morning when I am able to fix the problem. Which is what I am trying to avoid. Is bacula smart enough to fix this on its own? I am using 3 pools (daily,weekly,monthly) and I have extended those to the HD File storage as well (daily-file, etc..) so that the migrate jobs could get them on the correct tape pool. The problem this causes is that after a month there will be 3 sets of files that are waiting to be reused but still taking up space. Any Ideas? Doug ------------------------------------------------------------------------- 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
