hi,
i'm using a synology ds411 nas as backup target. the processor on this
device is very slow, so i don't get a transfer rate of more than 5 mb/s
when accessing it via ssh (cpu-bound). this makes backups for my 500GB
data partition rather painful.
i'd therefore like to interrupt and later
2012 13:34
An: 'tim'; rdiff-backup-users@nongnu.org
Betreff: Re: [rdiff-backup-users] resuming initial backup
Rdiff-backup takes any existing data as a base in a target dir that has to
be initialized, so just remove the rdiff-metadata from the target, while
keeping the data that has already
Not that I know of. Because of the complexity of the underlying archive,
rdiff-backup does not like a failed or interrupted previous backup
attempt at all and tries to remove one if it finds it. Otherwise the
risk would be that you corrupt the archive and lose your data history.
Although it
Hello,
If you need to store off the box you are rdiffing from then rdiff to a
local directory and then rsync that over.
Cheers,
Neil
On 20 May 2012 12:48, Dominic Raferd domi...@timedicer.co.uk wrote:
Not that I know of. Because of the complexity of the underlying archive,
rdiff-backup
Betreff: Re: [rdiff-backup-users] resuming initial backup
Rdiff-backup takes any existing data as a base in a target dir that has to
be initialized, so just remove the rdiff-metadata from the target, while
keeping the data that has already been copied :-)
Cheers
David
-bounces+mail=dkriesel@nongnu.org
[mailto:rdiff-
backup-users-bounces+mail=dkriesel@nongnu.org] Im Auftrag von
Dominic Raferd
Gesendet: Sonntag, 20. Mai 2012 13:54
An: rdiff-backup-users@nongnu.org
Betreff: Re: [rdiff-backup-users] resuming initial backup
What exactly needs to be deleted
On 20/05/2012 13:02, D. Kriesel wrote:
The whole history will be lost when following this procedure, which renders
it inappropriate for backup repositories whose history actually exists.
However, if I get Tim right, he is talking about an interrupted _initial_
backup run. In this case, giving
thanks for your explanations ... i was a bit confused to see a lot of
Processing changed file messages of files which have already been
transferred ... could be that checksumming these files is a performance
bottleneck on the NAS device ... so doing the rdiff-backup locally and
uploading via
hi david,
However, if I get Tim right, he is talking about an interrupted _initial_
backup run. In this case, giving up the entire history obviously does not do
any harm. Without any metadata (i.e. the rdiff-backup-data subfolder), afaik
a forced rdiff-backup run will take whatever there is
