Hi Dean,
We can probably start testing on windows pretty soon, so hang in there.
You could probably get the jump on it and try follow along here:
[ https://github.com/ericzolf/rdiff-backup/tree/ericzolf-py2to3 |
https://github.com/ericzolf/rdiff-backup/tree/ericzolf-py2to3 ]
If you want to
Yeah I dunno what happened. I responded on my phone, anyway, I was committing
to getting back rdiff-backup.org
Dave
> From: "EricZolf"
> To: "Rdiff Backup"
> Sent: Monday, 5 August, 2019 1:45:18 AM
> Subject: Re: [rdiff-backup-users] Future of rdiff-backup: Python 3 migration
> and
>
___
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
I think rdiff-backup 3 sounds great.
> From: "Otto Kekäläinen"
> To: "EricZolf" , "Andrew Foster"
> Cc: "Rdiff Backup"
> Sent: Friday, 2 August, 2019 8:13:53 PM
> Subject: [rdiff-backup-users] Bump major release version for rdiff-backup?
> Hello!
> With the adoption of librsync2 the old MD4
> PS: Speaking of saving the Debian package, it's also important but it should
> be
> enough for Otto to claim ownership to suspend removal. My times as Debian
> maintainer are long gone (Freemind, Freeplane and a few other packages) but
> Debian isn't known for changing fast ;-)
to use and support rdiff-backup,
and particularly Eric Zolf, who has put in some serious coding time to get
Python3 support happening recently.
Please let me know what I can do to help.
Dave Kempe
> From: "Patrik Dufresne"
> To: "Dale E. Qualls"
> Cc: "R
not be aware of, will be
gladly received. I believe Wes was hoping to make a release next week sometime,
but perhaps later depending on some other commitments he has.
--
Regards,
Dave Kempe
http://sol1.com.au
> From: "Patrik Dufresne" <ikus...@gmail.com>
> To: "Rdiff
> From: "Greg Troxel"
> Subject: Re: [rdiff-backup-users] Sol1 taking over rdiff-backup
> What's the motivation for leaving FSF hosting and moving to corporate
> hosting?
Better tools mainly. There seemed to be a consensus amongst the previous
maintainers.
thanks
Dave
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 from the
most recent maintainer(s).
We will be migrating the code to github:
https://github.com/sol1/rdiff-backup
I have been triaging
Hey,
we just renewed rdiff-backup.org domain rego. It redirects to
http://www.nongnu.org/rdiff-backup/ .
Anything else anyone wants to do with it? We are happy to continue
rego/hosting/redirection whatever.
--
Regards,
Dave Kempe
___
rdiff
From: Nikolaus Rath nikol...@rath.org
To: rdiff-backup-users@nongnu.org
Cc: Balázs Czviin czv...@gmail.com
Sent: Saturday, 9 November, 2013 1:15:32 PM
Subject: [rdiff-backup-users] Duplicate rdiff-backup's temporary files?
Thus my question: would someone be willing to help out from the
From: Stavros Korokithakis stav...@korokithakis.net
To: rdiff-backup-users@nongnu.org
Sent: Sunday, 8 September, 2013 3:04:24 AM
Subject: [rdiff-backup-users] Encrypted backups
Hello,
I would like a solution that will take incremental, remote backups.
Basically, what I want is exactly
and disk space.
Hi Jeffrey,
we frequently backup files larger than this all the time. It is reasonably
efficient, as diffs are compressed. Is the audio already compressed?
--
Regards,
Dave Kempe
___
rdiff-backup-users mailing list at rdiff-backup-users
- Original Message -
From: Stefan Lisowski s.lisow...@isti.com
To: rdiff-backup-users@nongnu.org
Sent: Wednesday, 5 June, 2013 3:35:32 AM
Subject: [rdiff-backup-users] Recovery to Linux from Windows
Our Linux box died, so now we're restoring from a rdiff-backup
repository on a
You need to account for the mirror_metadata file as well I think. And of course
any other metadata files in the rdiff-backup-data directory if they concern you
(but are probably not crucial)
--
Regards,
Dave Kempe
Solutions First
Phone: (02) 9923 2180
Mobile: 0413 022 143
Support
- Josh Nisly rdiffbac...@joshnisly.com wrote:
There's nothing inherent in rdiff-backup that prevents password-based
authentication, but putty (and plink) are broken (in technical terms,
they print the password prompt to stdout instead of stderr). What I
ended up doing was building my
Terry wrote:
that's interesting I am looking for a way to backup some laptops when
they connect to the lan.
Mostly documents and stuff but the big thorn in my side is there pst
files which are GB's in size plus outlook process is often
not closed correctly due to add-on like Ack hanging on to
Josh Nisly wrote:
Since we're talking about this anyway...
I operate a small business providing online backup service, centered
around rdiff-backup. I've built an installation and backup selection
GUI on top of it so that it's easy to use, and have rdiffWeb set up
for easy data restoration.
Rodney Schuler wrote:
I had found rdiffweb. Nice project. Not quite what I was looking
for. I did not want to bother with the web server setup/maintenance.
rdiffweb includes the webserver in the package. Can't see how its any
harder than archfs or anything else.
if you are using
Dominic wrote:
As a Ubuntu 8.10 user I think it is a good idea. I have my own script
for downloading and installing the latest rdiff-backup, but it would
be particularly helpful if other related utilities (such as archfs
(with patches!), rdiffweb etc) could also be put in your repository -
Michael wrote:
Hi,
I'm very new to rdiff-backup. I read a few places that if backup
process is interrupted while in progress, the backup folder may be
corrupted. Since every older version depend on the mirror copy,
basically all the increments become useless. Have I got it right so far?
Hi
Helge Milde wrote:
Can you elaborate on this, please? I don't understand what's technically
preventing rdiff-backup from letting me restore a backup from (for
instance) a given date. As far as I understand, rdiff already has all
the data it needs to do a restore, and since it should be a
Dominic wrote:
Can one have multiple rdiff-backup sessions running from different
clients simultaneously to one server but to different repositories (I
hope and have assumed so, because this is bound to happen with push
backups, which is the solution I am working towards)?
all the locking
Dominic wrote:
Well it may be a plug, but it's justified IMHO for an open-source
product that I had not heard of and that is based on rdiff-backup.
Safekeep is not mentioned at
http://www.nongnu.org/rdiff-backup/related.html. Looks good enough for
me to wish I had seen it earlier. But is it
Dave Kempe wrote:
thats a good point - we should also add backupninja to that list as well.
Although, they are on the wiki:
http://wiki.rdiff-backup.org/wiki/index.php/ContribScripts
dave
___
rdiff-backup-users mailing list at rdiff-backup-users
Helge Milde wrote:
If it is intended, are there any workarounds for this? We need to be
able to restore a backup within minutes, and a backup process can last
for 6+ hours (and we do them twice a day).
I believe this is intended behaviour. The backups are mean to be atomic.
Thus its not
Simon Hobson wrote:
Is it normal for the target of a backup to show 100% wait-io during a
backup ?
Both systems are guests on a Xen host with a 4core 2.4G processor and
plenty of ram (the target currently has over 1G free). rdiff-backup is
ver 1.2.1
I dunno about fixing rdiff-backup in
[EMAIL PROTECTED] wrote:
1. I found that generating an SSH key pair with puttygen.exe
generates keys in a Putty-specific format which therefore can not be
imported into Linux. Despite munging them in various obvious ways
(trying to make them look like keys from ssh-keygen) I couldn't
get them
Farkas Levente wrote:
2.
and such errors and warnings still exists:
---
ListError mnt/windows/f/shared/Document/2007/Hansol/Tectonbol/Jakab
Tamastol pendrive/07_0120_Hansol data/hansol/Gas ?? ???.dwg [Errno 2] No
such file or directory:
Mico Siahaan wrote:
Hi Andrew,
thanks, the current CVS version seems work well. I succeeded made
Windows distribution for CVS version of rdiff-backup. It made for
python 2.5. I also added some simple batch scripts into it. Anyone
Hi,
this seems to work pretty well in the basic tests I have
Mico Siahaan wrote:
Hi Andrew,
thanks, the current CVS version seems work well. I succeeded made
Windows distribution for CVS version of rdiff-backup. It made for
python 2.5. I also added some simple batch scripts into it. Anyone who
interested to try it can download from:
Josh Nisly wrote:
I've been backing up to a repository daily for a year and a half, and
over my 300ms latency link, it takes 30 minutes to run
--check-destination, which runs for over 30 minutes, then says, Fatal
Error: Destination dir does not need checking. With this patch, it
takes about
Madan Kumar wrote:
Hi all,
I am new to rdiff-backup. No doubt
that it provides great functionality but I am facing problem with it,
please do me some needfull.
I amusing rdiff-backup on windows
Vista and on XP.
I have downloaded the setup.exe for
windows by following the
pblahman wrote:
Doing an rsync of the rdiff-backup tree to another system, CentOS 5.1.
rdiff-backup is the same version 1.0.5 but with later version of python.
did you try rsync with --delete? you probably have too many mirror
markers
dave
mortee wrote:
Hi,
I just had rdiff-backup erase *all* my backups. That is just plain wrong.
Hi mortee,
I have had a similar issue which actually erased my / directory, (well a
staff member did it). This was because he used --force with a restore
and ended up erasing his root (/)
The bad news is that if my first set gets corrupted, then rsync will
relay the corruption out to the offsite copy. My reason for two
copies is disaster recovery, not backup repository corruption. May
need to rethink that based on this discussion.
That is exactly why I rdiff-backup the
Warren Guy wrote:
Is anyone is aware of a compatibility matrix of sorts for various
versions of rdiff-backup? Or perhaps even a summary of which versions
potentially break compatibility with previous versions? I have been
unable to find such a thing.
Hi Warren,
I don't think there is such a
Lorenzo Campanelli wrote:
Having the bad filesystem? clue led me to run fsck.ext3 (without
autorepair) a couple of times on the partition, but the error keeps
happening. The rdiff-backup process continues and seems to run
indefinitely, although as of this writing I am letting it churn out
Chris G wrote:
Will doing an rdiff-backup of a file hierarchy created by rdiff-backup
cause any problems?
nope we do this all the time.
just make sure you rdiff-backup the parent directory of any rdiff-backup
repos. you may need to create an extra directory structure to make this
happen
Brandon Saxe wrote:
The problem is this: If I lose my USB hard drive, then
I lose all my backups. Now, I know that a real backup
scheme requires one to have two copies of the backups,
but that kind of defeats the purpose of using an
efficient tool like rdiff-backup. I don't want to copy
all
Andrew Ferguson wrote:
It looks like you are using rdiff-backup to backup another rdiff-backup
repository. Are you sure this is what you want to do? That is not
something usually done.
While i agree with everything Andrew has said regarding long filenames
and such - on filesystems that don't
micah wrote:
The one downside that maybe wasn't accounted for is that this breaks
rdiff-backup between Debian stable and both Debian testing and unstable.
This means that to backup a Debian stable system with rdiff-backup, one
needs to backup to another stable system, whereas before this
Joe Beda wrote:
To make rdiff-backup work for me, I'd have to add the following
features initially:
1) Support for recovering dropped or lost backups.
2) Support for handling moved files.
3) Add sneaker net type backups.
In addition, I'd be very interested in hearing anyone's experience
with
RudySC wrote:
/usr/lib/libpopt.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[2]: *** [rdiff] Error 1
make[2]: Leaving directory `/usr/local/src/librsync-0.9.7'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
Hi Rick,
we routinely handle massive amounts of files and data. Rdiff starts the
backup at the begining and doesn't hold the list of files and metadata
in memory like rsync, so it doesn't suffer from that problem as much.
a 200Gb backup job is fine. I have a few 900Gb jobs that work ok as
gone
through a similar changeover.
I hope you can further duplicity and make it a more supported product.
If nothing else, just forking it and going it alone is sure to keep the
code alive...
thanks,
Dave Kempe
rsync.net wrote:
Hello,
Many of the customers of rsync.net use duplicity
Jeff have you tried --remove-older-than 30B for 30 backups?
that might do what you want.
Other than that, I always use --force on remove-older-than if space is
the problem - deciding between having the next backup complete and
loosing an extra increment.
dave
Jeff Simpson wrote:
I know I
http://solutionsfirst.com.au/~dave/backup/rdiff-backup1.0.1w4.exe
Karjala wrote:
Where is the setup.exe? Does it use CygWin like my version of
rdiff-backup does/
http://solutionsfirst.com.au/~dave/backup/rdiff-backup1.0.1w4.exe
Yes it uses Cygwin.
Is it open source?
yes.
dave
If you look in the setup.exe version I make that work with a batch file.
You might want to install that to get some hints.
dave
Karjala wrote:
Thanks, the installation was very smooth.
Now, how would you automate the process of backing up?
On UNIX I used cron for this.
On Windows I'm
Marc Haber wrote:
This is a real turn-off because it is not always feasible to roll
updates to all machines immediately. I'd expect a _backup_ tool to at
least offer some kind of backwards compatibility.
Yeah I was a bit disappointed too as well, but to be fair, 1.1.5 is
clearly the
Jason Faulkner wrote:
We are using rdiff-backup version 0.13.4-5 on Debian Sarge.
Thanks for any suggestions.
Hi, yeah you need to upgrade rdiff-backup to a newer version and get the
latest librsync from cvs. I am not sure any released version have the
patch for these large file errors. it
Jason Faulkner wrote:
If you can send your source deb my way, I'll make some modifications so
it works with sarge and compile a binary myself, unless you can attest
the hoary ones work on sarge out of the box.
I don't have access to the source debs atm (on on of my guys laptops). I
will see
Vadim Kouzmine wrote:
1) rdiff-backup 1.1.5 vs. 1.0.4
2) python 2.4.2 vs 2.2.3
I noticed a speed up (just visually) between python 2.2 and python 2.3
dave
___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
Martin Kos wrote:
so i thought perhaps i can use rdiff-backup when i mount the samba share
on my host (i used cifs) but rdiff-backup stops with the attached error
when i use a mounted samba share as destination.
i used rdiff-backup 1.1.5.
is this a problem of unsupported filesystem functions
[EMAIL PROTECTED] wrote:
Python seems to be running fine and I can get version information
from RDIFF, so it is at least somewhat working. Compilation and
building went fine, with no error.
you are missing the python-gzip module stuff.
rdiff is not rdiff-backup
what does rdiff-backup -V give
Wiebe Cazemier wrote:
I really think this feature should be part of the next stable release,
because now I can't fully trust my backup to be accurate.
the feature is in the development version... have you tried it?
On a sidenote, the wiki at
Felix Matschke wrote:
Did anybody experience the same error message?
I get it when rdiff-backup is not installed correctly.
or more specifically when the sitepackages dir is not available.
actually, it might be slightly different, but I would think its some
sort of installation/path error.
Hi,
I am trying to backup to ncpfs (the novell netware filesystem)
I have tried it on 0.13.4 and 1.1.5 both give the same error.
here is 1.1.5 traceback
Ben, if you want more tests to figure out more tests that might need
skipping or adjusting, let me know its a pretty exotic filesystem
Ben Escoto wrote:
Interesting, I've never been able to reproduce that bug (I haven't
seen it for years, but it gets reported occasionally on the list).
How much data is involved? Small enough that could you tar it up and
have me download it?
I deleted the old file that was causing problems
Golden Butler wrote:
Why would rdiff-backup fail at this point? If I can't get rdiff-backup
to backup a folder with three small text files, how would ever get it
backup up my company's data of over 50 GB? Any help or suggestions is
greatly appreciated.
Where you using FAT32 on this drive? I
Golden Butler wrote:
./backup-homes: line2: 703 Segmentation fault rdiff-backup /home /bkps/homes
Segmentation fault? Funny thing is, the first Full Backup runs fine.
This error shows up when the incremental backup occurs. The total size
of the /homes is about 19GB.
Can you run the
Hi,
I am trying to get rdiff-backup 1.0.1 going on cygwin. I will have a
windows package built shortly, but I would love it if windows- windows
backups worked.
the initial backup works ok, but after the session stats are printed at
the end I get an error similar to the one below. Thats fine,
Hi,
fsyncing problems notwithstanding, rdiff-backup for windows 1.0.1 is now
available.
it seems to work as well as the last versions :)
http://solutionsfirst.com.au/~dave/backup/rdiff-backup1.0.1w4.exe
let me know if there are any fixes needed.
I did see someone had written a cool batch file
63 matches
Mail list logo