On Mon, 29 Oct 2007, Michael Lewinger might have said: > Hi Mike, > > Yes, I agree that Bacula's method for upgrading an incremental backup to > full if no full backups are found is a good feature (expected though) but it > does not work the way I'd like it to. For instance there is an explicit > "ignore fileset changes" options to circunvent a methodic upgrade-to-full > when changing fileset - why such an option ?. If we're calculating MD5 > signatures to each file, in this case, I'd expect Bacula to transfer only > "NEW" files and "replenish" the old full backup with the new data according > to the new fileset - more or less "add to the jobid XXX those files as > they're new". Bend the rules a little, it is not like bacula can be used by > the average home user. Transferring the WHOLE set of data again is the easy > way to say "full is full, and data transfer is cheap", which is not always > the case. > > It seems to me that in bacula's restore you can choose both by point in > time, by most recent full backup, and particular folders/files, so > > Finally, regarding your question - eventually I'm reacting to it. I'm not > sure that I understand the TSM "perpetual" feature, maybe the name is > misleading. RTFM 4 me will do it, but until then - is there no "parallel" > feature in Bacula, or a procedure for emulating this feature ? > > Michael > > On 10/29/07, Mike Eggleston <[EMAIL PROTECTED]> wrote: > > > > On Mon, 29 Oct 2007, Michael Lewinger might have said: > > > > > Hi Mike, > > > > > > It looks all things are covered in Bacula: retention times, incremental > > > backup. But then I'm not a TSM expert. > > > > > > Michael > > > > > > On 10/29/07, Mike Eggleston <[EMAIL PROTECTED]> wrote: > > > > > > > > I like bacula and what it does for me (thank you development team). > > > > One issue I have is not really bacula, the issue is the long time > > > > required to write backups to tape. Is there anything in bacula like > > > > TSM's perpetual full where I can see the most current files from the > > > > client in the 'restore' command, files removed the client are kept > > > > for a specific number of days, and only the files that have changed > > > > during the night are written to backup tape ad infinitium? > > > > The big difference I can see is the perpetual full. Bacula will upgrade > > a backup level to Full if no other Full is found for the client. TSM > > will backup any files you tell it to regardless of backup level, and > > TSM will keep the file for a certain amount of time (30 days, etc) after > > the file is deleted from the client. TSM also knows what the most current > > files for a client are, so like 'restore' in bacula you can choose which > > files to load back to the client. You do not have to select a file by > > job id. You can ask for a list of 'active' and 'inactive' versions of a > > given file or wild card and like bacula's 'restore' you can choose which > > files to load back. > > > > The biggest difference for what I'm wanting between bacula and TSM is > > the 'perpetual full'. Just backup the files from the client and let me > > choose which files by date to restore (bacula does the latter). > > > > I greatly agreed with the idea of Full/Differential/Incremental backups > > (levels 0/1/2 from BSD) until I started with TSM. The TSM method, once > > you understand what it is doing, works very well. I was very skeptical > > at first of TSM until I had used it a while. The idea is similar to CVS > > or RCS. Only the files that have been modified get new version numbers. > > > > Does that make sense or am I rambling?
The perpetual backup, maybe that's only how I think of what TSM does, backups up a file from the client to the server and keeps a TSM admin defined (even per client defined) number of versions of that file before the oldest version falls off the back. If the file is deleted on the client, the TSM server keeps at a minimum the last, most current version of the deleted file for X number of days before that file falls out of the TSM server. The first time a client is backed up, all the files defined for that server are backed up. Each time after unless the admin or some schedule specifies, only changed files are copied. There is no need for a Full. Though some sites do a periodic or monthly full, you can setup the TSM server for incremental forever. My issue right now is that my tape drive is so slow that I want only the incrementals and not the fulls. Mike ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
