Forgive me for not telling you this earlier, been a long day so I'm not
thinking straight... ----> I think they've stopped supporting vcb, I think they
may have because they've made vadp available, emc was actually supporting vcb
backups because they didn't have a version of networker out that supported
vadp. VADP is only available with networker version 7.6.2. We moved to 7.6.2
to take advantage of ddboost with data domain and I had to go to vadp with that
version. Honestly, if you're going to build a virtual environment for backup
you may want to go with 7.6.2.
>I have read it. It does not tell me what else I need to do to my
vCenter server so that the auto-discovery command of "https://vCenter/sdk";
works.
Right now, that URL returns "Page not found", so the auto-discovery is
failing. So I think something more needs to be on the vCenter, so it responds
to that command.
Unfortunately I'm not a "vcenter" guy, but honestly I don't remember
having to ask the person on our team who handles the esx servers to install
something on vcenter. I seem to recall even after I verified that I could hit
the vcenter link through IE that after I pointed back to the 32 bit vcenter
host it started working.
>My vCenter is a 64 bit box, too. And I don't have the old 32bit box anymore.
>So I guess I am out of luck?
I'm not sure, luckily I had still had my 32 bit box up and running and was able
to point to it.
> I keep hoping to go to 7.6.2, but based on my one experience upgrading
7.5.2 to 7.6.2, and the enabler code failing to work because (according to EMC
Licensing), my license bundle is "too old and needs to be upgraded", I can not
risk upgrading my main NW server. Believe me, I would love to go to 7.6.2, for
the VM features and Win2008 support, but no way will I even attempt it, if I
can't enable it after installing ...
I went from 7.5x to 7.6.0 and it put the enabler code in there for me. The
only time I had to enter a code was when I went from 7.4.x to 7.5.x
> Room meaning Disk space for the snapshots? How do I calculate that - enough
> disk space for the largest VM user of disk space?
Yes, depending on how many jobs you want to run (you can control that by client
parallelism). So say if you have 5 clients, each with a 25gb drive you would
need 5 x 25gb of space on your proxy server, that is if you want to run all of
them at the same time. Also keep in mind that you will also need 5 x 1.5gb
memory if you want to run them at the same time
>I don't see a VCB framework on the download page at VMware ...
VCB Documentation is here:
http://www.vmware.com/support/pubs/vcb_pubs.html
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Michael Leone
Sent: Thursday, June 23, 2011 3:14 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NW 7.5.2 and VMware vCenter 4.1
> 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.
I have read it. It does not tell me what else I need to do to my vCenter server
so that the auto-discovery command of "https://vCenter/sdk"; works.
Right now, that URL returns "Page not found", so the auto-discovery is failing.
So I think something more needs to be on the vCenter, so it responds to that
command.
> 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..
My vCenter is a 64 bit box, too. And I don't have the old 32bit box anymore. So
I guess I am out of luck?
> 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.
I keep hoping to go to 7.6.2, but based on my one experience upgrading
7.5.2 to 7.6.2, and the enabler code failing to work because (according to EMC
Licensing), my license bundle is "too old and needs to be upgraded", I can not
risk upgrading my main NW server. Believe me, I would love to go to 7.6.2, for
the VM features and Win2008 support, but no way will I even attempt it, if I
can't enable it after installing ...
> Your proxy server will need plenty of room, based on how many vm's you
> plan to backup.
Room meaning Disk space for the snapshots? How do I calculate that - enough
disk space for the largest VM user of disk space?
> 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.
I don't see a VCB framework on the download page at VMware ...
> 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.
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
|
