Hello, we're planning a fairly large Bacula backup environment (~500
clients). The environment will be a purely disk based backup environment
and I'm trying to determine the "best" way to configure the
devices/pools/volumes so we can have:
* a large amount of concurrent backups
* maximum flexibility in changing individual client backup schedules
without having to hold onto huge volumes for an extended period of time
How are other large installations managing their devices/pools/volumes?
I've read of some folks creating new pools/devices for each of their backup
jobs so each job is in it's own volume and you can have lots of concurrent
jobs while maintaining flexibility in client retention periods without huge
volumes. Is this viable for a large installation?
Any tips or pointers are appreciated.
Thank you,
Romeo
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
