Beware of Disk with 4-Kilobyte Sector Size!
Microsoft reference:
Hyper-V gothcha:
http://jeffreypersson.wordpress.com/2014/04/17/microsoft-exchange-server-2010-dag-on-vhdx/
"Continuous replication - block mode has been terminated. Error: the log file sector size does not match the current volume's sector size (-546)"
Turns out that the issue is that the VHDX files are the default settings of 4096 PhysicalSectorSize.
But it is not supported on Exchange DAG database volumes! 4KB sector disks are not supported on Exchange Server as a whole!
This also counts for Exchange 2013!
IBM SAN gotcha:
http://windowsitpro.com/blog/how-flawed-firmware-can-really-give-your-dag-some-replication-headaches
Microsoft reference:
Support requires that all copies of a database reside on the same physical disk type. For example, it is not a supported configuration to host one copy of a given database on a 512-byte sector disk and another copy of that same database on a 512e disk. Also be aware that 4-kilobyte (KB) sector disks are not supported for any version of Microsoft Exchange and 512e disks are not supported for any version of Exchange prior to Exchange Server 2010 SP1.
Hyper-V gothcha:
http://jeffreypersson.wordpress.com/2014/04/17/microsoft-exchange-server-2010-dag-on-vhdx/
"Continuous replication - block mode has been terminated. Error: the log file sector size does not match the current volume's sector size (-546)"
Turns out that the issue is that the VHDX files are the default settings of 4096 PhysicalSectorSize.
But it is not supported on Exchange DAG database volumes! 4KB sector disks are not supported on Exchange Server as a whole!
This also counts for Exchange 2013!
IBM SAN gotcha:
http://windowsitpro.com/blog/how-flawed-firmware-can-really-give-your-dag-some-replication-headaches
Comments
Post a Comment