All, Thanks for all the input. I'm starting to fully understand how BackupPC scheduling is working now. My apologies for not stating that I was/am using rsync as it is the only choice that makes sense =)
On Fri, Feb 19, 2010 at 12:15 AM, Craig Barratt <cbarr...@users.sourceforge.net> wrote: > Mike, > >> Backup# Type Comp Level Size/MB Comp/MB Comp >> Size/MB Comp/MB Comp >> 0 full 3 78446.6 45871.8 41.5% 258032.2 >> 155715.6 39.7% >> 2 incr 3 276482.0 165123.8 40.3% 143.0 70.3 >> 50.8% > > Notice that the first full is 78GB, but the incr is 276GB. > > I would guess you added shares, directories or changed excludes after the > full, but before the incremental. Or a large amount of data was added > between these two backups. > >> 3 incr 3 900.7 530.7 41.1% 964.7 469.5 51.3% >> 4 incr 3 113.5 2.7 97.6% 218.0 30.8 85.9% >> 5 incr 3 73.4 6.1 91.7% 194.8 32.2 83.5% >> 6 incr 3 304.3 172.2 43.4% 1735.9 944.0 45.6% >> 7 incr 3 275955.3 165019.1 40.2% 1337.0 >> 658.0 50.8% >> 8 incr 3 520.4 249.4 52.1% 672.7 282.5 58.0% >> 9 incr 3 502.9 243.5 51.6% 587.6 264.1 55.1% >> 10 incr 3 116.8 3.7 96.8% 201.5 24.3 88.0% >> 11 incr 3 14.0 3.0 78.7% 244.3 32.8 86.6% >> 12 incr 3 127.1 5.3 95.9% 82.2 22.3 72.8% >> 13 incr 3 276989.9 165643.4 40.2% 329.3 40.7 >> 87.7% >> 14 incr 3 275957.9 165146.0 40.2% 1503.5 >> 615.1 59.1% >> >> My question is, why did backups 13 and 14 backup all that data? Same >> with 2 and 7 for that matter. >> >> Here's the times for the first few backups to give you an idea of the >> time it's taking: >> >> Backup# Type Filled Level Start Date >> Duration/mins >> Age/days Server Backup Path >> 0 full yes 0 2/9 07:29 1767.6 9.0 >> /backup/BackupPC/pc/fileserver/0 >> 2 incr no 1 2/10 23:59 1124.8 7.3 >> /backup/BackupPC/pc/fileserver/2 >> 3 incr no 3 2/11 19:00 68.3 6.5 >> /backup/BackupPC/pc/fileserver/3 >> 4 incr no 4 2/12 01:00 73.6 6.3 >> /backup/BackupPC/pc/fileserver/4 >> 5 incr no 5 2/12 07:00 73.9 6.0 >> /backup/BackupPC/pc/fileserver/5 >> 6 incr no 6 2/12 13:00 102.5 5.8 >> /backup/BackupPC/pc/fileserver/6 >> 7 incr no 1 2/12 19:00 1097.0 5.5 >> /backup/BackupPC/pc/fileserver/7 > > You can see that incrementals 2 & 7 are level 1 (4th column). Since the > full (#0) has a much smaller set of files, those level 1 incrementals > are backing up a lot of data, and a lot more than the original full. > > Bottom line: you need to do a full backup. It's going to take a while > (but no longer than the incrementals). After that, the future fulls > and incrementals will be a lot faster. > > Doing a full backup is good practice if you make a significant > configuration change that significantly changes what is being > backed up, or add a large amount of data. > > Craig > Craig, I see exactly what you're saying. What I'm thinking happened was that I was doing testing on one directory and ran the full, and then added the rest of my directories after. Using the explanations earlier about how increment levels and fulls relate, it makes perfect sense. Thanks again! Regards, Mike ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
