BackupPC-users

Re: [BackupPC-users] Interrupted rsyncd backups on Backuppc4 and rsyncTMP.XXXX files, these files never get cleaned out.

2017-01-31 17:54:26
Subject: Re: [BackupPC-users] Interrupted rsyncd backups on Backuppc4 and rsyncTMP.XXXX files, these files never get cleaned out.
From: Adam Goryachev <mailinglists AT websitemanagers.com DOT au>
To: backuppc-users AT lists.sourceforge DOT net
Date: Wed, 1 Feb 2017 09:53:40 +1100
On 01/02/17 07:45, Mike Dresser wrote:
> One thing I've noticed on backuppc 4.0.0alpha3 is that if an rsyncd
> backup is interrupted(server crash, someone rebooted the server, etc),
> it leaves behind a rsyncTmp.pid.y.z file in the main host directory,
> like ./hostname/309/rsyncTmp.8869.0.4
>
> On the next backup, this file gets copied to 310, but never gets
> deleted.  If you back up a 200gb file and it fails, and then do another
> 10 incrementals you'll now have 2 TB of disk space used that will never
> come back since each new backup copies the old backup as a starting
> point.  If a future backup fails, you'll now have multiple rsyncTMP files.
>
> I had a server with 22TB disk space that had an extra 16 TB of files
> like this...  Couldn't figure out why my pool stats were nothing like
> what the disk actually had.
>
> Suggestion would be to have the copy command that runs when a backup is
> started delete any leftover files that are named like that.
>

Thank you, this is so true...
I just found:
client 1: 20 x 1125MB
client 2: 38 x 8639MB
client 3: 20 x 3565MB
client 4: 19 x 8639MB
client 5: 97 x 100MB
client 6: 42 x 34MB
client 7: 7 x 4101MB
client 8: 73 x 124MB

Total: 635GB

Ouch..... Considering my backup server is reasonably stable, uptime is 
currently 99 days...

PS, would this work better is the rsyncTmp filename was pre-determined 
based on the file being transferred? This could also lead to some 
starting point for continuing a partially transferred file. eg, a 4GB 
file is backed up, and is modified daily. One day, there are a lot of 
changes, or some other network issue that interrupts the backup. Why not 
continue the transfer the next day instead of starting from the 
beginning. The argument that it will corrupt the backup is moot, since 
the tmp file is never actually "part" of the backup files.

Regards,
Adam

-- 
Adam Goryachev Website Managers www.websitemanagers.com.au

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

<Prev in Thread] Current Thread [Next in Thread>