Networker

Re: [Networker] NW 7.5.2 and VMware vCenter 4.1

2011-06-23 15:42:17
Subject: Re: [Networker] NW 7.5.2 and VMware vCenter 4.1
From: Chester Martin <cmartin AT SPP DOT ORG>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 23 Jun 2011 14:41:29 -0500
Hello,
Page 525 of the 7.5 admin guide goes into how to setup autodiscovery, I don't 
think there's anything else that needs to be on it besides the networker 
client.  There also needs to be a networker client setup in the console for it.

One thing that I ran into is that your server that you point the enable 
autodiscovery (usually your vcenter server) to has to be a 32 bit server.  I 
found out the hard way that it's not supported on 64 bit.  In our case we had 
just migrated off a 32 bit vcenter to a 64 bit box so I was able to point it to 
the old 32 bit box and somehow it works..

Using 7.52 you will be using vcb, 7.6x has a lot more vmware enhancements (like 
1 step vm recover) with it so you may want to go that route.  If you decide to 
go to 7.6.2 you'll have to use vadp, unless you leave your vcb proxy at 7.6.1 
or below.

Your proxy server will need plenty of room, based on how many vm's you plan to 
backup.  Each vcb backup process (nsrvcb_save.exe, I think) on the proxy can 
use up to 1.5gb of ram, so make sure the vcb proxy has plenty of ram.  You also 
need the vcb framework (you get that from vmware) installed on your proxy.

With 7.6x you can also do one image level backup and do a file level restore 
(this is for windows only), but for linux we found we could restore the image 
to the proxy, use vm converter to convert, then mount it offline and grab 
individual files that way.


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Michael Leone
Sent: Thursday, June 23, 2011 2:14 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] NW 7.5.2 and VMware vCenter 4.1

I'm trying to get my NMC to recognize my vCenter server, so I can start to 
understand how better to use NW with Vmware. But I can't seem to get the 
virtualization auto-discovery to work. It keeps saying it fails to find my 
vCenter server. I'm guessing it's not finding it, since NMC seems to be using 
"https://vcenter/sdk"; as the command to locate my vCenter server, and that 
command is failing. I'm guessing I need to install the Vmware SDK on my vCenter 
server?

Are there any step-by-step instructions on this (both on how to configure your 
vCenter server so NMC will talk to it, and for NMC)? And other requirements - 
I'm guessing from hints I've seen that I need to define some sort of proxy that 
will actually take snapshots of my Vms, and then the backup is made from these 
snapshots? So does that mean the proxy needs access to free disk space of xxx 
size?

I'm very lost on this, as you might tell. :-) Right now, I back up each VM as 
if it was a physical client - I install the NW client onto the OS of the VM, 
and schedule backups accordingly. If there's a better way to go, I'm all for 
it. But I'm not finding any documentation that is turning on any lightbulbs for 
me ...

Thanks

--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel:  215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>

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