Hi,

What about the storage node field in the client definition of client cyrus ? Did cyrus run backup to the backup server or to a storage node.

Secondly what about pool restrictions, should give you another error message but, version 6.1 was a while ago.

regards

Håkan

The storage node field just says "nsrserverhost" - from what little I know, that makes sense for the original setup. Since the original client isn't around anymore, there shouldn't be a problem restoring selected files to the local filesystem right?

How do I see about pool restrictions? I don't think there are any, but I'm not sure I'm looking in the right places. By the way, this server doesn't have X libraries so I'm doing it all command-line (nsradmin, etc...)

Hi,

It certanly looks like you didn't have any other storagenodes except for the backup server for that client, but if

nsradmin doesn't support visual mode.

nsradmin << EOF

print type:NSR pool

quit

EOF

Look for the devices attribute, but one other thing.

Did you set up remote access for root @ your restore machine on the source client?

regards

Håkan

All the devices lines are empty (apart from the semicolon). Does that mean "no restrictions for this pool" or "no devices are allowed for this pool"?

I'm just trying to restore the files on the local filesystem on the backup server as the original client node doesn't exist any more (all we have from back then are these old tapes), so I wouldn't think there'd be any permissions issues - am I right about that?

Thanks for the help - this has been a long journey...

Hi,

Are you able to resolv the client then?  Put "bogus" IP and orginal name inte hosts file of the backup server if it's not in DNS anymore.

Well permissions, you need to give the user on the backup server restore permissions to the data backed up from the orignal client, but I think

that should be ok as you are able to browse index of the client.

And the client is the same flavour as the backup server, UNIX to UNIX.

Do you get anything in the logs ? /nsr/logs/daemon.log ?

regards

Håkan

The host does have an IP (though everything at that domain  appears to be wildcarded for some reason)... I've tried putting it in hosts too and that doesn't get me anywhere.

Looking in that daemon log is useful though - I see the message: nsrmmdbd: WARNING: clients file missing from /usr/local/nsr/mm/mmvolume6 - seems like that could be a problem.

I did a few searches on cleaning up that situation, and it led me to trying "mminfo -mv" which shows me this very interesting bit of information:

   GS1-086                   23 MB 0.4%     undef    0 KB    14   5000 MB 15185         3 8mm 5GB
E  GS1-086                 9375 MB full   expired    0 KB     7   9500 MB 441         136 8mm

So it thinks there are two copies of the tape. This makes some sense because I tried a few things before I got the media indexes restored, some part of which could easily have made it think this tape was new somehow. The 0.4% is a little worrisome, but I've had the write protect tab on most of this time and don't think it's been written to. Is there a way to make it forget about that second version of the tape?

That did it.

Thanks so much for helping me out - I couldn't have done it without you.

It seems like I must have messed up something earlier, though I can see how I got two versions of the tape - the media indexes I recovered were actually older than the tapes themselves (or at least older than the files that were subsequently saved on them). I guess scanning first and then recovering the media indexes might be bad practice (or perhaps I messed up an option).

Again, thanks!