Hey, all!

I've been looking at setting up amanda as a backup solution for a fairly large environment at work and have just stumbled across backuppc.  While I love the design and scheduling methods of amanda, I'm also a big fan of incremental-only reverse-delta backup methods such as that used by backuppc, so now I'm wondering...

How big can backuppc reasonably scale?

The environment I'm dealing with includes around 75 various servers (about 2/3 virtual, 1/3 physical), mostly running Debian, with a few machines running other linux distros and maybe a dozen Windows machines.  Total data size that we want to maintain backups for is around 70 TB.  Our current backup system is using Tivoli Storage Manager, a commercial product that uses an incremental-only strategy similar to backuppc's, and the daily backup volume is running around 750 GB per day, with two database servers providing the majority of that volume (400 GB/day from one and 150 GB/day from the other).

Is this something that backuppc could reliably handle?

If so, what kind of CPU resources would it require?  I've already got a decent handle on the network requirements from observing the current TSM backups and can calculate likely disk storage needs, but I have no idea what to expect the backup server to need in the way of processing power.



_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Reply via email to