I tried running the command, and got the following error.
Which is logical based on your expectation of corrupted
$ rdiff-backup --check-destination-dir --tempdir
Fatal Error: Bad rdiff-backup-data dir on destination
The rdiff-backup data directory
exists, but we cannot find a valid current_mirror
marker. You can
avoid this message by removing the rdiff-backup-data
however any data in it will be lost.
Probably this error was caused because the first
into a new directory failed. If this is the case it is
safe to delete
the rdiff-backup-data directory because there is no
information in it.
I have actually tried deleting the backup and starting again
a few times now.
Perhaps my poor server does not have the grunt for
$ cat /proc/meminfo
MemTotal: 1026412 kB
MemFree: 14360 kB
The system is running a P4 2.8 Ghz cpu.
Does using the --tempdir command during backup help ?
Is there a problem with running multiple rdiff-backup
jobs from win workstations to the server ? Perhaps that
would be mitigated if I can use the --tempdir address@hidden::/mnt/hda1/temp idea above
Date: Thu, 5 Feb 2015 07:52:02 +0000
Subject: Re: [rdiff-backup-users] backup keeps failing
I doubt is to do with SSH. My guess is that your (C) backup
repository was already somehow corrupted on the destination.
So when you tried to run another session to it, rdiff-backup
automatically started a regression to get back to a safe
starting point for the backup. In itself this can take a
very long time, and also regressions of larger archives can
require a *lot* of temporary space; if this runs out then
the backup might hang. I suggest running something like this
on the server:
rdiff-backup --check-destination-dir --tempdir
On 05/02/2015 04:54, Stephen
I have 3 windows 7 computers scheduled to perform
an rdiff-backup over ssh to a microcore linux server
each day at 6pm.
Backups are triggered on all 3 computers at 6pm by
windows task scheduler each day.
I'm using volume shadowing to create a snapshot
of my files, which is needed for open outlook pst
Here's an example.
Win 7 PC (A) backup is under 1 gb and works each
day. Takes about a minute.
Win 7 PC (B) backup is under 2 gb and works each
day. Takes about two minutes.
Win 7 PC (C) backup is 45 gb and takes more than 12
hours to complete. I ran the backup last night at 6pm
and it was still running this morning at 11am. I
cancelled the backup, and ended up with a corrupted
Is this to do with SSH slowing down the process ?
I hope to find a solution to this problem, as
another system I'd like to use rdiff-backup on has
over 250gb of data to check.
Any suggestions are greatly appreciated.