Hi,
> You're talking about migration, basically, which is a planned future > feature. There's been some discussion just recently among > developers on > how to implement migration and an extended spooling > capability using the > same code. example: my backup get's taken today and will stay on-disk until 20050930. backup will be copied off to tape tonight by some kind of schedule. but a recover started tomorrow should still access the disk version. (let's ignore the more annoying details like flushing the oldest or least accessed backup first and automatically retrying the disk->tape copy until it's really, really done.) :) is all this really plain migration? migration to me means that the backup will move from disk to tape at some time, without being preserved and accessible on-disk any further. florian ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
