I just tried the same thing and had the same problem. Then I reran the nsrck
and didn't ctrl-c out....which I thought seemed wrong even if it was taking so
long. And the ctrl-c was what broke it because the nsrck index check process
wasn't allowed to run, which actually merges and continuity checks the index.
Here's my successful run:
------------------------------------------
# sudo nsrck -L7 -t 08/03/03 $server
nsrck: checking index for '$server'
nsrck: The file index for client '$server' will be recovered.
nsrck: Recovering index savesets of '$server' from 'MASTER'
Recover completion time: Tue Sep 23 11:24:56 2003 <--- Point at
which I ctrl-c out 1st run
nsrck: completed recovery of index for client '$server'
nsrck: /nsr/index/$server contains 1966002 records occupying 338 MB
------------------------------------------
I say, run it again and don't break out this time. Sooner or later the nsrck
recover will complete successfully. Then you will have no problems browsing
those dates.
--Ted
-----Original Message-----
From: George Sinclair [mailto:George.Sinclair AT noaa DOT gov]
Sent: Tuesday, September 23, 2003 10:59 AM
To: NETWORKER AT listmail.temple DOT edu
Subject: [Networker] Cannot browse client index -- need HELP!!!
Hi,
I'm trying to recover some data that is beyond the browse policy for an
old client. The client will no longer boot up, but its index is still
around, and it's still listed in the client list. As was recommended to
me, I used the nsrck command to merge in an older version of the index
so I could browse the data. I then run 'nwrecover -s myserver' from
client2 to access the old client's data and then I change the client
using the Update Client List button, but then I receive the following
error box:
Unable to find or browse backups from this client
After clicking 'ok' and closing out the window, I see the following
message at the Unix prompt:
nwrecover: lookup failed to server myserver
nwrecover: SYSTEM error: Bad file descriptor
I have listed root@client2 in the remote access field for the old
client. The data I'm trying to recover is a full from 01/26/03. This is
listed in the saveset recover window for the given client. The index I
recovered was a full from 01/27/03 as listed in the saveset recover
window. I ran the following command on the server to do this:
nsrck -L7 -t 01/27/03 old_client_name
It seemed to work, but it took it two attempts. I scripted it as
follows:
bash# nsrck -L7 -t 01/27/03 old_client
nsrck: checking index for 'old_client'
nsrck: The file index for client 'old_client' will be recovered.
nsrck: Recovering index savesets of 'old_client' from 'myserver'
Message from NSR server `myserver': retry for more
recover: Requesting remaining 2 file(s) from NSR server `myserver'
Message from NSR server `myserver': retry for more
Recover completion time: Tue Sep 23 11:19:50 2003
I should note that once it completed, the command just hung there, and I
never got a prompt. I was running this via the script command to capture
the output, but I would have expected it to still return a prompt.
Anyway, I waited for a few minutes and then pressed Ctrl-C. After all,
it did say the recover was completed. We're running 6.1.1 on Sun Solaris
8 on our primary server. I am able to browse other clients from client2,
so I'm wondering if the nsrck command goofed something up. It's not
supposed to, right? I was able to look at the old_client index via
nwrecover as recent as last week, but as I said, I was not able to
browse back as far as I wanted so I ran the nsrck command this morning
to merge in the old entries. I've not tried to view the index between
last week and today, so I can't swear that it was working just prior.
It's been several weeks since the old client died so it's not been
getting backed up since.
Any help would be appreciated.
Thanks.
George Sinclair
George.Sinclair AT noaa DOT gov
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
