EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
03/23/2010 01:58:37 PM:
> Correct !
>
> With vcb you can do either file or vm type backup, it's up to you to
> choose the correct granularity.
>
> Beside, remember that restore are always free with networker, you
> pay only for the backup. So you can install the client by default in
> your vm but NOT use it for backup so not requiring a license per vm
> but still being able to do a restore at file level in the vm without
vcb.
>
> There is really a choice to do that only you can do.
So ... if I get 10 Virtual Edition Client licenses for my 10 ESX servers,
I do *not* need the 85 NW client licenses that are currently installed in
the VMs on those 10 servers? And I'd still be able to recover a specific
file (or files) in one of the VMs, by browsing to it, as I can now? And I
would just have to backup all 10 ESX servers completely, rather than have
85 individual clients configured and listed as part of various backup
jobs?
Isn't VCB support ending very soon? How does that impact this scenario,
then?
>
> > Date: Tue, 23 Mar 2010 09:35:38 -0700
> > From: anuyamunan AT YAHOO DOT COM
> > Subject: Re: [Networker] client licenses for vmware virtual machines
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> >
> > Licensing for Virtual environments depend on how your backups are
> >
> >
> >
> > Licensing for Virtual environments depend on how your backups are
> configured.
> >
> > Guest Based Backups
> > - If you are performing guest based backups and have NetWorker
> client installed on each VM, then you can make use of the NetWorker
> Virual Edition Client license. This license is per ESX Server and
> allows unlimited number of VMs to be backed up. - If you have
> applications running in the VMs and have the corresponding
> application module installed on the VM, one module license per ESX
> server will allow multiple applications of the same type to be backed
up.
> > - This licensing policy is applicable to non-VMware environments
> like Hyper-V, IBM LPars, HP nPars etc.
> >
> > Proxy based backup (VCB)
> > - If you are performing VCB backups of your VMware environment,
> then a "regular" client license on the proxy is sufficient. This
> will allow you to perform recoveries to the individual VMs as well.
> >
> > Regards!
> >
> >
> >
> > ________________________________
> > From: MIchael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Sent: Tue, March 23, 2010 5:35:11 AM
> > Subject: Re: [Networker] client licenses for vmware virtual machines
> >
> > EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
> > 03/23/2010 08:01:26 AM:
> >
> > > Hi, the admin guide states the following which indicates that there
> > > is specific licenseing differences for VMs:
> > >
> > > The Virtual Edition Client Connection licence type is used to
> > > license virtual machines
> > > in the NetWorker environment. The Physical host identified in the
> > > Client resource
> > > consumes one Virtual Edition Client Connection license, regardless
of
> > how many
> > > virtual clients are running on that host. If
> > >
> > > So i am none the wiser as to what licenses i require.
> >
> > It works like this (I think):
> >
> > The license you quoted above is for 1 physical host (the actual VMware
> > box). The Virtual Edition Client Connection is the license for all
clients
> > on that particular host. However, my understanding is that if you get
this
> > license, you can't recover individual files in those VMs, but only the
> > entire VM. (since to VMware, each VM is really just a couple large
binary
> > files) I think of it as similar to doing a saveset recover, but
without
> > the option to specify only certain files, with each VM being similar
to an
> > entire saveset. When you recover, you get the entire saveset (entire
VM).
> > This is good for recovering in bulk, perhaps for D/R purposes.
> >
> > Me, I need to be able to recover individual files from each VM. So I
buy
> > the regular NW client licenses, and treat each VM as if it was a
separate
> > physical machine, and backup/recover (and license) the same as my
physical
> > machines.
> >
> > HTH (and I hope I am right about the licenses, and haven't confused
the
> > issue more)
> >
> > >
> > > Thanks, Mark
> > >
> > >
> > > --- On Tue, 23/3/10, denis.mail.list AT free DOT fr
<denis.mail.list AT free DOT fr>
> > wrote:
> > >
> > >
> > > From: denis.mail.list AT free DOT fr <denis.mail.list AT free DOT fr>
> > > Subject: Re: [Networker] client licenses for vmware virtual machines
> > > To: "EMC NetWorker discussion" <NETWORKER AT LISTSERV.TEMPLE DOT EDU>,
> > > "mark wragge" <mark_t_wragge AT YAHOO DOT IE>
> > > Date: Tuesday, 23 March, 2010, 11:12
> > >
> > >
> > > Hello,
> > >
> > > VM are physical machines, according to Networker.
> > >
> > > The client is running on every machine, not on the vmware.
> > >
> > > Denis
> > >
> > > ----- "mark wragge" <mark_t_wragge AT YAHOO DOT IE> a écrit :
> > >
> > > > Hi, do i need to license vmware VMs in the same way that i would
do
> > > > for physical machines? For example, if i have 3 Windows VMs should
i
> > > > have 3 networker client licenses.
> > > >
> > > > Additionally, if the windows VMs are configured as a Windows
Cluster
> > > > running SQL do i need to license for windows cluster client
connection
> > > > per node and 1 * SQL agent?
> > > >
> > > > Thanks for any help on this.
> > > >
> > > > Mark Wragge
> > > >
> > > > Send instant messages to your online friends
> > > > http://uk.messenger.yahoo.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
> > >
> > >
> > > Send instant messages to your online friends
> > http://uk.messenger.yahoo.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
>
> _________________________________________________________________
> Surfez en toute sécurité: téléchargez Internet Explorer 8
> http://www.microsoft.com/belux/fr/windows/internet-explorer/
> 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
|
