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
|