On 08/19/2010 08:57 AM, Neil Benn wrote:
Hello,
I'm trying to use rdiff backup to backup from my work server to
a hard drive on my home network (needed for audit purposes - I know it
sounds crazy but there you go!). The network is very slow however it
seems that rdiff backup starts
On 08/11/2010 08:03 PM, Robinson, Eric wrote:
I've never tried using --compare-hash.
There has been a lot of talk in the past about how to
verify backups and really for me the only full proof solution
is to restore somewhere and compare (diff) against original.
Unfortunately, I am talking
On 08/12/2010 03:55 PM, Robinson, Eric wrote:
You mean the rdiff-backup version? It's 1.2.8 on both servers. But does
it to an in-place comparison? If I understand the man page correctly, it
first copies the data from the dest to the source and then compares it
there?
I'm also running 1.2.8 on
On 08/10/2010 04:16 PM, Robinson, Eric wrote:
It's quiet.
Yeah, too quiet. Gives me the willies.
Me, too.
--
Eric Robinson
-Original Message-
From: rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org
[mailto:rdiff-backup-users-bounces+eric.robinson=psmnv@nongnu.org]
On 12/05/2009 01:28 PM, Alex P wrote:
Hi
This file has failed in the initial backup and not it fails everytime
UpdateError usr/bin/pstruct Updated mirror temp file
/mnt/backup/system/usr/bin/rdiff-backup.tmp.17 does not match source
Normally when you get this error it means that the source
On 12/04/2009 07:44 AM, elemental code wrote:
Hi,
I'm backuping a host through an unstable link. So, each time the ssh
connection get broken and rdiff-backup can't finish the backup.
When I restart it, I get Previous backup seems to have failed,
regressing destination now and all restart to
Dean Cording wrote:
I've come across an issue with the way that rdiff-backup ensures that only one
server is accessing a backup dataset.
...
Recently I had a backup fail, probably because of a network outage. All
subsequent backups refuse to run because rdiff-backup believes the failed rdiff-
Kilian Lackhove wrote:
Hello list,
ive been using rdiff-backup for 2 years now, but this evening it stopped
working:
Yesterday i deleted files from the backup-folder (i know, wasnt too smart), I
ran rdiff-backup this morning manually and it repaired the backup (it wrote
zeroes i think) So
Chris G wrote:
Some very old stuff I want to keep but not others.
E.g. I have a ~/tmp directory which gets backup up, it would be nice
to be able to clear out ~/tmp *and* the backups of it. I do want it
to be backed up but there's a fair chance that I don't want to keep
the backups for long.
tala...@tlen.pl wrote:
Hello, I have situation like this:
Soruce folder (300 GB, Windows share mounted by cifs)
Backup folder (350 GB, backup + some increments, 500 GB disk quota)
I'm doing rdiff-backup source backup and everything is ok but unfortunetly I didn't do protection in my backup
Michael Ross wrote:
My recent backup failed with a no space left on device error
(rdiff-backup 1.2.7 on Linux). It was running as root, so the partition
(which contains nothing but the backup) is completely full. Therefore, I
can't run the suggested --check-destination-dir command because it
Giorgio wrote:
Hi,
I have to perform a backup over the Internet, using rdiff-backup. The
scenario is as follows:
- Backup activities can only run at night, when no one is using the files.
- The connection is ADSL, so it is pretty slow.
- The turnover size is around 100 MB per day, so this
Brad Templeton wrote:
I noticed several postings on this list about switching to rdiff-backup
from a plain copy (from rsync) using --force
However, my tests show that when you do this, you get an rdiff-backup
repository that is a copy of the current state of the directory, but
the old directory
chuck odonnell wrote:
i have a fairly large repository that i back up using something like:
$ rdiff-backup remote::/m /backups/remote/m
but now i want to add some other folders that are above /m, e.g.:
$ cat include_file
/m
/etc
/usr/local/etc
$ rdiff-backup --include-globbing-filelist
Neil Van Dyke wrote:
I'm a user of the Debian packagings of rdiff-backup, and have been bit
hard as a result of Debian's version choices and the
non-backward-compatible protocol changes between 1.1.5 and 1.1.12.
Currently, Debian stable contains a development version of
rdiff-backup (which in
[EMAIL PROTECTED] wrote:
On Mon, 9 Jul 2007, Joe Beda wrote:
2) Change the main flow of the backup. Instead of modifying the dest
tree in place, instead write forward looking increments out. When all
of the forward increments are written out then patch the mirror tree
to move it forward. Care
Charles Duffy wrote:
Frederik wrote:
IOError: CRC check failed
So I see no way to recover any of the increments.
In over 12,000 rdiff-backup sessions, I have yet to encounter that issue
or anything like it (in terms of unrecoverability).
I'm with Maarten -- check your hardware.
Joshua N Pritikin wrote:
On Mon, Apr 23, 2007 at 05:19:32PM -0600, Steven Willoughby wrote:
I think it is possible to combine rdiff-backup and LVM snapshots to
have incremental backups on the same machine without having two full
copies of the data set.
It's not even very tricky
Hello everyone,
I think it is possible to combine rdiff-backup and LVM snapshots to
have incremental backups on the same machine without having two full
copies of the data set. What follows are some instructions on how I
think this would be done:
First, set up LVM such that you have
Mark Williamson wrote:
Mmmm. I'm by no means an rdiff-backup expert, but I wouldn't expect backing
up a Linux partition to a FAT filesystem to work entirely smoothly: FAT
doesn't support all the semantics that a Unix-style filesystem requires in
order to work properly. Since rdiff-backup
Baldur Norddahl wrote:
Hi,
I want to use rdiff-backup with my Postgresql database. The problem is
that the tool refuses to backup files that are changing.
The database is live and modifying the database files during the
backup. This is fine, because I am using the PITR (point in time
Ian Thurlbeck wrote:
Dear All
I currently backup a set of directories to a remote server. After working
fine for 9 months, I've found that I'm now getting errors (possibly
since I
upgraded to 1.1.9?):
Sending back exception of type exceptions.AssertionError:
File
Hello everyone,
I have been using rdiff-backup at the company where I work to back
up about 500 GB of data. In order to simplify management of this data I
needed to split that one large archive into lots of smaller archives
while preserving historical increments. I wrote a quick and dirty
23 matches
Mail list logo
