> 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 absolutely agree with you, and I want nothing better than to go to
7.6.2. But until I am assured I won't have the problem I had last weekend,
where the upgraded NW server does not accept the enabler code, I can't
risk it.
I have just now heard back from our vendor, who tells me that my problem
with that server was that it was a Business Edition server, not a Network
Edition server, and so my license must be upgraded from Business Edition
to whatever equivalent that EMC is using these days. Once that happens, I
will get a new enabler code that should work.
Woulda been nice if we had heard anything about this issue before I went
to upgrade to 7.6.2, or if EMC had contacted the Business Edition
customers, telling them to upgrade their licenses else the latest
Networker versions wouldn't accept the enabler codes.
Anyway, hopefully that won't be an issue with my Network Edition license.
I doubt it will be, since others have the Network Edition, and they have
not had this problem.
Also, we have upgrades of various servers scheduled every weekend for the
next month or more, and we don't want to be upgrade Oses, SQL versions,
hardware *and* Networker versions, all at the same time.
>
> >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.
Perhaps it's the fact that it's 64 bit that is causing the problem. That,
and the fact that I haven't (yet) installed the NW client, due to being
short of licenses. :-)
> > 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
In my upgrade case last week, we went from Win2003 to Win2008, and
re-formatted the server to do so. So it was a clean install of NW 7.6.2,
then I copied over the /index, /mm and /res folders. That's when it
complained it wanted an enabler, and the enabler EMC licensing gave me
wouldn't work, complaining it was for a different platform.
> > 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
Uh huh. I have some VM clients with 300G hard drives, and 8G of RAM. And I
have about 100 VM clients in total. Even tho I don't backup all of them
every night, there's no way I can back up just one at a time, nor can I
make a proxy with multiple terabytes of disk space, and a couple dozen G
of RAM. :-)
So I guess VCB is out for me. Hopefully VADP is easier on resources, else
I will stay with my current method of backing up each VM as if it was a
physical client.
>
> >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
Thanks
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
|
