I have a problem that a repository which 3 days ago occupied 26G has
mushroomed to 44G. The reason is that one night the backup seems to have
gone badly wrong, thinking the source data was missing, then the next
night it was all okay again - so it generated lots of diffs for files
that had
bart wrote:
What directories can be excluded when doing a full linux backup image which
could be restored and run on a new blank disk?
A more appropriate package for this purpose is mondo -
http://www.mondorescue.org - if it supports your distro.
Dominic
Wei, Xiaohai wrote:
I want to backup a whole linux system to windows for restoring the
system from windows to linux later.
I successfully installed native rdiff-backup on windows xp and it can
backup linux data to windows folder.
But it seems failed if there is symlink in the linux system.
Wei, Xiaohai wrote:
Dominic, thanks for your reply.
I have a solution to recover from disaster which can restore the
system to factory default. After that, I want to restore the system to
latest or earlier version. I can achieve it in linux - linux way. I
can back up the whole system to a
Ben Tucker wrote:
I had a machine fail in the midst of backing up a couple weeks ago and
ever since I have been unable to get it to successfully backup.
rdiff-backup --check-destination-dir runs without error, but then
running the actual backup command results in an exception. I'm
running 1.2.8
Josh Nisly wrote:
One of my clients encountered an interesting bug in rdiff-backup -
under certain conditions, if a file changes while it is being backed
up, rdiff-backup throws an unhandled exception...
I can't help on the main problem, but as a workaround (and a better
approach anyway),
Josh Nisly wrote:
One of my clients encountered an interesting bug in rdiff-backup -
under certain conditions, if a file changes while it is being backed
up, rdiff-backup throws an unhandled exception...
I can't help on the main problem, but as a workaround (and a better
approach anyway),
Ben Tucker wrote:
I had a machine fail in the midst of backing up a couple weeks ago and
ever since I have been unable to get it to successfully backup.
rdiff-backup --check-destination-dir runs without error, but then
running the actual backup command results in an exception. I'm
running 1.2.8
Piotr Karbowski wrote:
On Mon, Sep 21, 2009 at 2:02 PM, Matthew Miller mat...@mattdm.org wrote:
On Mon, Sep 21, 2009 at 01:58:11PM +0200, Piotr Karbowski wrote:
local rdiff-backup dir with remote server but how? If I will use for
example rsync it still need to check whole files for
Piotr Karbowski wrote:
On Mon, Sep 21, 2009 at 8:21 PM, Dominic Raferd domi...@timedicer.info wrote:
Piotr Karbowski wrote:
On Mon, Sep 21, 2009 at 2:02 PM, Matthew Miller mat...@mattdm.org wrote:
On Mon, Sep 21, 2009 at 01:58:11PM +0200, Piotr Karbowski wrote
simsam wrote:
My experience with Mozy was not good. I installed MOZY FREE Backup software on
my computer as per their instructions. After installation, my computer kept
freezing and it CRASHED my computer. Thanks god I have one additional backup of
data. I need storage space, but a more
Piotr Karbowski wrote:
On Tue, Sep 22, 2009 at 10:51 AM, Dominic Raferd domi...@timedicer.info wrote:
Piotr Karbowski wrote:
On Mon, Sep 21, 2009 at 8:21 PM, Dominic Raferd domi...@timedicer.info
wrote:
Piotr Karbowski wrote:
On Mon, Sep 21, 2009 at 2:02 PM, Matthew
Piotr Karbowski wrote:
So best will be using duplicity to make local backup and run rsync to
send new files (diffs) to remote server. and if backup will be TOO big
just mv backup backup_old and start new backup (every 4 weeks for
example)
I think so. There is a duplicity mailing list where
prateekmoturi wrote:
Hi i am getting the following error messages when i am trying to backup.
I am using the rdiff-backup 1.2.8.
Can anyone please help me to find the solution for the following error...
Traceback (most recent call last):
File /usr/bin/rdiff-backup, line 30, in ?
Jakob Unterwurzacher wrote:
in bash:
#!/bin/bash
for i in `seq 1 $((RANDOM%100))`; do /bin/true; done
But you should make sure that $RANDOM assumes different values after a
reboot (same for perl's rand(100), which is likely more advanced and
less likely to suffer from that problem).
Jakob
listserv.traf...@sloop.net wrote:
I'm not aware, so if I'm wrong perhaps someone could correct me, but
I'd like a command to, in essence, do a comprehensive
--verify-all-files-in-the-archive. [I'm pretty sure such a thing
doesn't exist, at least I never saw it in the docs.]
This would apply
Jakob Unterwurzacher wrote:
steve.du...@pgcmls.info schrieb:
Dear all,
A friend recommended that I use rdiff-backup to maintain a back up of an
inconveniently large, reasonably slowly changing file repository.
I would like to keep the back up copy on a warm standby system, so that if the
Jakob Unterwurzacher wrote:
I guess you will have to use a wrapper script for your rsync job and
your rdiff-backup job that does the locking (and obeys the lock).
If you start both jobs at the same machine, it's easy:
Put this at the start of each script - it will then exit when another
Sorry I don't know of any at the moment. I use Devil-Linux
(http://www.devil-linux.org/), and have requested that rdiff-backup be
added.
Let me know whether you find an alternative. If no other USB-stick
distros support it then that alone is a good reason to add rdiff-backup
to Devil-Linux.
Hi Alex
There is a long thread about this issue at
http://www.howtoforge.com/forums/showthread.php?t=3618. But the problem
in the end seemed to be (in this case) that the user had generated the
authorized_keys file with nano and had not switched off hard wrapping,
so that when the file was
Hi Dominik
Although it is not an answer to your present predicament, I would say
that rdiff-backup is not advisable over an unstable connection. A better
strategy is to run rdiff-backup locally (preferably to a different
machine) and then use rsync to mirror the rdiff-backup repository to an
On 06/04/2010 17:03, Greg Freemyer wrote:
On Tue, Apr 6, 2010 at 11:27 AM, Randy Syringrsyr...@inteli-com.com wrote:
Josh Nisly wrote:
Two things:
1) The rdiff-backup project likely won't accept patches for features that
are platform specific. There are exceptions for OS-specific
On 22/06/2010 19:28, Darren Hart wrote:
On Tue, Jun 22, 2010 at 10:07 AM, Anthony Toolearto...@gmail.com wrote:
Hi Darren,
Are you aware that there is already a rdiff-backup FUSE plugin?
http://code.google.com/p/archfs/
I had no idea! This is excellent, I'll have a look and see
On 28/06/2010 14:22, Darren Hart wrote:
...What I'm looking to do is occasionally mount
the backup repository, browse for a single file, and restore it from
some time in the past, then unmount the repo.
I think my approach of building the directory listings from the
responses provided by the
It looks to me as if the problem maybe relates to the special characters
in the filenames '\xf3' and similar. And I see at the bottom mention of
a win_acl. My suggestions are:
- try using option --override-chars-to-quote - or
- try using option --no-acls - or
- try rdiff-backup version 1.2.8.
On 26/11/2010 11:14, Valerio Pachera wrote:
2010/11/25 Jacob Anawaltjlanaw...@gmail.com:
Look into the remote-schema option, search around for rdiff-backup and netcat,
and there are ssh cipher options.
I found an article
David:
Following your posting, I have tested the behaviour of our system
backing up read-only folders and files with rdiff-backup, and it works
correctly, even when the read-only files change. We are backing up from
Windows machines but to a Linux server (using TimeDicer as wrapper for
See Andrew Ferguson's response regarding this error message here:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/rdiff-backup-23/regression-fails-ioerror-not-a-gzipped-file-93222/
Andrew is the current maintainer of rdiff-backup so his word is law!
What version
On 07/12/2010 14:42, ~D wrote:
On 12/07/2010 03:26 PM, D. Kriesel wrote:
Do you prevent a shutdown or reboot when rdiff-backup is running? How?
Since rdiff-backup does not like backup interruptions (and therefore is not
usable on slow or unreliable connections) I rdiff to a local repository
On 07/12/10 18:54, ~D wrote:
On 12/07/2010 05:09 PM, Dominic Raferd wrote:
On 07/12/2010 14:42, ~D wrote:
On 12/07/2010 03:26 PM, D. Kriesel wrote:
Do you prevent a shutdown or reboot when rdiff-backup is running?
How?
Since rdiff-backup does not like backup interruptions (and
therefore
On 07/12/2010 22:40, ~D wrote:
On 12/07/2010 09:33 PM, Dominic Raferd wrote:
On 07/12/10 18:54, ~D wrote:
On 12/07/2010 05:09 PM, Dominic Raferd wrote:
On 07/12/2010 14:42, ~D wrote:
On 12/07/2010 03:26 PM, D. Kriesel wrote:
Do you prevent a shutdown or reboot when rdiff-backup is running
yes you could write a bash script and put it as a job in your crontab
to run every 15 minutes, say...
My mirror backup server (not my primary) is updated from my primary by
a script which uses rdiff. The script runs on the primary and starts
by waking up the mirror server (over the internet),
Can anyone explain the relationship between /usr/lib/librsync.so,
and
/usr/local/lib/python2.6/dist-packages/rdiff_backup/_librsync.so?
They are not the same:
/usr/lib/librsync.so is symlinked to
/usr/lib/librsync.so.1.0.2 which is 46612 bytes, and I
On 21/12/2010 22:56, Greg Freemyer wrote:
All,
I've got a directory that seems to be missing some files.
I don't recall their names or exactly when they existed.
rdiff-backup -l --list-increment-sizespath-to-backup-dir
shows me that I have about 10 instances of that directory backup up.
Is
On 03/01/2011 20:27, Eric Wheeler wrote:
On Sun, Jan 02, 2011 at 08:11:00PM -0800, Eric Wheeler wrote:
Feedback and comments are appreciated!
Original Message-
From: Matthew Miller
How will this interact with existing backups?
rdiff-backup re-writes changed destination files, so if a
AFAIK Andrew's last posting on this newsgroup was March 2009, and his
last entry in CVS was January 2010, which is indeed the last entry by
anyone. Josh (who also created the excellent rdiffWeb GUI front-end) was
last seen here April 2010. You could try requesting to become a project
member
On 08/01/11 10:31, D. Kriesel wrote:
Hi Dominic,
this is certainly a cool idea, only I have no Python developer experience und
therefore you for sure don't want me as a project member :-). Currently, I just
try to help out people on the mailinglist from my experience as a computer
scientist
Thanks David, that is helpful.
It would be good if there was a way of removing a subset of data from
the entire repository. So let's say I put a 500GB folder in /home by
accident and it has gone into the repository and is bloating it. I can
exclude it from my future rdiff-backup runs but the
On 12/01/11 00:55, Thomas Evangelidis wrote:
I have an external hard drive where I would like to save my Windows
files and also create incremental backups for Linux. The problem is
that incremental backups cannot be created in the default HPFS/NTFS
file system of the hard drive. Is it
I think for exclude-globbing-filelist you don't need that dash prefix.
Here is an extract from mine, which works under Windows:
ignorecase:**/printhood/**
ignorecase:**settings/temp**
ignorecase:**NTUser.dat**
ignorecase:**Deleted Items.dbx**
ignorecase:**Old.dbx**
ignorecase:**/Kiesoft/**
This must be almost a record snail-wise for a newsgroup correspondence
(my original posting June 2009, Janne's reply Feb 2010, this reply Jan
2011), but by way of a very belated thank you to Janne for his
suggestion, and using his technique, I attach a bash script which
automates the process
That seems extraordinarily slow for rdiff-backup to backup a text file
to a local disk, even a file that is 3.9GB. Was the file changing
(additional log entries, maybe?) while rdiff-backup was trying to back
it up?
Dominic
On 01/02/2011 06:33, Patrick Nagel wrote:
-BEGIN PGP SIGNED
Yes, backing up from LVM snapshots is the best way (or, for Windows, use
VSS), but at least you found a workaround...
Dominic
http://www.timedicer.co.uk
On 01/02/2011 09:42, Patrick Nagel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dominic,
On 2011-02-01 17:14, Dominic Raferd
I'm afraid that the short answer is: no
In most situations there should be no need to remove an intermediate
backup because there would be little space saving. However in some
situations it would be very helpful - say if you backed up the wrong
stuff into an existing repository on one
excellent! I look forward to trying it...
Dominic
On 08/02/2011 11:22, Filip Gruszczyński wrote:
I'd like to announce first stable release of rdiff-backup-fs
filesystem (formerly known as archfs). rdiff-backup-fs is a filesystem
that provides easy access and browsing of rdiff-backup archives.
My reading is that using --force on a restore will overwrite existing
files with the same name - so you may lose previous data at the restore
destination. In general if you are restoring a directory (or a complete
repository) it is logical to use a clean destination, in which case it
shouldn't
On 09/02/2011 14:48, Robert Nichols wrote:
On 02/09/2011 07:32 AM, Dominic Raferd wrote:
My reading is that using --force on a restore will overwrite existing
files with the same name - so you may lose previous data at the restore
destination. In general if you are restoring a directory
I used rdiff.exe briefly before moving to rdiff-backup. Certainly
rdiff-backup does your 2-4 'under the hood' and fast. It is highly
optimised both for speed of transfer and for storage space - but does
require a reliable connection between source and destination. It does
not do your 1, you
Marc:
I can't help with the python. But first step, unless the most recent
backup is critical to you, is to try regressing the repository to get it
back to a clean state, with the --check-destination-dir switch. If this
refuses to regress, claiming that there is no corruption, I have a bash
On 21/02/11 00:22, Robert Nichols wrote:
On 02/20/2011 02:51 PM, Marc Haber wrote:
On Sun, Feb 20, 2011 at 06:11:19PM +, Dominic Raferd wrote:
Secondly, rdiff-backup --verify switch gives only a partial
verification
of the repository. Daniel Miller wrote a patch, available for
rdiff
On 20/02/2011 20:51, Marc Haber wrote:
On Sun, Feb 20, 2011 at 06:11:19PM +, Dominic Raferd wrote:
first step, unless the most recent
backup is critical to you, is to try regressing the repository to get it
back to a clean state, with the --check-destination-dir switch
Fatal Error
On 24/03/2011 00:07, Patrick Nagel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 2011-03-24 06:29, Scott Jilek wrote:
Is there any way to force Rdiff to use a hash compare for difference
triggering? I looked over the manual, and nothing seems to be what I'm
looking for.
I've
On 24/03/2011 17:31, Scott Jilek wrote:
Unfortunately, I can't just touch the file because it's in use and
locked by the truecrypt process.
Are you sure? I tried this and it worked for me with a truecrypt file in
use.
Is there any plan to add the rsync -c option to rdiff-backup to force
The problem appears to be with some non-ASCII characters. What
filesystems are you backing up to/from? Try with the switches
--null-separator and/or --override-chars-to-quote, or if you are already
using them, try without!
Dominic
http://www.timedicer.co.uk
On 03/04/2011 16:28, Benjamin
I can run rdiff-backup 1.2.8 fine on Windows 7 64-bit.
Edited from http://www.nongnu.org/rdiff-backup/:
On Windows, rdiff-backup requires the Visual C++ 2008 redistributable.
Download DLL package
http://download.savannah.gnu.org/releases/rdiff-backup/Microsoft.VC90.zip and
copy the four
Bruno:
Do you need to use NTFS for the external drive? I suggest you try again
using a Linux format such as ext3 and see if you have more success. My
impression is that a high proportion of problems with rdiff-backup
relate to backups to NTFS volumes (backup *from* NTFS generally works fine).
Alex, I believe Daniel Miller is working on a new project inspired by
rdiff-backup, I think he will post here when it is ready for others to
try. I don't think its archives will be compatible with rdiff-backup.
For most of us rdiff-backups works and works very well indeed. Users
like myself
Andreas:
I have never used the --include-globbing-filelist, only the
--exclude-globbing-filelist, but here are some suggestions:
Try: run the command with sudo [for cron: put in /etc/crontab]
Or: add '- /home/username/.gvfs' at the *top* of your filelist (if you
haven't already tried it
There is a fuse-fs for browsing rdiff-backup repositories [1].
Passing options to fuse is going to be enabled in the next release. With
allow_user set I should be able to mount my config backup as root, but
browse it as a user.
There's also a nice way to automatically exclude filesystems that
On 04/07/2011 14:48, Maarten Bezemer wrote:
...My money would be on the network stability.
Maybe rdiff-backup could somehow be made more robust, but I doubt the
current design can be patched to support reconnection attempts when
disconnected unexpectedly...
I agree. IMO rdiff-backup should
On 08/07/2011 13:30, abschiedsstein wrote:
Hi,
I used rdiff-backup for a while and everything was fine. Backups were fast and
restoring was no problem.
Then, after an interrupted backup, the data was broken. Neither restoring nor
fixing with --check-destination-dir was possible.
I guess there
On 18/08/11 22:47, Grant wrote:
And, looking at the whole subject from a different angle: pushing also has
the large drawback that in case your laptop is stolen/lost/whatever, and you
use an ssh key for rdiff-backup to connect to your backup server, you risk
not only losing your 'real'
On 28/10/2011 11:03, john wrote:
Hi
The same problem as described here strucked me, too: When regressing a backup, rdiff-backup starts instantly consuming memory at quite a high rate, until it reaches 3GB. Then it dies with a memory allocation error, because it is running on
I think (but haven't tried) you could alter the rdiff-backup option text
like this (this is under Ubuntu 10.04, the location might differ with
another OS):
sed -i 's/remove-older-than/remove-older-thax/g'
/usr/share/pyshared/rdiff_backup/*.py
So unless an infiltrator knew the new command
On 14/11/2011 14:21, Filip Gruszczyński wrote:
Do you have any plans to release an update to rdiff-backup-fs 1.0.0?
Yes. I have a lot on my head recently (changed job and country too),
but I have some changes in SCM waiting to be deployed. I will try to
get to that and release a new version
On 15/11/2011 00:23, Alex Schuster wrote:
I need to restore an old VMware image, but I am getting LOTS of these
errors:
Error reading /backup/weird/home/wonko/os/vmware/xp/winXPPro-0.log,
substituting empty file.
Warning: Hash da39a3ee5e6b4b0d3255bfef95601890afd80709 of winXPPro-0.log
doesn't
Schuster wrote:
Maarten Bezemer writes:
On Tue, 15 Nov 2011, Dominic Raferd wrote:
On 15/11/2011 00:23, Alex Schuster wrote:
Warning: Hash da39a3ee5e6b4b0d3255bfef95601890afd80709 of winXPPro-0.log
doesn't match recorded hash db9943d0284382131b553cef380aae99871b0f2e!
Any idea what has happened
On 08/12/2011 05:12, Chris wrote:
I'm doing some testing to learn how to utilise rdiff-backup. I'm hoping
some one can help answer a few questions.
I have created two directories. One is a directory called root where I
have created two files. I back those files up to a directory called
backup.
On 13/12/2011 14:31, Jean Pierre Dentone wrote:
Hi
I'm trying to get a backup of a 3TB partition and it failed with this error
Exception '[Errno 31] Too many links:
'/rdiff/newarsvrfs01/htdocs/chase.archinetonline.com/chasedata/project_89381''
raised of class 'exceptions.OSError':
This has
Jochen:
what if you change /etc/backup.list by removing the final slash from
/backup/dev/ i.e. /backup/dev
I think that with your backup list it tries to backup /backup/dev
(though not its contents) and maybe this causes the failure?
Dominic
-
, Dominic Raferd said:
Jochen:
what if you change /etc/backup.list by removing the
final slash from /backup/dev/ i.e. /backup/dev
I think that with your backup list it tries to
backup /backup/dev (though not its contents
On 10/03/12 08:00, Nicolas Jungers wrote:
On 2012-03-10 04:07, Willem Buitendyk wrote:
I'm a little perplexed. My scenario is that I have data loggers in
the field, each with a 3g usb modem on board. I want to have the
data loggers rdiff back to my server on amazon ec2 - or to push the
If you want to carry on running native rdiff-backup.exe directly, I
suggest you remove backslashes and just use a single forward slash as
the directory separator in your specifications (including in your
exclude-list file).
It is possible that you will hit further problems because you are
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
What exactly needs to be deleted (i.e. the rdiff metadata)? What happens
to the data history (held in the rdiff-backup directory), is it still
all recoverable after you have followed this procedure?
Dominic
On 20/05/2012 12:34, D. Kriesel wrote:
PS.: You might have to --force the backup, not
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
@David: if you try obnam please let us know how you get on with it.
I guess one could store rdiff-backup repositories on a deduplication
file system such as lessfs or zfs and get the de-duplication
benefits. And using the --no-compression switch might or might not
Thanks for your posting Kshitij, you give us yet another backup program
to consider - back-in-time.
If it ain't broke, don't fix it:
If your backup routine works for you, why change to rdiff-backup?
Back-in-time (according to the website) is a GUI and under the hood it
uses rsync, diff, cp
I recommend rdiffweb to restore single files from an rdiff-backup
repository.
On 22/08/12 22:54, wardrop wrote:
Any other means for that'll work on Windows. I have a combination of Windows,
OS X and a Busybox QNAP NAS that all need rdiff and possible restore
functionality; it's mainly the
Leland, have you tried doing the backup from your Windows machine to a
Linux host and then restoring from there?
Or, if that is not possible, using the linux version of rdiff-backup on
your Windows machine through cygwin?
Dominic
*TimeDicer - Windows Backup and File Recovery from Whenever
ried quite a few combinations of things but figured my
initial post would be long enough without going through them all. Also,
I figured the case I outlined was the simplest one (i.e. least number of
variables to worry about). But since you ask ...
On Sat, 2012-09-08 at 09:26 +0100, Dominic Ra
-19 at 17:53 +0100, Dominic Raferd wrote:
Sorry Leland, I have always explicitly excluded acls from my Windows
backups.
Hmmm, well there's something I haven't tried. However, as I understand
it (which may well be wrong of course) the rdiff-backup options about
ACLs (e.g. --no-acls) all apply
Hi Gary
From what I can tell this doesn't seem to be a problem with
rdiff-backup but some sort of issue with ssh? Anyway...
ssh-copy-id -i /home/clientrdiff/.ssh/id_rsa.pub
serverrd...@server.server.com mailto:serverrd...@server.server.com
as both root and clientrdiff returns
ssh: connect
**
On Fri, Nov 2, 2012 at 3:30 AM, Dominic
Raferd domi...@timedicer.co.uk
wrote:
Here is a
further-improved version of my script, and hopefully it can
now use yum to install any missing
Here is my 2 cents:
Long file names are not a problem for rdiff-backup
'Foreign' characters should not be a problem provided they are
properly supported on your Windows command line. If you can view
the file name correctly from the command line then it
450, in __call__
return apply(self.connection.reval, (self.name,) + args)
File
"/usr/lib64/python2.4/site-packages/rdiff_backup/connection.py",
line 370, in reval
if isinstance(result, Exception): raise result
OSError: [Errno 13] Permission denied:
'
On 06/11/2012 14:53, Slavko Kocjancic wrote:
On 11/06/2012 12:28 PM, Dominic
Raferd wrote:
I would not use rdiff-backup to backup Windows c:, I
regard rdiff-backup (for Windows) as a 'data
On 07/11/2012 14:43, Slavko Kocjancic wrote:
I tryed just one directory with few dirs under and afret few backups got
same problem.
cd c:/_Skeni
f:/_rdiff/rdiff-backup -v6 c:/_Skeni f:/_Skeni_Rdiff/
snip...snip
Regular copying ('SP1950', 'SP1950_5PRA_revizija_01',
Hi Luc
Why not just use this command:
rdiff-backup /cygdrive/t/data luc@jana::/smb/backup/armand
If this doesn't work, maybe there is a problem running rdiff-backup
to a samba-mounted volume on the rdiff-backup server? Try backing up
to e.g.
Hello Jason and welcome to rdiff-backup!
On 06/02/2013 20:07, Jason Sauders
wrote:
Hello! I'm a new user to rdiff-backup and have been
experimenting with it for the better part of two days now. It was
recommended to me by another user who wondered why
:
http://stackoverflow.com/questions/5828037/cygwin-sets-file-permission-to-000
I've written up the full details here if you are interested:
http://dadhacker.blogspot.co.uk/2013/03/getting-rdiff-backup-to-work-with.html
Thanks for the help!
Dave.
On 21 March 2013 17:18, Dominic Raferd domi
Ned, I think it would be great it you wanted to be maintainer, if you
have the time to do it. Andrew went off to pastures new a while ago and
isn't seen around here now, so the project has been unmaintained for a
while. I might be able to get you an email address for him though.
Failing that I
Harvey
wrote:
From: Dominic Raferd [mailto:domi...@timedicer.co.uk]
I might
be able to get you an email address for him though. Failing that I guess
you
could create a fork.
Thanks, I was able to reach Ben Escoto, who gave me
Hello Ans,
I have been using rdiff-backup for about 4 1/2 years and have found it
very stable and reliable. I created and maintain a Windows wrapper for
rdiff-backup called TimeDicer http://www.timedicer.co.uk/index and of
course use it (and therefore rdiff-backup) every day.
There are two
Kevin:
Just to rule something out, try running it via a script, this way
you can get rid of the sudo on the command line. I have known cases
where sudo (under Ubuntu) causes strange behaviour with wildcards,
not involving rdiff-backup but it is worth checking.
I'm sorry Kevin I don't take OS X (or any Apple sauce) so I'm out of
suggestions...
Dominic
On 17/05/2013 20:09, KP wrote:
Dominic,
I added--exclude-regexp '[{}]+' after checking Spotlight to
see if any vital files would be
Paul
Why not backup all the rdiff-backup data too? I use my TimeDicer
package to do same as you and then I use timedicer-mirror
(http://www.timedicer.co.uk/programs/help/timedicer-mirror.sh.php)
to backup the fileserver (Primary TimeDicer Server) to offsite
Bonjour Ibrahim
rdiff-backup does not have any built-in encryption. Also based on my
experience rdiff-backup should not be run directly over the internet, it
should be run on a lan (or of course a single machine) and then the
rdiff-backup repository (archive) mirrored over the internet using
Are you running this over the internet? I wouldn't advise this
precisely because of these sorts of problems. rdiff-backup really
needs a reliable connection, rsync is better for backup over the
internet. If you need the extra functionality of rdiff-backup, either
run rdiff-backup
The best source for info about rdiff-backup is presently this
mailing list! The online documentation is quite old, although we now
have a new maintainer in Ned so things are looking up.
Yes, you should be able to run rdiff-backup locally on the server
with --check-destination-dir to
1 - 100 of 218 matches
Mail list logo
