These days, some customers are deploying Exchange databases and log files on advanced format (4K) drives. Although these drives support a physical sector size of 4096, many vendors are emulating 5...
Updated Jul 01, 2019
Version 2.0
Blog Post
This is a great and timely article, as I have run into this issue with IBM ServerRAID (a.k.a. LSI MegaRAID) controllers - thank you, Tim! You are The Man for all things Exchange database!
I am curious though - instead of replaying logs for all DB copies, comparing headers, then suspending and resuming mailbox copies, wouldn't it be just as effective to simply delete and re-seed the database copies to the other DAG members? Sure, if the databases are large or across a WAN link it may not be optimal, but I would think this would also accomplish the same goal, right?
Also, what about Public folder databases? My initial thought is that they may not matter as much, since they don't replicate in the same manner as DAG databases, but they ARE .EDBs with the same structure and .log files, so it probably makes sense to do them as well, but I wanted to make sure.
Thanks again!