On Mon, 25 Sep 2006, Ryan Novosielski wrote: > I'd like to ask a side question (which I hope will not offend the > original author: I know that in my former backup software (HP Data > Protector), there was some value to keeping jobs longer than files.
Primarily "smaller databases" > You would still have the location of the job saved, and know where it > was on what tape. This is Bacula's default setup. > If you couldn't restore file by file, at least you knew where > to start to restore that listing and you'd know what backup to restore > if you wanted to go ahead and restore the whole thing. Is that true of > Bacula, or must you do a bscan to do anything useful? Bacula goes one better and also saves a catalog at the end of the job. I decided that the odds of ever wanting a full restore from an old dataset are slim vs the chances of wanting a particular file. MySQL can easily handle the load being thrown at it as long as there is enough ram in the database machine, so I keep file records as long as job ones. AB ------------------------------------------------------------------------- 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
