question

MacDaddy avatar image
MacDaddy asked

SQL Server Backup to Network Location Slow

I have a physical sql server 2008 server that's connected to our Oracle SAN. I have another VM server that is also connected to the same SAN on the same Domain. I have a backup process that backs up from the physical server to the VM server every night. The backup process used to take less than 1.5 hours. Recently we had a controller replaced on the SAN which required shutting down all servers that connected to the SAN. After the servers were rebooted the backup process now takes 15 hours! Both servers were shutdown and restarted properly and the SQL server has all SQL services running as before. Infrastructure is telling me nothing changed from a network standpoint. I have no control over the SAN or VMware, but I am convinced some service or setting has been changed with one of these areas. Can anyone offer some advice? Please do not suggest to backup locally and then copy the files to the backup server, as backing up to the backup server worked perfectly fine before. Something is different after rebooting the two servers. Any suggestions? Thanks ahead of time.
sql serverbackupsan
2 comments
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Is it possible that they made changes to the read/write settings of the controller?
1 Like 1 ·
Or did they change the multi-pathing which could introduce a bottleneck. Or did they move the backup disk down to a slower tier? Slower disks slower write times.
0 Likes 0 ·

1 Answer

· Write an Answer
MacDaddy avatar image
MacDaddy answered
The infrastructure group revealed the LUN these drives were on was over 90% full (it is noted that degradation can occur at 80%). They migrated the LUN to allow for more room and this took care of the problem. It's weird that the performance problem only surfaced after the SAN was taken offline and then brought back online. Yesterday I had also created a new share on the destination server and changed the backup process to use the new share, so maybe this is what actually fixed the performance issues???
1 comment
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Do your longer backups ever fail with a "The network name is no longer available" error?
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.