Backup Central

Hope this helps someone else who has run into the same issue.



After upgrading to vCenter on a 64 bit server, networker no longer can
use "auto-discovery" to find the vm clients. If you look in the
nsrtask.raw file after attempting an autodiscover you will see "Could
not run nsrvim: The system cannot find the file specified". If you look
on the vCenter server, sure enough nsrvim.exe does not exist in the
........\bin directory. This is because networker doesn't support a 64
bit version of the nsrvim.exe binary. I've seen several posts on the
net on others who have run into the same issue.



Emc support had me try something that allowed "auto-discovery" to work.
Since we still have our old infrastructure client server online (it's
not 64 bit). He had me point the "command host" in the "enable
auto-discovery" setup to the old infrastructure client, and leave the
"hostname" as the new vCenter server. Autodiscovery worked for us after
doing this.



Of course this is just a workaround, but it allows auto-discovery to
work until the 64 bit version supports nsrvim.exe.







via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

FYI...The 64 bit binary for nsrvim.exe doesn't exist. There is an
enhancement request open for it.



LGTsc30232/NW00099122



From: Chester Martin
Sent: Wednesday, November 18, 2009 2:12 PM
To: EMC NetWorker discussion
Subject: Networker and 64 Bit vCenter Server Woes



Hope this helps someone else who has run into the same issue.



After upgrading to vCenter on a 64 bit server, networker no longer can
use "auto-discovery" to find the vm clients. If you look in the
nsrtask.raw file after attempting an autodiscover you will see "Could
not run nsrvim: The system cannot find the file specified". If you look
on the vCenter server, sure enough nsrvim.exe does not exist in the
........\bin directory. This is because networker doesn't support a 64
bit version of the nsrvim.exe binary. I've seen several posts on the
net on others who have run into the same issue.



Emc support had me try something that allowed "auto-discovery" to work.
Since we still have our old infrastructure client server online (it's
not 64 bit). He had me point the "command host" in the "enable
auto-discovery" setup to the old infrastructure client, and leave the
"hostname" as the new vCenter server. Autodiscovery worked for us after
doing this.



Of course this is just a workaround, but it allows auto-discovery to
work until the 64 bit version supports nsrvim.exe.







via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

U dont have to use the old 32 bit client as command host.
any 32 bit networker client with nsrvim and dll's will work
you might get a cant decode result errors but the settings are saved, and you can x out after pressing ok and getting the error.

the discovery works fine