As yet another side-note, Networker 7.5.1 does not work with VMware
"Auto-discovery" for virtual Client access licenses if you run a 64-bit
vsphere/vcenter 4.0 server.... I have an SR/case open, hopefully they
can supply me a 64-bit nsrvim.exe binary, but I'm not holding my breath
.... :\

Regards,
jamie
>> -----Original Message-----
>> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
>> Behalf Of Chester Martin
>> Sent: Tuesday, October 20, 2009 9:40 AM
>> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>> Subject: Re: [Networker] VCB & Networker
>> 
>> One more thing to add is that if you use vmware converter for the
>> "single step" recovery, networker doesn't support vmware converter
4.0,
>> you have to use 3.0.x
>> 
>> -----Original Message-----
>> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
>> Behalf Of jsiano
>> Sent: Monday, October 19, 2009 9:18 PM
>> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
>> Subject: [Networker] VCB & Networker
>> 
>> hello
>> i shared similar frustration with the original poster. I'm not an
expert
>> at Networker and really super newbie to VMWARE. I know hardly antying
>> about VMWARe.
>> 
>> But with help of VMWARe tech support and a little trial and error...I
>> got it working.
>> 
>> First...be sure to follow instruction only from EMC networker tech
>> support.  There are postings for VMWARe from VMWARe experts on
community
>> pages that will leave you astray.
>> 
>> 1) install the latest versions of the Networker/VMWARE integration
>> module!!
>> 2) you don't need all the *.bat save command stuff.
>> 3) place user=system,host=proxyserver into remote access
>> 4) make sure all DNS is rock solid on all ends. if you don't get this
>> right, you will get a good capture but will have error messages with
>> busted certificates. my case, I use a local /etc/host file on top of
DNS
>> cause of issues with NT AD and local unix NIS/DNS.
>> 5) make sure *FULL* is selected and not *Full* for your
>> saveset---assumeing you want the whole/all VMDKS.  this killed me for
>> two weeks...I was using *Full* and not CASE SENSATIVE *FULL*  ..go
>> figure.
>> 5) use the SSPI option in your config.js to avoid any nonsense with
>> passwrods in clear text, registry passwords, etc.  this is super
easy.
>> 6) proxy backup type data in client resource if fairly
easy...type/host
>> name of proxy.
>> 7) if you follow some of the white papers posted by VMWARe
>> experts....they don't know Networker and will guide into installing
>> entire NSR/GTSD "master" server some place.
>> 8) works with Networker 7.4.sp2 and VMWARE version 4.
>> 9) Networker suport will help.    I did install 7.5 sp1 on a
>> client...but lower version as noted works.
>> good luck.
>> 
>>
+----------------------------------------------------------------------
>> |This was sent by james.c.siano AT lmco DOT com via Backup Central.
>> |Forward SPAM to abuse AT backupcentral DOT com.
>>
+----------------------------------------------------------------------
>> 
>> To sign off this list, send email to listserv AT listserv.temple DOT edu and
>> type "signoff networker" in the body of the email. Please write to
>> networker-request AT listserv.temple DOT edu if you have any problems with
this
>> list. You can access the archives at
>> http://listserv.temple.edu/archives/networker.html or
>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>> 
>> To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff
>> networker" in the body of the email. Please write to networker-
>> request AT listserv.temple DOT edu if you have any problems with this list.
You can access
>> the archives at http://listserv.temple.edu/archives/networker.html or
>> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER