On Tuesday 06 March 2007 21:23, Brian Debelius wrote: > Kern Sibbald wrote: > > On Tuesday 06 March 2007 18:55, Brian Debelius wrote: > >> Item n: Implement an 'Append Period' > >> Origin: Brian Debelius (bdebelius @ intelesyscorp dot com) > >> Date: 06 March 2007 > >> Status: Submitted > >> > >> What: Implement an 'Append Period'. An append period is a window of > >> time after the last job written completes that still allows the tape to > >> be appended. After the window closes, no more appends would be allowed. > >> > >> Why: While VolumeUseDuration limits the amount of time a media can be > >> used after the first write, this limits the amount of time that jobs can > >> be appended after the last write. > >> > >> Notes: The time window would be specified in minutes, hours, days, > >> weeks, years. The default window would be an infinite allow append, in > >> which the media will always allow appends until the media is filled. > > > > Before I add this to the projects list, you need to do two things: > > > > 1. Format it the same way that *all* the projects are currently formated. > > > > 2. Your Why clause is really a continuation of the What, so you need to > > provide some reason why we might want to implement this -- off of the top > > of *my* head, I don't immediately see one. > > 1. Okay. > > 2. I come from the Veritas world. I gave up after the current Symantec > Backup Exec11d mess. Veritas has what they call an Overwrite Protection > Period, which does what I described. I do not have a need to limit the > length of time that a volume can be written to. Maybe it is just what I > am used to from using Backup Exec. Maybe I need to get used to the > Bacula way.
It seems to me that "Overwrite Protection Period" already exists in Bacula -- it is just the Volume Retention Period isn't it? > > So what would the bacula way be to write a set of jobs to a volume, then > wait some period of time, and then write more jobs to another volume? I'm really having a problem understanding the utility of writing to a volume then waiting some period of time and writing to another volume. If you want to stop using the volume after some period, that is simply the Volume Use Duration -- it seems to me. > I > guess more pools would be an option, write some jobs to one pool, then > write some jobs to another, but that seems more complicated. > > Your thoughts? I don't really understand the problem, or precisely what is missing in Bacula. Things may be a bit different from Backup Exec, but it seems to me that the basic functions already exist. Regards, Kern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
