Unanswered: Diagnostic to identify slow down due to SAN
We use db 8.2.6 on windows.
Our DB is based on SAN discs. We had a production DB response slow down yesterday and we spent good amount of time analysing our DB configuration and the SQLs. Ultimately it turned out to be an issue with SAN controller. But it took us great part of our time to convince SAN gurus that DB2 configurations are optimal.
Is it possible to have a some sort of diagnostic application that can be used to prove the slow down is due to factors out side DB2 ( in this case SAN)?
Any suggestions/advice in this regard will be much appreciated.
take a big file (your backup-image) and copy that form local disk to SAN and back. Write down the size of the file and the elapsed time.
Whenever you suspect the SAN again, start copy-ing your backup-image around and, when it look longer, confront the SAN-person with the elapsed times.