We are having issues with timeouts after we moved our USR, SAP SQL Datafiles and SAP Transaction Logs from our old SAN to a new SAN.
Timeouts for SAPGUI users are set to 10 minutes.
We are running Windows Server 2003 with SQL Server 2005.
The SAP database has 8 datafiles with a total size of about 350GB.
___________________________________________
Procedure we used to move SAP to new SAN:
1. Attached 3 new SAN Volumes
-a. USR
-b. Data Files
-c. Transaction Logs
2. Shutdown SAP and SQL services
3. Alligned the new volumes with a 1024kb offset and gave the Data files and Transaction log volumes a 64kb allocation
size. (The alignment and 64kb allocation size were not setup for these volumes on the old SAN)
4. Copied the 3 volumes from old to new.
5. Changed the new volumes drive letter to the drive letters of the old volumes.
-a. I had to restart in order to change the USR volume.
-b. Because of this I had to resetup the sapmnt and saploc shares.
6. Started SQL services and then SAP services and everything came up just fine.
____________________________________________
The week before we had anywhere from 1 to 9 timeouts per day.
This week: Monday had 20 and Tuesday had 26.
On Monday we saw that MD07 was the only transaction that was timing out, but Tuesday had others as well.
The amount of users in the system is about the same. The amount of orders going in are about the same. No big transports went in right before we switched.
Performance counters that I know about for disk look a lot better on the Data Files.
- PAGEIOLATCH_SH ms/request is about 50% better
- Under I/O Performance in DBACOCKPIT:
- MS/OP is now anywhere from 5 to 30 - Old SAN: 50 to 300
- The Hit Ratio is over 99% - same as the old SAN
Looking at Wiley Introscope graphs:
- The "SAP Host: Average queue length" is about 30% to 40% lower then the old SAN.
- the "SAP Host: Disk utilization in %" is about the same.
Questions:
1. Did we do anything wrong or miss anything with our move procedure?
a. Do we have to do anything in SQL since we changed volumes even though we kept the drive letters the same?
2. What other logs or performance counters should I be looking at?
Thank you,
Neil