I have not seen any additional corruption since my initial post. My server specialist indicated there were warnings related to I/O latency that evening, but since then he has been monitoring things and here are his comments below.
However, I am still seeing warnings related to I/O latency on SQL02. The warning happens when the average I/O latency increases.
It is normally running in the range of 2ms write and 5ms read.
The spike is a consistent and predictable spike every night during our maintenance window starting at 12am.
The latency jumps to the 50-70ms for reads and 15-20ms for writes.
As soon as everything is done, it drops back to normal.
I'm not sure there's anything I can do about the maintenance jobs that are running (these are CheckDB, Backups, Index Rebuilds, etc). Since we are not experiencing any errors, should I be content or take some other action?
Thanks...