In response to "Terry Zink" <[EMAIL PROTECTED]>: > Currently my company uses a custom backup solution. While effective, we > are growing out of the point where it is scalable for what we need and > becoming unmanageable. It is also starting to lack features necessary. > > Essentially, it backs up both linux and windows systems. It does > standard dumps (A level 0, then level 1's compared against the level 0 > until the level 1 reaches 50% the level0 size) for linux, and for > windows we use smbclient to grab and tar up specific windows shares > (usually the c$ drive.. yes.. There are many limitations of this heh.) > > I stumbled across bacula awhile back, and it looks great! Looks like it > may do everything I need. (I need to read the documentation a bit more > clearly to determine if it does the 0 and 1's as needed, but I'm sure it > can.) > > The question I'm wondering is.. how well does it work in large scale > environments? > > Our current system, is disk(client server) to disk (backup server) to > disk (big array to back up the backup servers) and then to tape. The > first level of backup servers (what the client server sends the data to) > contains about 22 servers. Currently our system means managing each of > those individually. You see my dilemma. Now, granted bacula could > easily probably just handle them each as 20 or so different SD machines > and the director could manage all 20 or so. At least that's my > understanding. 22 storage devices? Well we're backing up around 800 > servers at least like this. > > My question is... aside from anything being blatantly wrong in the above > statements, can bacula reliably be used to backup 800 different systems > or should I look for a different solution? Every testimonial I see > mentions 30 or 50 clients max...
Wow. That's a pretty big setup. I've never heard of anyone using Bacula for something that size. In theory, it should scale up that big, but you may encounter some scaling issues that nobody else has seen yet. However, Bacula is open source, and (from your email) I get the feeling that you're the type who can help out by submitting helpful bug reports and working with the community -- maybe even submitting patches. The devel team is great. I think if you hit scaling problems putting Bacula into such a huge environment, you'll get great response from the Bacula community to help make it work. > Also, I noticed in the current "limitations" that 4 billion files is > the limit per database? (this would I assume be per director then in > reality if they used different databases?) Actually, it's per-database catalog. This is because most databases use 32 bit int for IDs. You can have multiple databases (what Bacula calls a catalot) per Bacula director, which allows you to get around this. Each catalog can only have 4 billion files. -- Bill Moran Collaborative Fusion Inc. ------------------------------------------------------------------------- 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
