UNSOLVED
RPC error .. nsrndmsv / snapimage process hung
A planned tasks start the backup of a emc documentum system nsrndmsv command, which starts a snapimage backup - which makes nice snapshot and write his data to the storageserver. When finished it hungs with this message in the nsrndmsv log.
Creating TCP/IPv4 RPC client handle
Attempting to bind IPv4 socket descriptor 1280
Socket bound to OS determined port
Setting RPC socket send buffer size to 65536
Setting RPC socket recv buffer size to 65536
Bound TCP/IPv4 socket descriptor 1280 to port 111
RPC service 390107 (vers 5) not registered on 127.0.0.1
80722 4 %s%s 2 24 36 Failed to create RPC client handle: 11 26 355:Program not registered
I dont see it as an documentum plugin issue - as the nsrndmp_save process is still alive and seems to loose connection to his daughter process.
nsrnmdsv.exe -M ALL -f nmdsi.cfg -l full ## runs under local account which is Administrator (nsrexecd runs under same)
|-> "C:\Program Files\Legato\nsr\bin\nsrndmp_save.exe" -D 9 -M -T image -LL -s s-BACKUPSERVER -c S-DOCUMENTUMCS -g FAVPROD_NMD -b POOL -N DCB_DOCBASEID:SI_SA_filestore_01:+: -l full D: ## inherit account
|-> "C:\Program Files\Legato\nsr\bin\nsrndmp_2fh.exe" -x -S 1000183921 -w -D 9 ## inherhit account
Some of the common hints are to put all kind of aliases in the client ressource - but they are all there - except localhost itself. Where would i put a alias in the "local" db ?
Name resolution is fine - works in all directions.
rpcinfo command shows nothing special.
C:\Documents and Settings\a-grunert>rpcinfo -p s-***********
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 8228
390435 1 tcp 9456
390113 1 tcp 7937
program vers proto port
100000 2 tcp 7938
100000 2 udp 7938
390436 1 tcp 8228
390435 1 tcp 9456
390113 1 tcp 7937
Can someone give me a hint how i can solve this "loop" ?
Hi .. ok so i can checkup if a program is registered - but how do i register a program ?
C:\Documents and Settings\a-grunert>rpcinfo -t s-CSSERVER 390107 5
80722 4 %s%s 2 24 9 rpcinfo: 11 26 355:Program not registered
program 390107 version 5 is not available
Programs should register itself if it started. If it does not respond and it listed then it is stuck/broken which requires restart. Note that for nsrexecd you need to use 390113 1 in query. Also note that on RH6 rpc is changed (actually I believe same is later RH5 code too) so you may not see at all nsrexecd in rpcinfo, but I believe you do not run RH in your specific case.
Unfortunatly even a new install of Networker Client 8.0.2.4 + installing Snapimage 2.5 over it Shows the same error ... i start the planned Task as "System" now and still have the issue that the Snapimage Subprocess hungs while the upper process write such Messages into the Log :
Bound TCP/IPv4 socket descriptor 1156 to port 7938
RPC service 390107 (vers 5) not registered on 127.0.0.1
Creating TCP/IPv4 RPC client handle
Support was on this - they stated that they have no knowledge any more on the Plugin i use here.
The strange thing seems for me the ndmp_save command - when i start the SnapImage Job from the nmc i dont see a ndmp_save process on the Client during the save progress - i see it on the networker server *ugh*.
What shoul i put in the config file of the plugin to force the nsrndmp_save process to run on the backup server instead of the "Client" ...
I see this process .."C:\Program Files\EMC NetWorker\nsr\bin\nsrndmp_save.exe" -M -T image -P StorageNodeProxy -s BackupServer01 -c CONTENTSRV -g GROUP -LL -A "device interface=data domain" -A DIRECT_ACCESS=No -b POOLNAME -l full -q -W 78 -N "D:\\" "D:\\"
I think it is SI config that you should focus. Last time I worked with SI was 10 years ago - I don't remember much from that era. I know that since there were two refreshes of SI and I believe latest one was for Windows platform. According to compatibility guide all current 8 versions are supported so support must provide help. I personally can't say for sure how much SI 2.5 is compatible with NW8 since product was made I believe before NW8 so I wonder how much ndmp tape server would pick up all those new variables and switches that we find in recent releases. I would start by using latest NW7 client and forget about device interface setting and other exotics from NW8.
I'm not familiar with Documentum module, but if I understood correctly, you use SI due to Documentum? Or you don't use Documentum module and use SI instead?
Downgrading NW Client Version to a Version 7 (i tried NW 7.6.1) was a try ago .. i need documentum module to put the application Documentum in a "quicened" state which just means it starts some fancy java app which switch the system to mark incoming changes in some way it can find and delete them when it restores. The Documentum app has a config file where i can "state" the snapimage backup command.
If i could run a succesfull restore once i could "capture" the restore by procmon to script the hidden Voodoo.
Once i declared the Client to a Storage Node - but i am unsure if i cleared up the program directories after my last reinstall and it reinstalled all the stuff to the Legato Folder instead to the EMC ... so i assume some stuff remained somewhere and the Client didnt forgot to be a "Client only".
christopher_ime
6 Operator
•
1962 Posts
1476
0
Posted December 4th, 2013 02:00
Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.
You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "NetWorker Support Forum".
NetWorker Support Forum
Documentum Support Forum