nwrecover or recover

[mouse123]

Hi All

I am not able to start either nwrecover or recover in unix. but I can run nwadmin and nwbackup without anyproblem

#nwrecover -s system(servername)
#recover -s system(servername)

What could be the wrong?

Thanks in Advance

 

[Serbtastic]

What error are you getting when you try to run them?

 

[mouse123]

Hi Serbtastic.

I following error message i am getting

recover: Cannot start session with server prodution1: Unable to receive

 

[Serbtastic]

Unable to receive is a networking error. Check that you have connectivity to your Networker server.

 

[605]

The problem could be caused by multiple issues:
- nwrecover cannot find the server
- nwrecover does connect to another NW server where this
client does not exist
- the index for this client is somehow corrupt
On NW 6.x run "nsrck -L6 client"

Make sure that the name resolution is unique and the correct
client file index is filled. Check /nsr/index and verify
whether the directories seen here match the client's name.

 

[mouse123]

I am runing in server itself and I am able to resolve the name also

prodution1:/oracle/stage_tmp/lsm/aix41#./nsrck -C
nsrck: checking index for production1.xyz.net
nsrck: compressing index for production1.xyz.net
nsrck: completed checking 1 client(s)

Even I restart the nsrexecd & nsrd (MW5.5lsmbuild51)

Stil the same problem

 

[bbills]

On the remote client try:

root[sh]@ucsd# cd /usr/bin/nsr
root[sh]@ucsd# ./recover -s uls
/usr/bin/nsr/ not in index
<return> will exit.
Enter directory to browse: /ucsd/home/temp
recover: Current working directory is /ucsd/home/temp/
recover> changetime 05/21/2003
time changed to Wed May 21 00:00:00 2003
recover> changetime 08:27:20
time changed to Wed May 21 08:27:20 2003
recover> ls
dfdf write_test xylo.html.old3
interoperability-index xylo.html xylo.html.old4
newtest xylo.html.old xylo.html.old5
permissionTest.txt xylo.html.old.old6
searchtest.html xylo.html.old2
recover> add xylo.html
1 file(s) marked for recovery
recover> recover
Recovering 1 file into its original location
Total estimated disk space needed for recover is 1 KB.
Volumes needed (all on-line):
uls-0003 at group
Requesting 1 file(s), this may take a while...
./xylo.html
Received 1 file(s) from NSR server `uls'
Recover completion time: Wed May 21 08:36:48 2003
recover> exit
root[sh]@ucsd#

The client has to be running the networker client daemon to begin with. For recover on the local server, just drop the -s [server name]. If this still doesn't work, you may have to change the device name of you tape drive, delete [with caution, can you afford to delete these volumes from the media db?], re-label, and inventory your volumes, and then do another full backup. Then try to do a recover.

 

[mouse123]

I tried renaming the tape drive also, I does not work.

what you mean drop? you want me to stop or remove the server name and rename the server name

one good thing is that my (oracle )rman backup is working good
Anyother tip please?

Thanks

 

[fscnwuser]

This could be a network problem:
take the full-qualified-Servername or ip-address for the '-s' option like that:

recover -s 'netwokerserver.xxx.yyy.domain.de'

or, on the client, look first what nslookup says about the servername/ip-address. then you can check with 'rpcinfo servername' wether you can reach the server over the net.

perhaps it could also be a firewall-problem.
cu

 

[mouse123]

Hi Fscnwuser

As I mention my previouse, I am ussing this nwrecover or recover in server only, I have taken some backup in server, which I want to recover (restore) in the same server ( in the server I am able to resolve my networker name). When I run ./nwcover -s networkerserver.xxx.yyy.domain

The following error message i am getting

nwrecover: Cannot start session with server networker.xxx.yyy.dominname: unable to receive

 

[Serbtastic]

Try pinging networkerserver.xxx.yyy.domain, does it resolve to the correct IP address on the Networker server?

 

[mouse123]

Serbtastic,

It does resolve to the IP address on the networker server.

 

[Serbtastic]

Ok, then run ps -ef |grep nsr and post the output.

 

[mouse123]

Here is the output


prodution1:/#ps -ef |grep nsr
root 42082 170390 0 May 26 - 0:00 ./nsrexecd
root 47210 1 0 May 26 - 0:08 ./nsrd
root 94628 47210 0 May 26 - 0:13 /oracle/ora81/stage_tmp/lsm/aix41/nsrmmdbd
root 97254 47210 0 May 26 - 0:00 /oracle/ora81/stage_tmp/lsm/aix41/nsrindexd
root 97550 47210 0 May 26 - 22:34 /oracle/ora81/stage_tmp/lsm/aix41/nsrmmd -n 1
root 170390 1 0 May 26 - 0:00 ./nsrexecd
root 182332 18434 1 09:53:36 pts/0 0:00 grep nsr

 

[mouse123]

Here is the output


prodution1:/#ps -ef |grep nsr
root 42082 170390 0 May 26 - 0:00 ./nsrexecd
root 47210 1 0 May 26 - 0:08 ./nsrd
root 94628 47210 0 May 26 - 0:13 /oracle/ora81/stage_tmp/lsm/aix41/nsrmmdbd
root 97254 47210 0 May 26 - 0:00 /oracle/ora81/stage_tmp/lsm/aix41/nsrindexd
root 97550 47210 0 May 26 - 22:34 /oracle/ora81/stage_tmp/lsm/aix41/nsrmmd -n 1
root 170390 1 0 May 26 - 0:00 ./nsrexecd
root 182332 18434 1 09:53:36 pts/0 0:00 grep nsr


I did stop and restart the above, it doesn't help me

thanks

 

[605]

This could also point to a problem with the client file index, especially if you have corrected the name or network
parameters.

Try the following:
- stop all daemons
- copy the nsr directory
- delete the /nsr/index/client_name
- start NW.
It will recreate an empty client file index database
- run nsrck -L7 client_name

Good luck.

 

[mouse123]

I did stoped all the daemons and copied all the /nsr directory to different place
and then I delete /nsr/index/production1
-start nw
I does created the client name
but when i run production1:/oracle/ora81/stage_tmp/lsm/aix41#./nsrck -L7 prodcution
usage: nsrck [ -qM ] [ -T tempdir ] [ -X [ -x percent ] | -C | -F | -m | -c ]
clientname ... ]

then
production1:/oracle/ora81/stage_tmp/lsm/aix41#./nsrck
nsrck: checking index for production1
nsrck: completed checking 1 client(s)

production1:/oracle/ora81/stage_tmp/lsm/aix41#./nwrecover
nwrecover:cannot start session with server production1: service not avaviable yet

Also I don't see any volume names in volume option if i run nwadmin and also indexes. how can i restore this

 

[605]

O.K.

The problem with nsrck points to older NW software (5.x)
which you obviously have. And i have not noticed it. As
you stated on 05/20:

&quot;Even I restart the nsrexecd & nsrd (MW5.5lsmbuild51)&quot;

This points to NW 5.5.1 which does not support level
checking of the file indexes yet (nsrck -L#).

In this case please vary the procedure as follows:
- run mminfo -av -r &quot;name=index&quot;
- stop all daemons
- copy the nsr directory
- delete the /nsr/index/client_name
- start NW.
It will recreate an empty client file index database
- run &quot;recover -S ssid#&quot;
Where ssid# is the number of the last full index backup.

Then try to recover.

 

[mouse123]

Hi 605,

I did tried the following

-run mminfo -av
-stop all the daemons
-copy the nsr directory different filesystem
-deleted the /nsr/index/client_name
-start NW

It does created an empty client file index database

then I tried

./recover -s production -S 2427

the following message

recover:cannot start session with server production1: unable to receive

Any other tips please

 

[605]

That points to a defective client file index that might have been backed up already.

What happens if you try to restore an older FULL of the
index backups ?