MMRNLA
asked on
SQL Backup times in new ESXi cluster
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jumbo Frames can make an improvement, but it could make it worse.
It's usually a recommended option when use NFS.
Enabling jumbo frames, needs to be be enabled, on the ESX server, network switch and NetApp filer. So it's not a quick change, and will require planning before implementation.
It's usually a recommended option when use NFS.
Enabling jumbo frames, needs to be be enabled, on the ESX server, network switch and NetApp filer. So it's not a quick change, and will require planning before implementation.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Robocat, when I attempt this command from a SSH session on the filer it comes back with "wafl not found". This is 8.0.2P4 7-Mode.
Any ideas?
Any ideas?
Try if it works in advanced mode
priv set advanced
wafl ...
priv set
Or you could try this command instead:
reallocate measure volname
priv set advanced
wafl ...
priv set
Or you could try this command instead:
reallocate measure volname
ASKER
Quick question Hanccocka, when you said
"Jumbo Frames can make an improvement, but it could make it worse."
How could this possibly make things worse? We are discussing this change inhouse now..
thanks
"Jumbo Frames can make an improvement, but it could make it worse."
How could this possibly make things worse? We are discussing this change inhouse now..
thanks
We have tried Jumbo Frames, on many installations, and although recommended, it really is a matter of test after enabling, and checking it performance is better or worse.
for some of our clients, performance was no better, and some worse.
It depends on your network infrastrcucture, switches, Im told that some switches do not have adequate buffers, although do support Jumbo Frames.
So, test, test,testband test again, and see if JF works for your site.
for some of our clients, performance was no better, and some worse.
It depends on your network infrastrcucture, switches, Im told that some switches do not have adequate buffers, although do support Jumbo Frames.
So, test, test,testband test again, and see if JF works for your site.
ASKER
thanks!
ASKER
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.
Thanks
SQL.jpg