I have a 1.2 TB filesystem where I store backups. Thanks to pooling and compression features in BackupPC , I have almost 14 TB of data there - very nice:
1975 full backups of total size 13813.27GB (prior to pooling and compression) Unfortunately, it doesn't scale very well in terms of performance - you may see this thread on linux-fsdevel list for more info: http://marc.info/?t=120333985100003&r=2&w=4 The main problem seems to be hard disk seeks caused by a great amount of hardlinks. I.e., removing anything from the drive takes ages. I don't even remember when the "trash" directory contained fewer subdirectories than 10, not to say when it was empty. Also, the BackupPC_nightly runs virtually all day - although I use this setting: $Conf{BackupPCNightlyPeriod} = '16'; $Conf{MaxBackupPCNightlyJobs} = '1'; I wouldn't like to increase $Conf{MaxBackupPCNightlyJobs}, as then seek time is even larger and it affects other tasks, like new backups or BackupPC_trashClean. Increasing $Conf{BackupPCNightlyPeriod} is also impossible with the current BackupPC design, but technically, it should be doable. After all, there are 16 * 16 * 16 = 4096 cpool subdirectories. What changes would be needed in BackupPC to allow $Conf{BackupPCNightlyPeriod} to be bigger than 16? -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
