Hyper-V - Bytes Per Physical Sector

Hi,

We recently bought a new server, set it up as a Server 2012 Hypervisor and put it in a remote location. We set up a VM with Exchange 2010 and added it as a member of our Exchange 2010 database availability group. After a few days of copying the database; it has failed with the following error.

The log copier was unable to continue processing for database 'PG***MB01\PG***EX02' 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.

Select all Open in new window

After some research this would seem to happen if the "Bytes Per Physical Sector" is different on the two storage areas used by the Exchange Nodes within a DAG. EX01 is a physical server with it's own storage self-contained, EX02 sits on a Server 2012 hypervisor; which we'll call HV01

Original EX01 server

PS C:\Windows\system32> fsutil fsinfo ntfsinfo c:
NTFS Volume Serial Number :       0x5c0e7ad30e7aa5a4
NTFS Version   :                  3.1
LFS Version    :                  2.0
Number Sectors :                  0x000000007cf4ffff
Total Clusters :                  0x000000000f9e9fff
Free Clusters  :                  0x0000000007abbecc
Total Reserved :                  0x00000000000007f0
Bytes Per Sector  :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length :           0x000000000ba00000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000000000002
Mft Zone Start :                  0x00000000000cba00
Mft Zone End   :                  0x00000000000cc920
Resource Manager Identifier :     6352C42B-3E39-11E2-9E4F-967128CA17C9

Select all Open in new window

New Virtualised EX02 Server

[PS] C:\Windows\system32>fsutil fsinfo ntfsinfo c:
NTFS Volume Serial Number :       0x82940ba7940b9cb3
NTFS Version   :                  3.1
LFS Version    :                  2.0
Number Sectors :                  0x00000000bff4ffff
Total Clusters :                  0x0000000017fe9fff
Free Clusters  :                  0x00000000106452d7
Total Reserved :                  0x0000000000000780
Bytes Per Sector  :               512
Bytes Per Physical Sector :       4096
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length :           0x0000000009bc0000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000000000002
Mft Zone Start :                  0x00000000000c8b00
Mft Zone End   :                  0x00000000000cc820
Resource Manager Identifier :     2B4B4C07-3B73-11E3-83D9-85F8D66C1EC6

Select all Open in new window

Now you can see the different in "Bytes Per Physical Sector" is different on the two Exchange 2010 servers.

However just to add a twist, running the command on the Hypervisor itself (the one that hosts the VHDX of EX02) gives this.

2012 HyperVisor which holds EX02.

PS C:\Windows\system32> fsutil fsinfo ntfsinfo c:
NTFS Volume Serial Number :       0x16004e91004e77af
NTFS Version   :                  3.1
LFS Version    :                  2.0
Number Sectors :                  0x000000020ad36fff
Total Clusters :                  0x00000000415a6dff
Free Clusters  :                  0x000000002b652d6c
Total Reserved :                  0x0000000000000780
Bytes Per Sector  :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length :           0x000000000a200000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000000000002
Mft Zone Start :                  0x00000000000ca200
Mft Zone End   :                  0x00000000000cc820
Resource Manager Identifier :     2E992DD7-3B58-11E3-AE83-949ADAF9EF8D

Select all Open in new window

I'm confused. What does Hyper-V do to make the sector size change on the VHDX, which isn't present on the host operating system (HV01); thus stopping us from adding another member to our DAG?

Thanks Guys,