We help IT Professionals succeed at work.

Backup Exec 2010 - Very slow ESX backup

mvalpreda
mvalpreda asked
on
We are evaluating Symantec Backup Exec 2010 with the VMWare ESX agent. One of the things we are interested in is the direct backup of VMWare VMDK files. Problem is when we backup our 30 VMs this way, they are slow slow slow. Takes ~24 hours to backup just shy of 1TB.

The selection is all 30 VMs, and under the VMWare options we have SAN and NBD selected for the Transport Mode.

In talking with Symantec, they alluded to it can be faster. I'm just not sure how. This machine is NOT connected directly to the SAN. Is that someplace I should start? Add another NIC and connect that to my SAN switch? We are using software iSCSI.
Comment
Watch Question

Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
You should get about 1GB/minute.

Are you backing over a GB link?

What version of ESX are you using?

Author

Commented:
Some servers are on 4.0 and some on 4.0 update 1. Plan is on the next window to update everything to 4.0 update 1.

It is a GB link, but not directly to the SAN. Also, is the SAN being software iSCSI going to be an bottleneck? I have read that since everything goes over the control port, it can be slow. I just know it's a lot slower than I ever would have expected.
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
iscsi shouldn't make a difference. Is the media server virtual or physical?  Make sure you have IPV6 turned off if not using it.

Author

Commented:
Media server? Our SAN? If that is what you mean it's a Compellent SAN. Redundant connections to two separate Netgear managed gigabit switches. No jumbo frames....yet.
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
I was referring to backup exec media server.  What version of ESX.. 3 or 4? Is it a licensed ESX or ESXi (free)?

Author

Commented:
As previously stated it is Backup Exec 2010 and ESX 4.0/4.0 Update 1.
Roshan MohammedCloud Engineering Officer

Commented:
through whihc switch setup is your backup exec backing through! I suggest create a seperate vmkernal vswitch and configure it to use atleast 2x physical nics (if you have to buy them), and this will allow you to seperate your traffic!! can you imaginse backing up 1TB of data and sharing the traffic through concentrated networks

Author

Commented:
SAN connectivity is on it's own network. There are two NICs dedicated to it. One goes to switch A and one goes to switch B.
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
From the backup exec media server try copying a virtual machine using veeam fastscp to see how fast it copied, this will let you know whether it's a network issue or a backup exec issue.  Trying to baseline here

Author

Commented:
I will give that a shot this week.

Commented:
Any update?
Upgraded the switches and life seems to be a bit faster. Need to check and see what speeds we are getting.
I just got the vmware option for my backup exec 2010 and did my first two tests of backing up a vm from an esxi host:

iSCSI san on a 1GB Cisco switch
Backup Exec server connected to SAN switch
ESXi hosts connected to SAN Switch
SAN is HP lefthand 4500 SAS

Backud up a VM on one host at 1600Mbs/min

That is half the speed when I backup through network and VM OS
I am reading alot of posts but can't find if this is expected or too slow.
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
That is about expected unless you perform LAN free backups.  

What type of tape drive?
What type of SAN?

Tape is a Quantum LTO-4.  I can get up to 3.6GB for LAN based backups.

SAN is iSCSI connected through a 1GB Switch.

I ws expecying the vmware backup (2 large files) would be faster than an OS backup (many small files), but the opposite is true.  I have jumbo frames, tried with/without GRT.

Author

Commented:
Turned out to be a switch issue.

Author

Commented:
Stupid switch! LOL