You can use the VCB option. It configures one server as NW storage node and then backs up all VM from this storage node. The VM's actually get backed up from the storage avoiding any network traffic and backup application load on each Virtual Machine.
Thanks for the reply Anuj, I am not sure if the VMWare VCB option will work with SUN M5000? but will explore your suggestion and discuss it further with my work mates and perhaps raise the question with support to get a resolve. Cheers GARY
unfortunately, you are not really stating which virtualization technology you would be using... Solaris Zones or VMWare?
Anyways, what is definitely the simplest solution - upgrade to NW 7.4.3. Due to the changes in licensing of virtual machines, it is now allowed to backup individual guest machines under "cap" of a physical host virtualization machine - and install NW client and backup from each guest...
...i like the future 7.5 "ESX"-esque display of the virtual environments very much!
Finally they got up to integration of EMC Software with VMWare, so deployment and configuration of NetWorker Clients for guests residing on ESX farms will be soo much simpler...hopefully!
and yes - new license model is "friendly" towards other virtualization platforms (Zones, LPAR, HyperV) , and "supports" even advanced features like VMotion...
As far as I see the new Networker virtual client edition license enables you to to define a physical server in the Networker client properties. All you have to do is buy one of these new licenses, check virtual client attribute and fill in the name of the physical host in the client properties. So in my opinion this should work with any kind of virtualization technology... I didn't find any infos about software compability / supported virtualization technology in powerlink despite it is mentioned in Networker 7.4.3 release notes.
I don't see that the Networker software is trying to detect the actually used virtualization technology. There is no license check at all, you can even write an imaginary name for the physical host. It is only necessary that the string is used identically on every virtual machine... I'm really interested if this behaviour will change in next servicepack
I asked my EMC sales guy regarding this feature. In Networker 7.5 there will be a check implemented which tests virtualization technology. I also asked which virtualization platform will be supported but have no answer yet. I'm interested in Sun Logical Domains and dynamic domains on Sparc-platform.
I believe auto-discovery will work only for vmware... eventually Sun's zones. Others will need to use 7.4.3-like approach by manually filling information.
I only think about this because you can cheat with VEC licenses at the moment. Have a look at this statement from EMC:
Ich kann nur soviel sagen dass der Kunde Recht hat. Die neuen Networker VEC (Virtual Edition Client) ueberpruefen (noch) nicht die VM Instanzen die gesichert werden. Das bedeutet aktuell kann der Networker nicht unterscheiden zwischen logischen und physikalische Servern. Einmal VEC eingespielt und man kann unbegrenzt Clients sichern auch physikalische, aber nur technisch - lizenzrechtlich liegt hier aber ein Verstoss vor. Es gibt folgendes zu beachten: ¿ Kunde ist trotzdem angehalten sich an das Lizenzrecht zu halten ¿ Dieses "Loch" wird vermutlich in Networker 7.5 gestopft werden, d.h. der Kunde koennte danach eine "Überraschung" erleben, wenn dann wirklich ueberprueft wird ¿ Der Kunde wird ziemlich sicher mit dem neuen Lizenzmodell attraktiver fahren, auch was Module anbelangt. Er benoetigt z.B. nur noch ein SQL Modul pro ESX Server - hier gibt es tatsaechlich eine groesse Einsparung fuer den Kunden.
amediratta
2 Intern
•
2K Posts
1
October 20th, 2008 22:00
stewartg1
22 Posts
0
October 21st, 2008 13:00
Cheers GARY
stewartg1
22 Posts
0
October 21st, 2008 22:00
But will VMWare VCB option will work with SUN M5000 VMs?
Cheers GARY
stewartg1
22 Posts
0
October 21st, 2008 22:00
YES - One Licence if its a VMWare platform.
Should have read as follows>>>>>
But will VMWare VCB option WORK with SUN M5000 VMs?
Cheers GARY
amediratta
2 Intern
•
2K Posts
0
October 21st, 2008 22:00
mofo
58 Posts
0
October 24th, 2008 02:00
unfortunately, you are not really stating which virtualization technology you would be using... Solaris Zones or VMWare?
Anyways, what is definitely the simplest solution - upgrade to NW 7.4.3. Due to the changes in licensing of virtual machines, it is now allowed to backup individual guest machines under "cap" of a physical host virtualization machine - and install NW client and backup from each guest...
rgds,
Mladen
ble1
4 Operator
•
14.4K Posts
0
October 24th, 2008 03:00
I'm not 100% clear if new license is friendly only towards VM or other virtual design available on market. Do you know?
mofo
58 Posts
0
October 24th, 2008 04:00
Finally they got up to integration of EMC Software with VMWare, so deployment and configuration of NetWorker Clients for guests residing on ESX farms will be soo much simpler...hopefully!
and yes - new license model is "friendly" towards other virtualization platforms (Zones, LPAR, HyperV) , and "supports" even advanced features like VMotion...
rgds
Mladen
otmanix
52 Posts
0
November 24th, 2008 13:00
I don't see that the Networker software is trying to detect the actually used virtualization technology. There is no license check at all, you can even write an imaginary name for the physical host. It is only necessary that the string is used identically on every virtual machine... I'm really interested if this behaviour will change in next servicepack
otmanix
52 Posts
0
November 25th, 2008 10:00
I also asked which virtualization platform will be supported but have no answer yet. I'm interested in Sun Logical Domains and dynamic domains on Sparc-platform.
ble1
4 Operator
•
14.4K Posts
0
November 26th, 2008 00:00
otmanix
52 Posts
0
November 26th, 2008 01:00
otmanix
52 Posts
0
November 26th, 2008 02:00
Ich kann nur soviel sagen dass der Kunde Recht hat. Die neuen Networker VEC (Virtual Edition Client) ueberpruefen (noch) nicht die VM Instanzen die gesichert werden.
Das bedeutet aktuell kann der Networker nicht unterscheiden zwischen logischen und physikalische Servern. Einmal VEC eingespielt und man kann unbegrenzt Clients sichern auch physikalische, aber nur technisch - lizenzrechtlich liegt hier aber ein Verstoss vor. Es gibt folgendes zu beachten:
¿ Kunde ist trotzdem angehalten sich an das Lizenzrecht zu halten
¿ Dieses "Loch" wird vermutlich in Networker 7.5 gestopft werden, d.h. der Kunde koennte danach eine "Überraschung" erleben, wenn dann wirklich ueberprueft wird
¿ Der Kunde wird ziemlich sicher mit dem neuen Lizenzmodell attraktiver fahren, auch was Module anbelangt. Er benoetigt z.B. nur noch ein SQL Modul pro ESX Server - hier gibt es tatsaechlich eine groesse Einsparung fuer den Kunden.
Message was edited by:
Otmar Meier
ble1
4 Operator
•
14.4K Posts
0
November 26th, 2008 02:00
Hari5
443 Posts
0
November 26th, 2008 03:00