Hi,
Arno Wagner a...@wagner.name wrote:
I found a bit more time and found also some .pm files
with the same issue. Looking into the files though,
I have a suspicion, namely that for some reason these
files were changed by a Debian update, that then did
set the same original metadata after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Scott Jilek sc...@bytality.com wrote:
On 3/24/2011 3:42 PM, Chris Wilson wrote:
Hi Scott,
On Thu, 24 Mar 2011, Scott Jilek wrote:
Unfortunately, I can't just touch the file because it's in use and
locked by the truecrypt process.
In that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-03-26 08:27, Patrick Nagel wrote:
If that TrueCrypt volume is mounted anyway, why don't you just
rdiff-backup the files inside it into another TrueCrypt volume on the
backup system?
Patrick.
Hi Scott,
Hm... I think I might have used
-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 tried adding the --compare-hash switch.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dominic,
On 2011-02-01 17:14, Dominic Raferd wrote:
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
Hi,
I have been running rdiff-backup on multiple servers for a couple of
years, and never saw something that comes even close to what I just got
from one of the backup servers. The output is attached - I replaced some
file names with 'X's - those were normal file names, containing customer
and
Hi Eric,
On 2010-06-21 19:39, Eric Beversluis wrote:
Well I rebooted and then it ran fine. Does that mean it is _necessary_
to run rdiff-backup with a clean boot, or does anyone have some other
explanation for the errors I got?
Thanks
On Mon, 2010-06-21 at 07:27 -0400, Eric Beversluis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matthew,
On Sunday 30 August 2009 02:05:48 Matthew Miller wrote:
I'd like to have one backup with different expiration policies -- is this
possible, or do I need to split it up? Thanks!
AFAIK you will have to split it up.
Patrick.
- --
Key
But the whole discussion still doesn't explain why it's so much slower during
the *first* run (that's what Scott's mail was about, if I'm not mistaken). In
that case, rsync/rdiff-backup should be (roughly) as fast as NFS, if there is
no processing bottleneck on the machine that's running both
Hi,
On 2009-07-20 08:07, Dean Cording wrote:
My understanding of rdiff-backup is that effectively nothing is ever deleted
and therefore the backup size should always be increasing. For example, if I
create a 1Mb file, back it up and then modify 500Kb worth of the file, then
the next backup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Harry,
On 2009-07-10 22:42, Harry Putnam wrote:
Ended up copying 23 GB... but the nasty thing is, it took a whopping
6+ hrs... from the session-stats log:
ElapsedTime 21751.67 (6 hours 2 minutes 31.67 seconds)
I guess it would help to have
Hi,
On 2009-05-07 14:14, Gregy wrote:
Wouldn't it be easier to just follow the guide located on the wiki?
There is step-by-step how to configure rdiff-backup on windows as a
client to linux server. Or do you want windows to be the server?
Oh, right, there is a Wiki article:
Hi Chencho,
On 2009-05-06 23:02, Chencho wrote:
Now i want to develop an app (windows platform will be 99% users) to make
this external incremental backups directly from the desktop, without office
server.
I'm not sure how configure ssh in each desktop to not ask about password,
and i think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 2009-01-31 06:09, Andrew Ferguson wrote:
[...]
Fortunately, the fix is simple. In selection.py just change lines 534
and 535:
if min_max: sel_func = lambda rp: (rp.getsize() = size)
else: sel_func = lambda rp:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Randy,
Randy Orrison wrote:
I suppose this is a strange request. I used to use rsync to create and
update a mirror of my /home directory (on /backup/home, where /backup is an
external USB drive). This is my home PC, used just by my family, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Oliver Hookins wrote:
| Hi, I posted about this issue a while ago but I'm having a hard time
| diagnosing the problem since there is no logging on the client side. We are
| doing backups by initiating from the backup server, and for some reason
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ahd71 wrote:
| Yes I tried all combination I could imagine except changing the working
directory (smart thinking!!!).
| Unfortunatly it didn't work either. Maybee I'm doing something wrong with my
'globbing-file'?
|
| My goal is to backup a windows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andrew,
thanks for getting back to me about this.
Andrew Ferguson wrote:
| On Aug 10, 2008, at 8:17 AM, Patrick Nagel wrote:
| today's backup gave me the following message:
|
| Warning: Attempt to rename over same inode:
| /mnt/sdb1/backup/some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
today's backup gave me the following message:
Warning: Attempt to rename over same inode:
/mnt/sdb1/backup/some/path/rdiff-backup.tmp.3491 to
/mnt/sdb1/backup/some/path/some_filename
Is it something I need to worry about?
Patrick.
- --
Key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Mico Siahaan wrote:
| I built rdiff-backup 1.2 python binary module for Windows using MinGW. The
module can be downloaded here:
http://www.intermatik.co.id/download/ftp/rdiff-backup/rdiff-backup-1.2.0.win32-py2.5.exe
.You need python 2.5 to make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I read a lot about a native Windows port of rdiff-backup going on. Andrew
Ferguson mentioned it (stating that he thinks it's finished) in the
announcement of version 1.1.17, for example.
Now I have a few questions, regarding this port:
* Is it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
David Sickmiller wrote on 2008-06-07:
| I'm using rdiff-backup to run a nightly backup across the Internet from
| a production server to a backup server. I'd like to be able to produce
| monthly snapshots and save them on removable media. It'd
Hi Bert,
Bert Hiddink (Monday, 2008-06-09):
If I would like to implement:
rdiff-backup [EMAIL PROTECTED]::/source-dir [EMAIL PROTECTED]::/dest-dir
...rdiff-backup should be installed on ALL hosts, that is, local host,
host1 and host2?
Why don't you just
ssh [EMAIL PROTECTED] rdiff-backup
Hi Mike,
Mike Green (Monday, 2008-05-12):
[...]
Is there a way of getting rdiff-backup to use the current working copy
on the backup machine rather than trying to push the lot across again?
My initial thought was to make a second copy on the backup machine,
however we do not have the free
Hi Richard,
Richard Chapman (Tuesday, 2008-04-29):
It appears to me that both rdiff-backup and rsnapshot would do a good
job for me. Could anyone provide their thoughts on the relative
strengths and weaknesses of the two tools.
I have posted a similar request on the rsnapshot list - and have
Hi Josh,
Josh Nisly (Friday, 2008-04-04):
I'm attempting to make a native Windows port of rdiff-backup. I've
succeeded so far in building librsync and rdiff-backup's cmodules, as
well as fixing rdiff-backup's fs_abilities checks. What I'm running up
against now is that there seems to be a lot
Hi there,
I'm new to rdiff-backup, and so far I find it to be a great tool. During this
night's (incremental, the script runs for the 5th time or so) backup of four
vservers, I encountered a batch of errors that looked like:
SpecialFileError var/run/dovecot/auth-worker.2765 Socket error:
27 matches
Mail list logo
