For Debian/Ubuntu you can use Patrik's repo. Follow instructions at
https://nexus.ikus-soft.com/repository/archive/rdiffweb/2.8.9/doc/installation.html#option-1-debian-ubuntu-repository
to add the Debian/Ubuntu repository.
You can then add Rdiffweb as suggested but you can also add
h 00, Dominic Raferd
a écrit :
Hi Patrik
can you add my email address to your Rdiffweb google group? For
technical reasons I can't subscribe myself.
Regards
Dominic
On 26/02/2024 00:07, Jonathan Hutchins wrote:
Is encryption an option for rdiff-backup?
Not in itself, but you can run rdiff-backup on a system with block
device encryption such as LUKS + dm-crypt, and at the time of writing
this is offered as an option ('encrypt with LUKS') when installing
On 17/02/2024 03:14, Robert Nichols wrote:
On 2/16/24 08:44, Dominic Raferd wrote:
Until then, I am interested in your parallel processing approach.
Presumably you start 8 parallel rdiff-backup verify sessions for
datetime points -1 to -8 (and then, when they are all complete, -9 to
-16, -17
On 15/02/2024 20:05, Robert Nichols wrote:
On 2/15/24 09:47, Dominic Raferd wrote:
...snip...
So the only way to be confident about *all* the data in a repository
is to use 'rdiff-backup verify' to verify each and every backup
session in each repository; and this includes verifying the current
I wondered if those who know the rdiff-backup code from the inside can
confirm or correct my understanding about verification of rdiff-backup
repositories, which is as follows:
'rdiff-backup verify' verifies the integrity of all files/directories
(etc) in a single backup session at the
-> /opt/rdiff-backup-2.2/rdiff-backup
Le jeu. 15 févr. 2024, à 07 h 32, Dominic Raferd
a écrit :
Thanks Eric and Patrik.
Patrik, on a client (running Ubuntu 22.04) I added your repo (for
rdiffweb) per the instructions at your website (option 1), but
running
apt upgrad
.
Hope this helps, Eric
On February 14, 2024 3:32:38 PM UTC, Dominic Raferd <
domi...@timedicer.co.uk> wrote:
First, continued thanks for Eric and the team for their great work on
updating rdiff-backup - really amazing stuff.
Following a system upgrade of my backup server to Ubuntu 23
First, continued thanks for Eric and the team for their great work on
updating rdiff-backup - really amazing stuff.
Following a system upgrade of my backup server to Ubuntu 23.10, I have
version mismatches: clients have (Windows and) Ubuntu 22.04
(rdiff-backup 2.0.5) whereas the server has
On 15/02/2022 02:24, Mr. Clif wrote:
Hi Folks,
In case it's helpful, here's a shell function I came up with to backup
snapshots of VMs in a way that preserves the usual UIDs and GIDs: ...
This is clever but I was puzzled why you experience this UID/GID shift
problem in the first place - I
On 10/02/2022 07:19, Mr. Clif wrote:
...Right now my backups for this vm have been corrupted by the shifted
UID/GIDs I can no longer use that archive to restore to the running vm...
If you want to regress your archive back to a 'clean' state you can try
my rdiff-backup-regress script
On 08/02/2022 06:59, ewl+rdiffbac...@lavar.de wrote:
Hi,
just because I became curious, the numbers are probably not to be
compared:
- iperf3 tells me ~170Mbit/s
- I transferred initially my Downloads repository from laptop to
server (which has roughly as much disk as you have RAM :-P),
On 06/11/2021 18:45, Bill Harris wrote:
I've been using rdiff-backup for 10+ years...
What is the problem?
On 01/11/2021 15:21, Michael Crider - HOEC wrote:
We have used rdiff-backup for well over 10 years for our Linux servers
and workstations, and until recently to back up Windows servers and
workstations we mounted their drives locally on the backup server and
ran rdiff-backup against the mount.
You could try using rdiff-backup --no-compression (or
--no-compression-regexp). This will make backups bigger but should speed
up backups and restores.
The only built-in compression offered by rdiff-backup is gzip, but if
you run rdiff-backup --no-compression to a file system using
On 22/04/2021 08:31, griffin tucker wrote:
On Thu, 22 Apr 2021 at 17:17, Dominic Raferd wrote:
On 22/04/2021 08:07, Dominic Raferd wrote:
On 22/04/2021 08:01, griffin tucker wrote:
I've tried using deduplication, but only get about 6gb savings per 30gb.
I intend on using squashfs on top
On 22/04/2021 08:07, Dominic Raferd wrote:
On 22/04/2021 08:01, griffin tucker wrote:
I've tried using deduplication, but only get about 6gb savings per 30gb.
I intend on using squashfs on top of rdiff-backup, btrfs is just being
used temporarily.
On Thu, 22 Apr 2021 at 16:41, Dominic
On 22/04/2021 08:01, griffin tucker wrote:
I've tried using deduplication, but only get about 6gb savings per 30gb.
I intend on using squashfs on top of rdiff-backup, btrfs is just being
used temporarily.
On Thu, 22 Apr 2021 at 16:41, Dominic Raferd wrote:
On 22/04/2021 07:03, griffin tucker
On 22/04/2021 07:03, griffin tucker wrote:
i have a collection of the last 5 monthly dumps of various wikis from
dumps.wikimedia.org
each dump has numbered directories in the format 20210501, 20210401,
20210301, etc.
all the filenames in these directories remain the same with each
wiki's dump,
On 26/03/2021 12:44, Reio Remma wrote:
On 26.03.2021 14:41, Arrigo Marchiori wrote:
I would like to add:
* Multi-platform (I have used it on Windows, Linux, FreeBSD)
* Easy to deploy and schedule, because all parameters are given on
the command line
* Command-line interfaces allows
On 27/03/2021 07:29, reg.rdiff_bac...@excel4x.com wrote:
On 25.03.2021 09:29, reg.rdiff_bac...@excel4x.com wrote:
I just heard about rdiff-backup and I'm planning how to
configure it.
The documentation says:
"Earlier states of your files are saved just by 1) keeping
a copy of
them,
2) in
On 25/03/2021 07:29, reg.rdiff_bac...@excel4x.com wrote:
I plan to use rdiff-backup on Windows using Windows networking - e.g. drive
letter for remote file access. I have a mirrored copy of files already on
the backup system.
1) Can I run rdiff-backup for the first time with a pre-populated
On 02/01/2021 20:38, Eric L. Zolf wrote:
Hello everybody,
first, let me wish you a happy new year, health and good luck.
I'm currently working on using argparse to improve the way command line
arguments are parsed, in a way compatible with the old handling while
developing a new, hopefully
Can someone help with getting the latest stable release of
rdiff-backup i.e. 2.0.5 into the official repositories of
Debian/Ubuntu (instead of 2.0.0)? (Otto has Ubuntu launchpad repos
which allow 2.0.5 to be installed on old systems, and allow the latest
development version to be installed on
On Sun, 28 Jun 2020 at 17:20, Otto Kekäläinen wrote:
>
> Hello!
>
> ke 24. kesäk. 2020 klo 16.14 Dominic Raferd (domi...@timedicer.co.uk)
> kirjoitti:
> >
> > Hi Otto,
> >
> > Thanks for your great work on rdiff-backup and for your PPAs!
> >
> &g
On Tue, 9 Jun 2020 at 15:28, Derek Atkins wrote:
>
> EricZolf writes:
>
> > 3. to answer Derek's e-mail as well: would it have an impact on speed?
> > To be honest, no clue, we would need to analyze this.
>
> Just as another data point, apparently a year ago my backup server
> wasn't backing
On Thu, 4 Jun 2020 at 11:46, EricZolf wrote:
>
> rdiff-backup has currently its own file formats, which are far from
> being standard, meaning a lot of custom code to handle these formats,
> respectively a lot of different files...
+1 for YAML, but please retain compatibility (at least for
On Tue, 21 Apr 2020 at 07:17, Eric Lavarde wrote:
>
>
> On 20/04/2020 22:54, Gregor Zattler wrote:
> > Hi Eric,
> > * "Eric L. Zolf" [2020-04-20; 07:43]:
> >> How to detect (under Linux): run `cd MY_BACKUP_REPO; ls -1
> >> rdiff-backup-data/mirror_metadata.* | sed -e 's/^.*mirror_metadata\.//'
On Mon, 20 Apr 2020 at 19:10, Eric L. Zolf wrote:
> Hi Dominic,
>
> On 20/04/2020 08:40, Dominic Raferd wrote:
> > I have checked our 108 repositories which go back a long way (I am still
> > using v1.2.8). I find this issue in one repository for some 27 dates
> > (mos
On Mon, 20 Apr 2020 at 06:46, Eric L. Zolf wrote:
> we've got a report for an issue [322] where we're not sure how it
> happened and if it happens often. As I know that some of you have many
> and long standing repos, you might want to have a look before you
> upgrade to 2.0.0. Also I'd like to
On Thu, 14 Nov 2019 at 19:12, wrote:
> Hi,
>
> On 14/11/2019 01:47, Yves Bellefeuille wrote:
> >> 3. which file system type you are using to backup?
> > Backing-up from NTFS (Windows 7) to ext4.
>
> Cross-filesystem-types backup is always a bit tricky. This said if you
> have the occasion, it
Is it possible you are running out of temporary file space? You can specify
a different tmp location with switch --tempdir (or, if running to remote
server, --remote-tempdir). When checking an archive rdiff-backup may need a
lot of temporary space for all that unpacking. By the way, it may not be
On Fri, 26 Jul 2019, 17:37 Otto Kekäläinen, wrote:
> Hello!
>
> There has not been any new releases of rdiff-backup since 2009. If the
> original maintainer does not intend to work on this project, could I
> please be allowed to take over?
>
> I am a Debian Developer and active in multiple open
On Fri, 19 Jul 2019 at 20:43, Jelle de Jong
wrote:
> On 7/18/19 4:45 PM, Lew Wolfgang wrote:
> > On 07/17/2019 04:48 AM, Jelle de Jong wrote:
> >> Hello everybody,
> >>
> >> I am trying to run an rdiff-backup and it keeps missing some documents
> >> compared with the source, we are using a
e to create a new backup set, so I won't know if this
> workaround helps immediately.
>
> Would anyone be able to shed light on this issue? Is there a way to make a
> failure to copy (this kind of) ACE non-fatal?
>
I advise running rdiff-backup from Windows with --no-acls, and following
any restore consider using icacls to fix permissions back to the standard
inherited ones e.g.
icacls %APPDATA%\Thunderbird /reset /t /c /q
Dominic Raferd
https://www.timedicer.co.uk
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
On Sat, 27 Apr 2019 at 10:28, David Croll wrote:
>
> Dear rdiff-backup people,
>
>
> Yesterday, a backup failed repeatedly. Error Number 28 - No space left
> on device. The backup stopped with a specific file, a Firefox cache file
> with a size of 0 bytes.
>
> But neither on the source nor on
On Fri, 29 Mar 2019 at 11:57, Harald Hannelius
wrote:
>
> On Fri, 29 Mar 2019, Dominic Raferd wrote:
> > On Fri, 29 Mar 2019 at 11:47, Harald Hannelius <
> harald.hannel...@arcada.fi>
> > wrote:
> >> On Fri, 29 Mar 2019, Dominic Raferd wrote:
> >>>
On Fri, 29 Mar 2019 at 11:47, Harald Hannelius
wrote:
>
> On Fri, 29 Mar 2019, Dominic Raferd wrote:
> > On Fri, 29 Mar 2019 at 11:01, Harald Hannelius <
> harald.hannel...@arcada.fi>
> > wrote:
> >
> >> If I run the command "ssh -C root@backupser
On Fri, 29 Mar 2019 at 11:01, Harald Hannelius
wrote:
>
> Hi all,
>
> I have a win 2019 server that I'd like to take backups from. I'm using the
> OpenSSH version included in MS RSAT and I have succesfully created
> SSH-keys
> and I can verify that running the ssh-command indeed starts a
On Mon, 24 Dec 2018 at 11:20, dsep...@t-online.de
wrote:
> Today morning i started a backup. This backup gots interrupted by the feet
> of our cat :)
>
> So i thought, that i simply empty the target directory and start over from
> scratch. But no luck. Everything i try gets answered from
On Wed, 1 Aug 2018 at 17:31, Bill Harris
wrote:
> On Tue, Jul 31, 2018 at 10:30 AM Dominic Raferd
> wrote:
>
>> On Tue, 31 Jul 2018 at 16:53, Bill Harris wrote:
>>
>> > I've used rdiff-backup for years, and I'm mostly very happy with it.
>> There
>> &
On Tue, 31 Jul 2018 at 16:53, Bill Harris wrote:
> I've used rdiff-backup for years, and I'm mostly very happy with it. There
> is one problem that crops up occasionally; and I haven't found a way around
> it yet.
>
> AFAICT, rdiff-backup likes running as root. On rare occasion, I forget and
>
On 5 February 2018 at 10:59, Richard Hector wrote:
> Hi all,
>
> I have a problem with an (inherited) rdiff-backup setup - actually used
> from backupninja.
>
> When I try to run a backup, I get:
>
> OSError: [Errno 2] No such file or directory:
>
I am still reading the list and actively using rdiff-backup, which
works well. However it seems to be effectively unmaintained and has
been for some time. I don't do python sadly. It would be great if
someone such as Patrik could take it on (as he has done so well for
rdiffweb, which provides a
On 23 June 2017 at 12:53, Ron Leach wrote:
> List, good morning,
>
> Having messed up the latest backup increment of our quite-large filesystem
> and, having long been a very happy user of Dominic's rdiff-backup-regress
> script, I thought I'd better regress the messed-up
On 11 June 2017 at 11:13, Marcin Zajączkowski wrote:
> Hi,
>
> I have a long established backup with some large files which I would
> like to move to another directory withing the same backup (or just
> remove entirely from the backup) as a clean up of the original disk
>
On 4 May 2017 at 09:44, Ron Leach wrote:
>
>
> Thanks, I've done that and I think there must be, after all that, a
> somewhat more-serious problem. The regress started then aborted saying
>
> Error 1 occurred when attempting to regress archive...
> ls: cannot access
On 3 May 2017 at 22:28, Ron Leach <ronle...@tesco.net> wrote:
> On 02/05/2017 23:42, Dominic Raferd wrote:
>
>
>> I suggest you take a backup of the existing broken repository and then try
>> on it the latest version of my script which can be obtained from
>> ht
On 3 May 2017 at 08:37, Ron Leach <ronle...@tesco.net> wrote:
> On 02/05/2017 23:42, Dominic Raferd wrote:
>
>>
>>
>> I suggest you take a backup of the existing broken repository and then try
>> on it the latest version of my script
>>
>
> Domini
>
> ...
>
> I searched for this new error and, in this archive,
>
> http://www.backupcentral.com/forum/17/213517
>
> Dominic announces what I imagine is an early version of his regress script
> which overcomes this second error.
>
> But I am unsure whether to run it here because - really - I
On 23 March 2017 at 07:55, Henti Smith wrote:
> Good day all.
>
> I'm having a tough problem with backing up a server. We've been running
> successful backups on the server, but due to storage constraints we dropped
> the retention to just one day. We're using backupninja
On 13 January 2017 at 18:36, Patrik Dufresne wrote:
> Hello,
>
> If I need to backup multiple disks (C: & D:) on a Windows server, do I need
> to run rdiff-backup twice. Once for each disk ? Or there is a way to backup
> both of them in a single pass ?
>
Hi Patrik, if you are
On 4 January 2017 at 22:40, Ilario wrote:
> 2017-01-04 20:11 GMT+01:00 Adrian Klaver :
>> On 01/04/2017 11:00 AM, Ilario wrote:
>>> Excluding a hidden file without full path doesn't rise an error (as
>>> happens with non hidden files) and copies
On 4 January 2017 at 16:08, Ilario wrote:
> 2017-01-04 15:53 GMT+01:00 Ilario :
>> 2017-01-04 15:17 GMT+01:00 Ilario :
>>> AssertionError: Bad index order: ('long_filename_data', '820') >=
>>> ('backup-20140716', 'progetti',
If this doesn't work, try with --remote-tempdir [path] instead of/as well
as --tempdir [path], as you seem to be restoring from a remote machine and
in this case I think the remote machine probably does the heavy lifting.
On 12 July 2016 at 07:29, Dominic Raferd <domi...@timedicer.co.uk>
Put the --tempdir (path) before the main parameters.
On 12 Jul 2016 07:24, "Stephen Butler" wrote:
> Hi all,
>
>
> I'm experimenting with restoring older version of a large outlook file
> (9gb)
>
>
> My command and the error output.
>
> sudo rdiff-backup
gt; Thank you for taking the time to look at this..
> >
> > On Mon, March 28, 2016 10:41 am, Dominic Raferd wrote:
> >> Is this really your first rdiff-backup to this location? If you have any
> >> previous rdiff-backup runs to this repository then the situation
Is this really your first rdiff-backup to this location? If you have any
previous rdiff-backup runs to this repository then the situation is
complicated by rdiff-backup's need to create a new set of reverse diff
files to be able to regress to previous file contents.
What is your /tmp location?
Hello rdiez,
I have done a simple test of this scenario but when I run rdiff-backup
--verify I don't see any warning messages. (I believe the SHA1 digests are
held in the rdiff-backup-data/mirror_metadata.* files.)
See some postings here
Great news, thank you for taking on this responsibility.
Dominic
On 13 February 2016 at 05:28, Dave Kempe wrote:
> Gday,
> as of today, Sol1 has taken over official maintainership of rdiff-backup.
> We have done so with the blessing of the original author, Ben Escoto, and
>
The message I see in the same situation is:
Fatal Error: Destination directory
[dir]
exists, but does not look like a rdiff-backup directory. Running
rdiff-backup like this could mess up what is currently in it.
*If youwant to update or overwrite it, run rdiff-backup with the
--forceoption*.
Hello Patrik
I believe the current maintainer is Ned Harvey who took over in May 2013,
but I think his actions were confined to some fixes to the website rather
than any work on the program code, and he hasn't been visible here
recently. Before him the maintainer was Andrew Ferguson and before
I am not a python coder sadly, but the fault appears to be generated by
this line in fs_abilities.py:
assert letter_rp.lstat(), letter_rp
I would suggest commenting out this line, as it is just an error test, and
in this case it may be a 'false positive', but of course this is not so
easy for
to restore 2015-08-21T01:12:31-04:00, we need to delete every newer
file from increments directory. Then --check-destination-dir is working.
--
Patrik Dufresne
On Wed, Sep 23, 2015 at 1:44 AM, Dominic Raferd
<domi...@timedicer.co.uk <mailto:domi...@timedicer.co.uk>> wrote:
H
Hi Patrik
On 22/09/2015 22:00, Patrik Dufresne wrote:
I've tried the script. I had issues with it.
It searchs 'current_mirror' file recursively. For some reash, the
backup contains files named 'current_mirror'. I add `-maxdepth 1` to
fix this.
Good point, I have updated the script with
After deleting the current_mirror file did you then run rdiff-backup with
--check-destination-dir? This performs the actual regression to the
previous, hopefully consistent, backup.
On 15 September 2015 at 00:46, Patrik Dufresne wrote:
> Hello,
>
> One of my backup repository
;2015-09-14T19:00:02-04:00". Should I delete all of
> them ? I know the last successfule backup is "2015-08-24".
>
> --
> Patrik Dufresne
>
>
> On Tue, Sep 15, 2015 at 3:05 AM, Dominic Raferd <domi...@timedicer.co.uk>
> wrote:
>
>> After de
Hi Heri
On 05/09/2015 15:52, heri wrote:
Hi
The following error concerns a file in a folder which is maintained by
rdiff-backup itself. I never changed something therein. rdiff-backup
cannot recover itself. Each run of
rdiff-backup" --include-globbing-filelist rdiff_include_f_to_r.txt
Hello Patrik
I think the simple solution is to backup to a directory to which only
one linux user has access. For our windows backups each Windows client
machine has a separate linux user account on the server and backs up to
its home directory. All users' home directories have 0700
My 2p...
Rdiff-backup has limitations and it would be *really* good if someone
who understood python could step up and maintain the code, but I don't
see the problem with regressions. Yes they are slow but they should be
emergency operations reserved for rare circumstances. If you are
I get:
Inode count: 29360128
Inodes per group: 8192
Inode blocks per group: 512
Inode size: 256
so I don't think what you are seeing is excessive.
To use --remote-tempdir you specify the directory as it would be on the
remote machine (and it should exist
Use --remote-tempdir switch to set the temp dir to be used on the remote
machine.
On 21/07/2015 03:15, Stephen Butler wrote:
Thanks Bob,
That sounds like a good lead, The server is running tinycore and /tmp
is in memory.
I've created following folder on server /mnt/hda1/tmp
I've set it to
I don't think temporary space is likely to be an issue on the
destination machine when doing a backup run. But if you want to rule out
the out-of-temp issue at the destination when running rdiff-backup
remotely, you need to use the --remote-tempdir switch, not --tempdir.
Removing the
Thanks for sharing this Clif, it seems a most ingenious and useful tool.
I would still recommend that wherever practicable people regress an
archive to recover disk space (my rdiff-backup-regress utility can help
with this), but if this is not feasible, your script could be a life-saver.
Marcin:
Please look at my utility rdiff-backup-regress at
http://www.timedicer.co.uk/programs/help/rdiff-backup-regress.sh.php
In your case I think you need to run it with -n 2.
Regards, Dominic
http://www.timedicer.co.uk/
On 28/12/2014 19:31, Marcin Zajączkowski wrote:
Hi,
I accidentally
Hello Stephen
Of course you do realise (now!) that you must never delete stuff from an
active repository by using rm...
Assuming you still have, somewhere else, the directory that you deleted
from your repository, I would suggest that you copy this back into the
repository, then run
Your problem I think is that bash expands the asterisks, you could try
this (note the single quotes):
rdiffoptions='-v4 --print-statistics --exclude **Outlook.pst';
or try escaping the asterisks with backslashes...
To properly overcome Outlook.pst being locked, as you have found you
need to
rdiffWeb is maybe 'stale' but it still works fine. If you have problems
installing it, try my helper program:
http://www.timedicer.co.uk/programs/help/rdiffweb-install.sh.php
Dominic
On 09/10/2014 14:03, m...@dkriesel.com wrote:
Am 09.10.2014 15:00, schrieb Dale E. Qualls:
Is anyone using
wiki link in help
regards
Stefan
Am Donnerstag, 9. Oktober 2014, 15:28:49 schrieb Dominic Raferd:
rdiffWeb is maybe 'stale' but it still works fine. If you have problems
installing it, try my helper program:
http://www.timedicer.co.uk/programs/help/rdiffweb-install.sh.php
Dominic
On 09/10
Stephen:
As you seem to be running this under Windows, please try: --exclude **.pst
Dominic
On 08/10/2014 07:09, Stephen Butler wrote:
Hi all,
Having trouble excluding Outlook.pst file from a backup.
Target dir is d:/Users/Steve
And the outlook.pst file is located several sub folders below
I can't see how to do what you want except the slow way, but I also
don't understand what you are trying to achieve, or why you want to
restore past increments.
As far as I can see attic (if that is your preferred choice) doesn't
keep prior versions of backed-up files (or deleted files). I
On 04/09/2014 15:39, Dominic Raferd wrote:
I like that idea. But whereas the initial snapshot takes up almost no
disk space, I think that deleting its rdiff-backup-data directory
would cause it to swell in size by the size of the rdiff-backup-data
directory, or perhaps somewhat more (since
Hello Marco
If you want to do some coding work on rdiff-backup then that would
be welcome, but I think you will be on your own. rdiff-backup is not
under active development at present, sadly.
An alternative is to see if you can prevent the problem of a broken
On 04/09/2014 13:01, Marco Mariani wrote:
Even if it does, it isn't much use if your communication drops are so
frequent that you rarely complete a single backup session, because
your last
usable backup data might be too old for your purpose.
Not only at the level of backup sessions, I must
On 04/09/2014 15:02, Chris Wilson wrote:
Hi all,
On Thu, 4 Sep 2014, Dominic Raferd wrote:
If I had enough space for the LVM snapshot, I would probably rsync
the current
data and run rdiff-backup locally on the destination every time
rsync succeeds.
This would provide - in our setup
You could also consider duplicity http://duplicity.nongnu.org/ which
creates encrypted tar-format
volumes, but it is a different tool to rdiff-backup.
On 25/07/2014 23:10, Egor M. wrote:
No problem. Can't recommend anything here though as I don't
Steve, I'm not clear if the backups to which you are referring are
rdiff-backup archives or just straightforward copies of the source
data. If the former then you could just run rdiff-backup from each
backup location in turn (starting with the oldest) to a single new
Can you give us a bit more informationj? What is the full rdiff-backup
line that apparently causes the problem? What linux os are you running
on the server?
On 24/05/2014 05:57, bt101 wrote:
I'm been stumped by a problem for days.
I use nothing but linux and have been using rdiff-backup for
On 14/04/2014 11:50, Patrick Lauer
wrote:
On 04/14/2014 04:41 PM, Tobias Leupold wrote:
Hello list!
Gentoo Linux has masked rdiff-backup:
Patrick Lauer patr...@gentoo.org (09 Apr 2014)
Dead upstream, has known dataloss bugs.
Please use
this patch and running a backup at this very
moment. Unfortunately it’s taking quite long because I had to
interrupt a previous backup and rdiff is busy with ‘regressing’.
Regards,
Marijn
On 14 May 2014, at 14:07, Dominic Raferd domi
.
attributes / access is not really essential, but preferred!
Thanks,
Marijn
On 15 May 2014, at 10:45, Dominic Raferd domi...@timedicer.co.uk
wrote:
Hello Marijn
Marijn, a similar situation was discussed here quite recently, see
http://lists.gnu.org/archive/html/rdiff-backup-users/2014-03/msg00012.html.
The cause in this case, and probably in yours, is that the source
data is changing while the backup is proceeding. I note that in
On 25/04/2014 03:48, Brice Burgess wrote:
I have a relatively simple rdiff backup script which backs up the
`/home` directory to `/backups/test-target`.
|===
#!/bin/sh
rdiff-backup \
--exclude '**/.git' \
--exclude '**/.svn' \
--exclude '**/.ssh' \
On 29/03/2014 12:40, Marcus Schopen wrote:
Hi,
I got these warnings today, when running an rdiff-backup on some of my
cyrus mailboxes. I did a lvm snap before running backup:
Warning: Attempt to rename over same
inode:
On 26/03/2014 09:41, Thomas Harold
wrote:
On 3/26/2014 4:59 AM, Sam's Lists wrote:
I was removing some old increments on my backup server using:
rdiff-backup --remove-older-than 3M --force root
While this was running a cronjob on a remote
Martin:
See the response on this issue at
http://lists.gnu.org/archive/html/rdiff-backup-users/2004-06/msg00071.html
by Ben Escoto who wrote the original rdiff-backup:
The error is probably caused by files changing as rdiff-backup
processes them. If this happens, rdiff-backup doesn't touch
Marcus, because rdiff-backup works with reverse diffs you can
normally only delete the oldest increments.
rdiff-backup --remove-older-than 5B...
should remove the 5th most-recent increment i.e. the oldest of yours
below.
You could try:
rdiff-backup
Possibilities:
1. Does the backup which causes the problem come from a source which
already has a subdirectory called 'rdiff-backup-data'? This is a
special-purpose directory for rdiff-backup so there might be
problems if it already exists on the source.
2. Are both backup destination
Laurent,
Firstly - thanks for posting, I see you are using a version of my
regression script and I have been able to update it slightly
based on your posting. However this is nothing to do with your main
problem, regarding which the rdiff-backup FAQ here
says:
On 18/12/2013 15:43, Adrian Klaver wrote:
On 12/18/2013 03:29 AM, Ron Leach wrote:
On 16/12/2013 15:28, Dominic Raferd wrote:
Ron, see my utility here:
http://www.timedicer.co.uk/programs/help/rdiff-backup-regress.sh.php
Dominic, thank you for posting this. From its description, it would
1 - 100 of 218 matches
Mail list logo