I finally find the solution in the release supplement (LGTOpa00800 for
release 6.1x or LGT44728 for release 7):

'When recovering a directory that has been renamed since the last full
backup (and only incremental backups have been run since then), you might
find that files you expect to find under the renamed directory are not
there. To recover those files, either perform a full backup before starting
the recovery, or do the following:

- Shutdown the Networker daemons on the server and client.

- Set the environment variable NSR_RENAME to Yes before starting the client.

- Set the environment variable NSR_NAMEONLY to No before starting the
server.

- Start the recover session'.

Setting the environment variables as stated above works fine.

> -----Message d'origine-----
> De:   EXT / CADENCE SIXA PRIGENT Yves
> [SMTP:ext.cadencesixa.prigent AT SNCF DOT FR]
> Date: lundi 6 octobre 2003 13:52
> À:  NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Objet:        [Networker] Incremental backups - How to restore the
> contents of renamed dire ctories ?
> 
> We had some issues for restoring the contents of a directory where a
> subdirectory was renamed between full and incremental backups (with
> Networker 6.1.3 - Solaris client and server).
> 
> Something like that:
>         /directory/subdir/file1
>         /directory/subdir/file2
> was saved with a full backup.
> 
> The subdirectory 'subdir' was renamed to 'subdir.new' so at this point we
> had:
>         /directory/subdir.new/file1
>         /directory/subdir.new/file2
> and it was saved via an incremental backup.
> 
> The /directory which was deleted and had to be restored.
> When we select the /directory (via nwrecover GUI or recover command line)
> and start the recovery process: only the directory 'catalog'
> (/directory/subdir.new) is restored but it remains empty: file1 and file 2
> are not restored.
> 
> The nsrinfo command shows that only the subdir.new catalog (not its
> contents) was saved by the incremental backup (not file1 and file2), so
> Networker seems to be clever at this point (file1 and file2 were not
> modified at that time, and were always there for sure).
> 
> Of course we managed to restore file1 and file2 in the former directory
> from
> the full backup by changing the browse time and then moving them back in
> the
> new directory.
> 
> The real case could be more complex than described above (multiples
> incremental backups and renamed directories) and it might be difficult to
> recover things in the right place, so I wonder if this is the standard
> behavior of Networker with incremental saves and/or if there is a way to
> restore the full files hierarchy (files and directory) in the state it was
> at the time of the last incremental backup in this kind of situation?
> 
> Yves Prigent.
> 
> --
> Note: To sign off this list, send a "signoff networker" command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=