On 04/28/2013 01:34 PM, Edward Ned 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 an address for Andrew @
is
wrong.
This follows from what I noted above. To do a verify at 1Y ago, it will
(on average) only process 5 rdiffs. It may process 10 or 0, but that's
the average. You are only verifying the backups immediately after the
1Y ago mark.
Matthew Flaschen
Matthew Flaschen wrote:
That is incorrect. Every 10 incremental diffs, rdiff-backup stores
another snapshot of the file. [...] During the restore, rdiff-backup
finds the oldest snapshot at least as recent as the desired backup time
(it could be the current mirror, or one of these snapshots
than you thought.
Matthew Flaschen
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
in the man page.
Really, though, I think the text is clear enough as is.
Matthew Flaschen
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff
padoivi wrote:
Jakob, it looks like you know a bit about this option. Could you tell
me more about how it works ?
The way it works is simple. It tells rdiff-backup, Hey, I'm using a
filesystem that is case-sensitive, even though it appears otherwise.
As multiple people have said, you're /not/
Simon Hobson wrote:
I think the problem, from observation of effect (with MacOS at each
end), not from reading any code is that the data file is processed, and
the recipient is too dumb to realise that the other half will come later
- so it copies the data file (which is different) and the
Dave wrote:
My source directory tree looks like this. I only want to back up the latest
directory under the-stuff-I-want-to-backup.
/
-| some-stuff
| my-stuff
| the-stuff-I-want-to-backup
-| 1001
-| 1002
-| 1003
-| 1004
The
padoivi wrote:
I am pretty sure that I never have two files with the same name
(foo and FOO) and thus a nice option would be
--dont-mess-with-my-file-names-I-know-what-Iam-doing, even though I
understand how risky this could be.
That's what --override-chars-to-quote does. The fact that this
Madan Kumar wrote:
Hi all, I am using rdiff-backup-1.2.8 on WindowsVista and on XP.
I take backup of a single .dat file from following command:
rdiff-backup -b --include D:/Source/myfile.dat --exclude **
D:/Source D:/Dest
I take the backup of this file on irregular interval like sometime
Jakob Unterwurzacher wrote:
Hi!
Madan Kumar schrieb:
Hi all,
I have downloaded the code of rdiff-backup. This code is written in
python language.
I want to compile this code but I dont know Python. Please guide me that
how can I compile it and what should I need for that.
Python is
Josh Nisly wrote:
Attached is a patch to support Unicode on Windows. This fixes support
for filenames with non-ascii characters, and paves the way for long
filename support. Also attached is a patch to prove the correct
behavior, which can be run on Windows or Unix.
FWIW, on GNU/Linux the
of various kinds.
Matthew Flaschen
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
listserv.traf...@sloop.net wrote:
I'm not sure if no 3 covers file errors like files being busy etc...
I'd guess that even if it did, I'd like a code that is basically
everything went smoothly, but some files were locked, or otherwise
unavailable.
This will tell us we got a good backup, but
listserv.traf...@sloop.net wrote:
If it does this, how do you tell in a bash script that anything went
wrong. (Ok, yeah, I could grep the file for Errno...)
People's wrapper scripts are just not that air-tight as to reasonably
expect every file to be accessible. However, I see where you're
Fabrice DELENTE wrote:
Hello.
I'd like to do the following:
I have two computers on which I work. I'd like to sync some directories on
both of these computers, so that both of them always have the latest version
of the files I'm working on.
Depending on the details, consider a revision
Serge Zub wrote:
Hi,
I'm still testing rdiff-backup 1.3.3 under WindowsXP.
Before my backup process is started I need to know -- is the contents of the
source directory changed since last backup (files and directories were added
or deleted, contents of the files were changed).
I assume
Serge Zub wrote:
Oops...
Thank you, Matt.
I need to compare only directory structure and files' content!
Again, then you need to use --compare-full. If it says
metadata changed, data the same: $filename
then you just ignore that line (you could easily do this with grep or sed)
If it
listserv.traf...@sloop.net wrote:
as an aside
I plan to stage backup to a second hard-drive on-line in the system,
and then rsync a copy to a second disk.
Another option to consider is making the backup drive a RAID 1 volume.
Then the mirroring is automatic and occurs at backup time.
Matt
listserv.traf...@sloop.net wrote:
True enough, but that leaves two other problems.
Theft or other loss or destruction of the mirrored drives.
In my scenario, one drive will be either off-site or protected in a
fire-proof safe. It will come on-site (or out of the safe) only to
refresh the
Marcel (Felix) Giannelia wrote:
OK, after writing a few little utilities, I was able to investigate this
further last night and found that the inability to run du is not
entirely rdiff-backup's fault -- one of the machines that's backing up
to this server has a misconfigured sendmail that's
Marcel (Felix) Giannelia wrote:
If a typical restore is only restoring a small part of the filesystem
and only going back a few days, you're right. But I wasn't even
concerned with restore operations -- I want the increment storage to
be more efficient so that I can archive it quickly and
Curtis Osterhoudt wrote:
I just wanted to point out that 7zip isn't proprietary :)
The default distribution, which comes with RAR, is.
Matt Flaschen
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
Jakob Unterwurzacher wrote:
However testing --exclude by dropping test.txt in ~/Downloads shows that
the directory is still being copied over. Is this because the first
time I ran rdiff to the target I did not include --exclude in my script?
Your invocation looks wrong, you're missing a
Daryl Styrk wrote:
Daryl Styrk wrote:
I currently have a simple script to run
rdiff-backup --exclude /home/daryl/Downloads/ /home/daryl/
/media/Lacie/daryl_backup
However testing --exclude by dropping test.txt in ~/Downloads shows
that the directory is still being copied over. Is this
Daryl Styrk wrote:
Where as before 6 7 8 9 10 would have made it over and foo would have
still existed.
Is it possible rdiff-backup does not have deletion permission for the
destination?
Matt Flaschen
Delete permission? I only know of w r x. Wouldn't write be the same as
delete?
Not
Daryl Styrk wrote:
It was ext3. Currently undergoing dd if=/dev/urandom of=/dev/sdb1 . Not
that I gave up on the project. I figured might as well encrypt the drive
with the contents /home if it's going to be sitting around unattended.
Reasonable choice. I recommend cryptsetup(-)luks. You
Moses wrote:
I'm sure not too many people run into this, and its not a bug. I believe
max-file-size just excludes the files like they were not there.. maybe
if they were marked as existing and just ignored somehow that would
work, instead of rdiff believing they were actually deleted? Is so,
Austin Roberts wrote:
Can anyone confirm that this behavior is abnormal for backing up Windows
to Linux?
If it happens every time, it's still an apparent deficiency in librsync
(I doubt rdiff-backup itself).I'm not going to call it a bug,
because I don't understand the rsync algorithm well
Austin Roberts wrote:
Here is a link to the photo: http://home.ausiv.com:85/P5220001.JPG. Bear in
mind that this is happening with lots of files (maybe even a majority of
them). If I can get a copy of the version from my dad, I'll post it as well.
I can't imagine there's any point in posting
Dominic wrote:
But I am not sure what official sanctioning there could be; Canonical
take no responsibility for private repositories, emphasizing 'you should
be happy that you trust the author of the package'. This is something of a
problem IMO.
I disagree. The whole point of PPA is that
Fedor Piecka wrote:
The backup of the most used
machines (they also have the largest amount of data to backup) takes
about 30 minutes. But after that, the verification takes about 12
hours.
Is this normal?
Yes. I think so. The backup obviously only does work on changed files,
but verify
Michael Grant wrote:
On line 77 of robust.py, should this perhaps be exc.errno instead of e.errno?
Yes. It is recommended to upgrade to 1.2.5.
Matt Flaschen
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
bt101 wrote:
tx for the info It's good thing I'm only backing up my stuff. I'd
hate to be an admin who has to explain to users that their stuff
wasn't backed-up.
Except that won't happen. rdiff-backup always backs up each file
(assuming it's in an included directory) at least once. Then,
Michael wrote:
GNUtar includes a file in the incremental backup if the mtime OR ctime
changes. Does rdiff-backup check only the mtime and ignores the ctime?
there isn't anywhere to set ctime to an arbitary date/time?
Apparently, not on POSIX.
Gregy wrote:
Samba can do this very nicely but I see where are you going. I guess
there is simply no easy way of doing this.
I just found a *ix program called convmv
(http://www.j3e.de/linux/convmv/man/) that might actually be just what
you need. It is meant to convert filenames between
Gregy wrote:
Hello, I have a little problem here. I am using rdiff-backup for
linux-linux backups without issue but I have a problem with windows
version. When I backup special characters are not reencoded or
reencoded badly so it appears like '?' on my utf8 linux system. On
windows I am
Andrew Ferguson wrote:
Gregy, you probably have a display issue in your xterm or whatever you
are using to view the filenames on Linux.
The problem is Linux naturally doesn't have first class support for
Windows 1250, since it's a proprietary Microsoft encoding
Alan Douglas wrote:
Buoyed by this success, I'm going to see if I can extend the method to more
general cases. I might also look at hacking archfs to use this approach.
That's probably going to be harder than you think. From what I can
tell, archfs wasn't exactly built with performance
Hans-Christian Armingeon wrote:
Hi,
I'm having some troubles with rdiff-backup 1.1.16.
I hade a backup directory, which I had been using with version 1.1.15. After
the upgrade, I wanted to do a backup. The backup directory ran out of space.
rdiff-backup --check-destination-dir fails
Yuval Hager wrote:
Hi,
I am using rsync.net as the backup server for my home computer. The quota on
the server is limited (this is a pay-by-GB service).
Probably, the best choice is to use:
rdiff-backup --remove-older-than
You can do it repeatedly, in stages, until you're under quota.
Matthew Flaschen wrote:
rdiff-backup follows symbolic links across filesystems with the
--exclude-other-filesystems option enabled. I expected that this option
would cause rdiff-backup to copy a symbolic link that pointed to another
FS without following it. However, rdiff-backup also follows
David wrote:
If the symlink is under the backup source, then in all cases it should
always be copied as a symlink and never followed.
Mea culpa. rdiff-backup is behaving correctly and doing what I expected
originally.
The mistake I made when checking was probably (symlink_dir is a symlink
on
rdiff-backup follows symbolic links across filesystems with the
--exclude-other-filesystems option enabled. I expected that this option
would cause rdiff-backup to copy a symbolic link that pointed to another
FS without following it. However, rdiff-backup also follows such links.
Matt Flaschen
Jon Kolb wrote:
After poking around for a while, I discovered that on encfs/sshfs (or
perhaps fuse in general), os.rename fails with Operation not permitted
if the destination file already exists.
That sounds like a bug in one of fuse/encfs/sshfs. I don't think it
should be worked around in
Matthew Flaschen wrote:
I think the regression did that before it failed. I don't see any
2007-08-10 increments left in the increments directory. When I run
rdiff-backup now I get the below traceback.
Matt Flaschen
I removed the rest of the 2007-08-10 files. Now I get the below error
Matthew Flaschen wrote:
Matthew Flaschen wrote:
I think the regression did that before it failed. I don't see any
2007-08-10 increments left in the increments directory. When I run
rdiff-backup now I get the below traceback.
Matt Flaschen
I removed the rest of the 2007-08-10 files
Andrew Ferguson wrote:
Matthew Flaschen wrote:
Previous backup seems to have failed, regressing destination now.
Regressing to Fri Aug 10 03:40:36 2007
Fatal Error: No metadata for time Fri Aug 10 03:40:36 2007 found, cannot
regress
Matt,
What does `ls rdiff-backup-data` say? From
:36 2007
Fatal Error: No metadata for time Fri Aug 10 03:40:36 2007 found, cannot
regress
Matthew Flaschen
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http
Andrew Ferguson wrote:
[EMAIL PROTECTED] wrote:
I am imagining the following process, please let me know your thoughts:
Step A, Backup Sync:
1. Write changes as diffs against the current repository into
something like $REPO/rdiff-backup-data/scratch/.
2. Simultaneously, write changes
Vahid Pazirandeh wrote:
Hi All,
I love rdiff-backup. However, I don't like how fragile it is when it
crashes during a backup. Let's say the client pushes some backup data to a
remote server, but in the middle of a file transfer, the remote server's
network goes out. The next time
Ralph Lehmann wrote:
What happens here? I do NOT try to restore anything, a wish to create a
backup.
Thanks for your help! :-)
I'm new to rdiff-backup, and I don't know why cygwin is giving you
trouble (not that it's entirely surprising). However, you can try:
rdiff-backup --backup-mode
52 matches
Mail list logo
