Re: [rdiff-backup-users] Newbie question: Restore target already exists

[Sherrard Burton]

Well those restore options are the result of another closely-related
issue. Sometimes we end up having to restore multiple sets of files down
a given path. For example, maybe we want to restore files from
/u/jdoe/Maildir/new/, /u/jdoe/Documents/ and /u/tsmith/Maildir/cur/, but
in multiple phases. Instead of restoring everything to/tmp/restore, we
would like to restore the original tree as much as possible. That way
you don't have to move jdoe's mail files before you restore tsmith's
mail files. It also means that you don't have to pick through
/tmp/restore to and separate jdoe's documents from his mail files and
tsmith's mail files.

In a nutshell, we don't want to have to do restore, move, restore,
move...


On Mon, 2003-03-03 at 15:08, Ben Escoto wrote:
> >>>>> "SB" == Sherrard Burton <address@hidden>
> >>>>> wrote the following on 03 Mar 2003 10:59:59 -0500
> 
>   SB> Is there a way to force a restore into a directory, or down a
>   SB> set of directories that already exist?
> 
> Yes, you can specify --force, but then anything in that directory that
> isn't present in the restore will be deleted.  It sounds to me like
> you want some kind of --no-delete option which prevents this.
> Unfortunately there is no such option.  However, you can run:
> 
>   SB> rdiff-backup -r 1D --include '/tmp/restore/u/jdoe/Maildir/new/'
>   SB> --exclude '**' /u-backup/ /tmp/restore/
> 
> Then:
> 
> cp /tmp/restore/u/jdoe/Maildir/new/* /u/jdoe/Maildir/new/
> 
> then something like:
> 
>   SB> rdiff-backup -r 2D --include '/tmp/restore/u/jdoe/Maildir/new/'
>   SB> --exclude '**' /u-backup/ /tmp/restore/
> 
> but with force, and then:
> 
> cp /tmp/restore/u/jdoe/Maildir/new/* /u/jdoe/Maildir/new/
> 
> again, etc.
> 
> BTW, your restore options seem strange, maybe just type:
> 
> rdiff-backup -r 2D /u-backup/u/jdoe/Maildir/new /tmp/restore
> 
> or something like that.
>