> The most important thing is probably what amount of data you expect from > each machine, and how much of it changes. Assuming a short backup time > window and expecting lots of changed files from many clients might force > you to implement more complicated schedules than you'd might wish (for > example four groups of hosts to have the full backups on four separate > weekends).
Thanks Arlo. Yes, I probably should have mentioned a general amount of data. We probably have between 4-5 TBs of data across the machines. Some of this may not be backed up and can be filtered out. At the moment, the only other product we have looked at is Retrospect. While it has worked ok, it has not been reliable and has tended to crash when trying to back up some clients. We'd essentially like to mimic the same type of setup that Retrospect allows with tape sets where when the set gets big enough, you "archive" it and then declare a new tape set. I have just begun to look at the technical details of Bacula so I can't say if it works in a similar manner. --tom ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
