Video Screencast Help

HotAdd transport mode - Backup Exec 2010 R2

Created: 01 Sep 2010 | 9 comments
niko's picture

Hi -

What are the requirements for the HotAdd transport mode, using Backup Exec 2010 R2 to backup Vsphere 4 environment?

Must the Backup Exec 2010 R2 media server be installed directly on a VM to make HotAdd work?

Kind r

Bjørn.

Comments 9 CommentsJump to latest comment

CraigV's picture

Hi niko,

Pg. 1341 of the BE Admin GUide states you need to check your VMware documentation for more information.
Hotadd would simply be the means of how BE gets your VMs backed up...not really a BE-restricted feature, and the software leverages what is in VMware itself to do the backup.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

CraigV's picture

Actually, get hold of the BE 2010 R2 Admin Guide, and read the section on Symantec Backup Exec Agent for VMware Virtual Infrastructure...that will tell you what you need to do.
Hotadd basically allows you to use a VM as a proxy server...

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

sazz.'s picture

Are you using esx 4.1 then check this out:

http://support.veritas.com/docs/358281

If it is not esx 4.1 then there might be some other issue if it is not working and there is no need to install backup exec on VM to make hotadd work.

teiva-boy's picture

Currently as of this date, 4.1 is not supported.  It will be soon as there is a bug in the vStorage API from Vmware.  This applies to both Backup Exec and NetBackup.

Now, if I understand right, hot-add is mainly for virtualized backup servers, and for no other reason.  Correct?  

There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."

Ben L.'s picture

"Currently as of this date, 4.1 is not supported." Actually that is incorrect. 4.1 is supported by Backup Exec 2010 R2, please review the BE SCL for 2010 R2.

If this response answers your concern, please mark it as a "solution"

CraigV's picture

Hi,

 

Any news on this? Did it help at all?

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Ed_B's picture

Hi,

Any idea when R2 will support the Hot Add feature on VSphere 4.1? NBD peformance is painful to say the least

Cheers

Ed

teiva-boy's picture

Ed, why not look at improving the NBD performance by way of more bandwidth?  This is a vmware limitation at the moment, but I've never been able to figure out if you can team the console ports to get more bandwidth, but that would solve the issue given enough ports...

There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."

Colin Weaver's picture

I am slightly wondering about the point of Hot Add using the vSphere/vStorage API

With VCB - you could install the VCB proxy on a separate server from the Backup Exec Media server therefore the proxy could be inside a VM with the media server outside so that it can still address a physical library.

With vSphere/vStorage - you can't separate the vStorage API calls from the BackuP Exec Media Server so to run HotAdd you would have to out the meida server inside a VM and then have complications trying to access phycical tape libraries - just my 2p/2c