troubleshooting Question

Exchange DAG fails because of sector size does not match

Avatar of mattemattsson
mattemattssonFlag for Sweden asked on
ExchangeWindows Server 2008Virtualization
3 Comments1 Solution5008 ViewsLast Modified:
Hi,

My dag on exchange 2010 sp3 fails because

"The log copier was unable to continue processing for database 'mb03-data01\TITAN-EX-A-MB03' because an error occured on the target server: Continuous replication - block mode has been terminated. Error: the log file sector size does not match the current volume's sector size (-546) [HResult: 0x80131500]. The copier will automatically retry after a short delay."

I got two servers running windows 2008 R2 on hyper-v 3.

The VHD files on the servers are dynamic .vhdx disks.

If i look with "fsutil fsinfo ntfsinfo" on the disks for the loggfiles i got different result, on the "sending" DAG member i got
Bytes Per Sector  :               512
Bytes Per Physical Sector :       <Not Supported>
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024

And on the reciving
Bytes Per Sector  :               512
Bytes Per Physical Sector :       4096
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024


Does anyone know what is causing this differance or a workaround for it?
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 3 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 3 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros