SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
rdiff backup doing is doing a full restore every time
Author Message
Post rdiff backup doing is doing a full restore every time 
Question..

I'm using rdiff-backup 1.0.0 (no patches)
The backups were ONLY created with 1.0.0

For machines A, B and C,
- I've done a backup from A to B
- then I'm doing a restore from B to C

The first restore from B to C is transfering every file from A's backup
to the system, C (I think every file.. looks like it at least)
Then when it's done if I immediately do the same restore it copies
everything again.. as if it's not seeing that all the files are then
same as on the destination.

Running on B, the restore command line looks like:

rdiff-backup -v5 --print-statistics --exclude-device-files
--exclude-filelist ../../bin/exclude.lst --exclude-globbing-filelist
../../bin/exclude.additionally_when_restoring.lst --restore-as-of 0D
--force . root < at > C::/

Is --force the problem? I thought that makes it delete on the
destination what didn't exist on the source which is how I want it to
behave.

Any ideas?

Please Help,
Davy

Post rdiff backup doing is doing a full restore every time 
Sorry.. my bad.. dumb user error.. turns out my restore script was using
a backup tree from an older version of rdiff-backup

So it's working great!

-- Davy

Davy Durham wrote:

Question..

I'm using rdiff-backup 1.0.0 (no patches)
The backups were ONLY created with 1.0.0

For machines A, B and C,
- I've done a backup from A to B
- then I'm doing a restore from B to C

The first restore from B to C is transfering every file from A's
backup to the system, C (I think every file.. looks like it at least)
Then when it's done if I immediately do the same restore it copies
everything again.. as if it's not seeing that all the files are then
same as on the destination.
Running on B, the restore command line looks like:

rdiff-backup -v5 --print-statistics --exclude-device-files
--exclude-filelist ../../bin/exclude.lst --exclude-globbing-filelist
../../bin/exclude.additionally_when_restoring.lst --restore-as-of 0D
--force . root < at > C::/

Is --force the problem? I thought that makes it delete on the
destination what didn't exist on the source which is how I want it to
behave.

Any ideas?

Please Help,
Davy




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

Post rdiff backup doing is doing a full restore every time 
On Thu, 18 Aug 2005 14:10:50 -0500
Davy Durham <pubaddr2 < at > davyandbeth.com> wrote:

The first restore from B to C is transfering every file from A's
backup to the system, C (I think every file.. looks like it at least)
Then when it's done if I immediately do the same restore it copies
everything again.. as if it's not seeing that all the files are then
same as on the destination.

No compare is done on a restore. It's exactly that: a restore that
overwrites the destination if --force is specified (otherwise it
expects to create a new directory to restore into).

--
Keith Edmunds

Post rdiff backup doing is doing a full restore every time 
Davy Durham <pubaddr2 < at > davyandbeth.com>
wrote the following on Thu, 18 Aug 2005 15:39:10 -0500
Sorry.. my bad.. dumb user error.. turns out my restore script was using
a backup tree from an older version of rdiff-backup

So it's working great!

Hmm, well in theory it shouldn't matter which version of rdiff-backup
you made the backups with, when restoring it should only overwrite
files that need it.

But since you seem satisfied I won't inquire further :)


--
Ben Escoto

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB