|Article:TECH127089|||||Created: 2010-01-08|||||Updated: 2014-11-20|||||
Article URL http://www.symantec.com/docs/TECH127089
NetBackup for VMware Compatibility
The following topics describe NetBackup for VMware support. NetBackup for
VMware protects VMware virtual machines by integrating with VMware vStorage
APIs for Data Protection.
Note the following about VMware updates:
■ VMware updates to vSphere 4 and 5 are supported, unless otherwise noted.
■ vCloud Director 5.1.x and 5.5.x updates are supported, unless otherwise noted.
22.214.171.124 ,126.96.36.199 SUPPORTS
vSphere 5.0, 5.1, 5.5, and all 5.1, 5.5
of their update releases.
For more information on
VMware's VDDK support,
see the VMware VDDK 5.5.1
In VDDK 5.5.1 release nores (used by NetBackup 7.6):
The VMware policy concerning backward and forward compatibility is for VDDK to support N-2 and N+1 releases. In other words, VDDK 5.5 and all of its update releases support vSphere 5.0, 5.1, and 6.0 (except new features).
And in VDDK 5.0 (used by NetBackup 7.5):
VDDK 5.0 adds support for ESXi 5.0 and vCenter Server 5.0, and now works with the following VMware platform products:
So, can I use a NetBackup 7.6 as master / media and a separate backup host in NetBackup 7.5 to backup an ESX 4.1 ?
Hi Gdd, ESX 4.1 is supported under netbackup 188.8.131.52.( Am currently running this in my environment). But not in 184.108.40.206 and up. One other option we are leveraging per symantec directory is to set up a dedicated media server running supported netbackup version ( in this case 220.127.116.11 Vs ESX/ESXi 4.1). This way, you will be able to protect ESX 4.1 even if your master server is running 18.104.22.168 and up.
Hi Dolly, Gdd, inn_kam,
Thanks for the discussion inputs!
I am facing the same issue having NBU 22.214.171.124 Master and a large ESX/ESXi 4.1 farm. From what I am reading if I back the VMware with NBU 126.96.36.199 Media Servers it should work.
Any problems with the support of the config?
v188.8.131.52 is starting to get a bit long in the tooth, and is 5 or 6 patch revisions behind now...
...so I would also consider reviewing the contents of the latest revision of the v7.6 EEB guide, here:
...to check for any issues related to VMware backups discovered since v184.108.40.206 was released, to see if any of this issues represent a real problem for you or not. HTH.
I just completed upgrading of my Production master server VMware domain to 220.127.116.11 and provisioned a separate dedicated media server running 18.104.22.168 to cater for my ESX4.1. Everything is running good . backup/restore are all running fine.