I'm not sure if SQL backups would be a good way to gauge performance, but this warrants some concern.
We recently finished a project where we stood up a new virtual environment. Our old system was ESX 4 with a Clariion SAN serving FC LUNs. The FC connections were rated at 4GBs.
The new system is ESXi 5 with a NetApp NAS serving NFS datastores (IP storage is 4x 1GiGe).
As we migrated all of our applications and utility servers, we noticed a performance increase with the response times. We left our file server and main SQL server for last.
Our SQL(2008 R2) backups were taking about an hour each night to run. This is SQL's native backup process. We expected this time to change once we moved the VM over to the new system. It hasn't. If anything, it increased by a few minutes. With the new hardware on the new hosts we expected to see some decrease in time.
Am I missing something here?
Old ESX Specs:
HP DL380 G7
X5650 2.67GHz CPUs
New ESX specs:
Cisco C260 M2
E7-2870 2.4GHz CPUs
Memory contention was never an issue here.
I've attached a screenshot.
Looking at this graph, the numbers look good until we hit our backup window (10PM). Would'nt this be normal given the amount of I/O that is involved during a SQL backup?
Is enabling jumbo frames going to make that much of a difference? Reason I am asking is this will require an outage on the network side all the way to the core.