rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] rdiff-backup 1.1.10 released


From: rdiff
Subject: Re: [rdiff-backup-users] rdiff-backup 1.1.10 released
Date: Thu, 17 May 2007 11:55:27 -0700 (PDT)


On Thu, 17 May 2007, dean gaudet wrote:
If you have large 1.0.5 repositories, can you test upgrades to 1.1.x from
1.0.5 and see what kind of metadata needs fixed up?  Regression procedure
which comes to mind is:

  rdiff-backup-1.1.x /some/data /backup/1.0.5-data/
<ctrl-c before it finishes, check it, run again and let it finish>
  rdiff-backup-1.1.x --check-destination-dir /backup/1.0.5-data/
  rdiff-backup-1.1.x /some/data /backup/1.0.5-data/
<test to see if we can restore from 1.1.x data after a 1.1.x backup>
  rdiff-backup-1.1.x -r 0B /backup/1.0.5-data/some/directory /restore0/
<test to see if we can restore from 1.0.5 backups after a 1.1.x backup>
  rdiff-backup-1.1.x -r 2B /backup/1.0.5-data/some/directory /restore1/

no no i'm waiting for other people to test :)

I've gota ~50gb backup with a bunch of small files in it to try with the procedure above. I'll report back soon! Does anyone else have repositories they can test with?

-Eric





-dean

On Thu, 17 May 2007, address@hidden wrote:

On Tue, 15 May 2007, dean gaudet wrote:

i'd also like to know if there are any folks doing large backups with
1.1.x:  a few million files minimum, 0.5 TB+, non-zero quantities of
hardlinks...

as i mentioned i'm still using 1.0.5 and probably won't switch soon, so
i'm relying on the community to provide enough proof that 1.1.x is
actually stable.

Dean,

If you have large 1.0.5 repositories, can you test upgrades to 1.1.x from
1.0.5 and see what kind of metadata needs fixed up?  Regression procedure
which comes to mind is:

  rdiff-backup-1.1.x /some/data /backup/1.0.5-data/
<ctrl-c before it finishes, check it, run again and let it finish>
  rdiff-backup-1.1.x --check-destination-dir /backup/1.0.5-data/
  rdiff-backup-1.1.x /some/data /backup/1.0.5-data/
<test to see if we can restore from 1.1.x data after a 1.1.x backup>
  rdiff-backup-1.1.x -r 0B /backup/1.0.5-data/some/directory /restore0/
<test to see if we can restore from 1.0.5 backups after a 1.1.x backup>
  rdiff-backup-1.1.x -r 2B /backup/1.0.5-data/some/directory /restore1/

If that procedure succeeds on a few large data sets, then I might be willing
to take the leap.  I half-expect metadata warnings/errors which will need
fixedup.

-Eric




-dean

On Tue, 15 May 2007, Greg Freemyer wrote:

Dean,

Once enough time has gone by to move this to stable on the front page
please post another e-mail.

FYI: I tried to get OpenSUSE factory to update to 1.1.10, but they
said no because it was a devel/unstable release.

Thanks
Greg

On 5/13/07, dean gaudet <address@hidden> wrote:
i realised i'd moved my rdiff-backup mail folder after linux-kernel in
my
tab list... and hadn't got past linux-kernel in months.  oops.

better late than never.

as before, i haven't tested it (i'm still using 1.0.5), i'm just
releasing
it because there was a request for a new release.

-dean


New in v1.1.10 (2007/05/12)
---------------------------

New --exclude-if-present option (i.e. --exclude-if-present .nobackup).
(Jeff Strunk).

Use signal 0 rather than signal.NSIG when testing if another
rdiff-backup
is still running.  (Patch from Sébastien Maret)

Sockets don't have extended attributes -- don't try to access them.
(Patch from Andrew Ferguson.)

Fix restore from read-only bug -- rx perms on a repository directory are
enough, no need for write perms when restoring.  (patch from Andrew
Price)

Fix --list-increments bug in set_must_escape_dos_devices.
(Marc Dyksterhouse)

_______________________________________________
rdiff-backup-users mailing list at address@hidden
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL:
http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki



--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century

reply via email to

[Prev in Thread] Current Thread [Next in Thread]