rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] rdiff-backup reliability ad lzop compression


From: dean gaudet
Subject: Re: [rdiff-backup-users] rdiff-backup reliability ad lzop compression
Date: Sun, 29 Jan 2006 13:13:54 -0800 (PST)

On Fri, 27 Jan 2006, roland wrote:

> some "real world" experiences? ('.....i´m backing up 2 TB daily and 
> never had a problem.....')

it's not 2 TB by any means... but these are the average daily stats for 
/home backup on my shell server.

--------------[ Average of 32 stat files ]--------------
ElapsedTime 13852.59 (3 hours 50 minutes 52.59 seconds)
SourceFiles 1244847.15625
SourceFileSize 126665014885.0 (118 GB)
MirrorFiles 1243889.65625
MirrorFileSize 126329389861.0 (118 GB)
NewFiles 1663.78125
NewFileSize 490312504.406 (468 MB)
DeletedFiles 706.28125
DeletedFileSize 186038110.812 (177 MB)
ChangedFiles 11117.75
ChangedSourceSize 11392924536.5 (10.6 GB)
ChangedMirrorSize 11361573906.6 (10.6 GB)
IncrementFiles 13503.6875
IncrementFileSize 348486468.125 (332 MB)
TotalDestinationSizeChange 684111491.594 (652 MB)
Errors 0

so that's avg of 652MB for a daily inc on a 118 GB /home partition.

it occurs over dsl (6mbps down 768kbps up) ... and the backup server is an 
old p3 750 with slow raid5.


> regarding diskspace, there is one idea coming to my mind:
> 
> what about storing _all_ of the backup data compressed and adding a 
> layer of "realtime compression/decompression" - i.e. instead of only 
> gzipping the data in rdiff-backup-data subdir, why not compressing the 
> data in "destination_directory", too ?

maybe you could do this with a block compression layer below the 
filesystem... dunno if there are any of them which are writeable though.

-dean

reply via email to

[Prev in Thread] Current Thread [Next in Thread]