[rdiff-backup-users] Nooooooooo!

2005-08-19 Thread JonathanSmith
I attempted to restore a set of files to a directory and was told: Fatal Error: Previous backup to /mnt/e3 seems to have failed. Rerun rdiff-backup rdiff-with --check-destination-dir option to revert directory to state before unsuccessful session. I fail to understand the instruction, find no s

[rdiff-backup-users] Version 1.0 what about the old ones?

2005-08-19 Thread Steve Clement
Hi, I maintain the rdiff-backup port on FreeBSD but am not willing to update to 1.0 just yet because of obvious reasons :) Could you put past releases onto the site so we can at least see the old_stable versions (which work better at the moment than 1.0) Also calling 1.0 stable is a bit "poor" as

Re: [rdiff-backup-users] Version 1.0 what about the old ones?

2005-08-19 Thread Gary Mu1der
Steve, I'm actively using the FreeBSD port of rdiff-backup. If you need any testing done, I'd be happy to help. Gary Steve Clement wrote: Hi, I maintain the rdiff-backup port on FreeBSD but am not willing to update to 1.0 just yet because of obvious reasons :) Could you put past releases on

[rdiff-backup-users] continuing halted backup

2005-08-19 Thread Noah
Hi there, I am backing up 41GB of data and due to a netowrk error my stream was interrupted. is there any way to continue this halted backup? the error message I am seeing is: --- snip --- # ./backup.sh Fatal Error: Bad rdiff-backup-data dir on destination side The rdiff-backup data directory

Re: [rdiff-backup-users] current version versus 0.6 - old better?

2005-08-19 Thread Ivo Michiel
When I give the option do not create meta-files, is that the solution? Thanks Ivo On Sat, 6 Aug 2005, Ben Escoto wrote: > > Ivo Michiel <[EMAIL PROTECTED]> > > wrote the following on Thu, 12 May 2005 14:26:35 +0200 (CEST) > > > I use rdiff-backup for several yaers now version 0.6. > >

Re: [rdiff-backup-users] Version 1.0 what about the old ones?

2005-08-19 Thread dean gaudet
On Fri, 19 Aug 2005, Steve Clement wrote: > Also calling 1.0 stable is a bit "poor" as it seems we haven't tested it > enough :( i dunno... i've been using 0.13.x since forever, and top of CVS since i gained commit privs... and it's always been stable enough for me. what you're seeing now is a

Re: [rdiff-backup-users] Nooooooooo!

2005-08-19 Thread dean gaudet
On Fri, 19 Aug 2005, JonathanSmith wrote: > I attempted to restore a set of files to a directory and was told: > > Fatal Error: Previous backup to /mnt/e3 seems to have failed. > Rerun rdiff-backup rdiff-with --check-destination-dir option to revert > directory to state before unsuccessful sess

Re: [rdiff-backup-users] continuing halted backup

2005-08-19 Thread dean gaudet
On Fri, 19 Aug 2005, Noah wrote: > Probably this error was caused because the first rdiff-backup session > into a new directory failed. If this is the case it is safe to delete > the rdiff_backup_data directory because there is no important > information in it. yeah do what the error message say

Re: [rdiff-backup-users] UpdateError

2005-08-19 Thread dean gaudet
On Thu, 18 Aug 2005, Davy Durham wrote: > Is this serious? I get a few like this while backing up.. > > UpdateError var/log/secure Updated mirror temp file > ./var/log/rdiff-backup.tmp.1685 does not match source unfortunately there's always a race condition when backing up from a live files

Re: [rdiff-backup-users] UpdateError

2005-08-19 Thread David Kempe
dean gaudet wrote: (on a related rant: it's unfortunate linux 2.6 LVM2 doesn't have stable snapshots yet... i'm stuck on 2.4 still because i want snapshots.) well 2.6 is the development kernel :) dave ___ rdiff-backup-users mailing list at rdiff-b

[rdiff-backup-users] RE: Nooooooooo!

2005-08-19 Thread JonathanSmith
O.K., dean, I followed your advice, which seemed to work. The command took about eight hours to process and ended with no message. So, is that a good thing, bad thing, or too soon to tell? ___ rdiff-backup-users mailing list at rdiff-backup-users@nong

Re: [rdiff-backup-users] RE: Nooooooooo!

2005-08-19 Thread dean gaudet
On Fri, 19 Aug 2005, JonathanSmith wrote: > O.K., dean, I followed your advice, which seemed to work. The command took > about eight hours to process and ended with no message. > So, is that a good thing, bad thing, or too soon to tell? it probably worked... try another backup now... -dean ___

Re: [rdiff-backup-users] current version versus 0.6 - old better?

2005-08-19 Thread Ben Escoto
> Ivo Michiel <[EMAIL PROTECTED]> > wrote the following on Fri, 19 Aug 2005 16:15:59 +0200 (CEST) > > When I give the option do not create meta-files, is that the solution? There's no option anymore not to create a mirror_metadata file. I guess you could delete the ones you have, but I w

Re: [rdiff-backup-users] Version 1.0 what about the old ones?

2005-08-19 Thread Ben Escoto
> Steve Clement <[EMAIL PROTECTED]> > wrote the following on Fri, 19 Aug 2005 15:20:31 +0200 > Hi, I maintain the rdiff-backup port on FreeBSD but am not willing to > update to 1.0 just yet because of obvious reasons :) > > Could you put past releases onto the site so we can at least see t

Re: [rdiff-backup-users] SECURITY: Not all file ops accessed via vetted RPath objects? Also a path prefixing patch

2005-08-19 Thread Ben Escoto
> Charles Duffy <[EMAIL PROTECTED]> > wrote the following on Thu, 18 Aug 2005 06:39:44 -0500 > > Yes, I have one (netcat on the client, tcpsvd on the server). That's > fine, it works -- but it rules out the (SSH-based) multi-server > authentication mechansims which have been thus far sugg

[rdiff-backup-users] Backing up multiple directories

2005-08-19 Thread Jochem van Leeuwen
Hello, I'm new to the list (and actually never post in mailing lists), so excuse me if I make a mistake or something. I've searched the archives for my 'problem', to no avail. The older archives don't allow you to search and my search on Google didn't give me any good results either. My qu

[rdiff-backup-users] A BIG Thanks!

2005-08-19 Thread Davy Durham
Hey Ben et al, I just wanted to issue out a thanks for the great tool! I've just successfully done hardware maintenance (i.e. swaping out old harddrives for new ones) over a remote connection hundreds of miles away on 8 of our production servers where I work. The tool saved MUCH time in do