Has this ever become a killer for anyone else?

I've got a server with many, many hard-linked files, and I just now, for
the first time, witnessed the way in which NBU handles hard links, which
appears to be 'if you want to restore a file which is a hard link, you
must also restore the file it was linked to as well.'  This is great
if you want to do a full filesystem restore, but rather frustrating
if you just want to restore a small subset of those files.

What makes the situation more frustrating is that NBU seems to have all
the information about which file to link to (it tries to link them
during the restore), it doesn't allow the option to either automatically
restore the original inode, nor to restore it with the new name.

Has anyone else run into this and/or made a work-around, or does anyone
have any suggestions as to how to do so.

My first idea is to:

1)  Select the files to restore, not knowing where the hard links
lead, and restore them.

2)  Capture the errors in regard to relinking files from the restore,
create another file list, and restore those files, possibly renaming
them to the files I wanted.

Anyone have any ideas?  Any help would be much appreciated.

Take care,

---------------------------------------------
Casey Feskens <cfeskens AT willamette DOT edu>
System Administrator/Network Svcs. Consultant
Willamette University, Salem, OR
---------------------------------------------