> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:bacula-users- > [EMAIL PROTECTED] On Behalf Of Kern Sibbald > Sent: Friday, November 25, 2005 2:58 PM > To: [email protected] > Subject: [Bacula-users] Fwd: Feature Request > > Hello, > > I am forwarding this to the list because it is a very interesting feature > request (a big project too), and because it is very similar to the request > submitted by Ross Boylan. My question to Ross and Ray (and others), is: > are > the two requests compatible? and if so, what would the wording be for a > single request? > > Thanks ... >
In a very abstracted way these two could be classified together. Simply put the ability to delete objects after a specified time. That is the common thread. I acknowledge my request is pretty major and I realize it will take a lot of work and time to see it through fruition. I however feel the end product will rival the big enterprise backup software. It's more of a big picture of where bacula could go. I also see Daniel Amkreutz is thinking along the same archiving line. Enterprise class storage software (ie Legato) has an archiving module which will allow you to remove files from a filesystem after they have been moved to tape and verified. I don't feel this part is a stretch. I am going to be attempting getting this behavior working using scripts to create file lists which will be kicked off as run-before/run-after scripts. Needless to say it's pretty sloppy to piece it all together and test. Once archiving is implemented it can be combined with migration to implement the second part of my request. This is a more general idea of what bacula could become. Once these are combined together you have the platform to control your data automatically from the time it is written to disk to the time it is archived for 30 years. It also allows storage admins to configure their environment to maximize their hardware investments. It's feasible that bacula could control what media type a backup is done based on some rules an administrator created (ie size, type of data, age). I don't want anyone to get overwhelmed with this idea. It's just my idea of what bacula could become. Maybe a version 2.0 goal? I think the archiving is a major piece that bacula is missing now and migration on some level will be showing itself in bacula in the not too distant future. Please let me know if you agree/disagree or need more examples of how this pieces together. Ray ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
