Procedure for restore?

jp_rdiff-backup@gcfl.net jp_rdiff-backup@gcfl.net
Fri, 18 Jan 2002 08:41:12 -0600


OK, so the increments directory contains the whole file instead
of just the differences?  I thought that rdiff actually created
a binary patch file, if you will, of each file that had changed.
What I was trying to understand was how to patch the file from
day 1 to day 7.  But what I think you are saying is that day
7's complete file is in rdiff-backup-data/increments, so I just
get it from there.

So the restore procedure would be:

1. copy all files needed from the mirror directory
2. check rdiff-backup-data/increments to see if there are more
up-to-date files that match the files you are restoring, and
restore them.

Right?

On Thu, Jan 17, 2002 at 10:10:03PM -0800, Ben Escoto wrote:
> Suppose you are backing up to /backup.  Since you trashed it on day 7,
> the data will be in the /backup/rdiff-backup-data directory.  Suppose
> the original file was named /origial/foo/bar then you will want to
> check the directory /backup/rdiff-backup-data/increments/foo.  For
> each different version of bar there will be a dated file, like
> bar.2001-07-15T04:09:38-07:00.snapshot.  To restore the file or
> directory, just run rdiff-backup with the dated increment file and the
> place to put the restored file, as in:
> 
> rdiff-backup
> /backup/rdiff-backup-data/increments/foo/bar.2001-07-15T04:09:38-07:00.snapshot
> /original/foo/bar.new
> 
> There are some more examples on the man page ("man rdiff-backup").
> 
>   JP> I also wonder is there is a rpatch that goes with rdiff...
> 
> Yep, you can use rdiff directly to recover your data.  For instance
> "rdiff patch basis delta new" writes to "new" the result of applying
> patch "delta" to "basis".  Try "man rdiff" for more information.
> 

-- 
Today's funny quote of the day:
The only substitute for good manners is fast reflexes.

www.GCFL.net (The Good, Clean Funnies List): Good, clean funnies
five times a week, FOR FREE & no ads in the mailings!

The information transmitted herein is intended only for the person
or entity to which it is addressed and may contain confidential
and/or privileged material.  Any review, retransmission,
dissemination or other use of, or taking of any action in reliance
upon, this information by persons or entities other than the
intended recipient is prohibited.  If you received this in error,
please contact the sender and delete the material from any computer.