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.
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 : 0x5c0e7ad30e7aa5a4NTFS Version : 3.1LFS Version : 2.0Number Sectors : 0x000000007cf4ffffTotal Clusters : 0x000000000f9e9fffFree Clusters : 0x0000000007abbeccTotal Reserved : 0x00000000000007f0Bytes Per Sector : 512Bytes Per Physical Sector : 512Bytes Per Cluster : 4096Bytes Per FileRecord Segment : 1024Clusters Per FileRecord Segment : 0Mft Valid Data Length : 0x000000000ba00000Mft Start Lcn : 0x00000000000c0000Mft2 Start Lcn : 0x0000000000000002Mft Zone Start : 0x00000000000cba00Mft Zone End : 0x00000000000cc920Resource Manager Identifier : 6352C42B-3E39-11E2-9E4F-967128CA17C9
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?
I don't know if this question is still live/an issue, but I will answer anyway.
2012 added support for 4KB drives, which is the new sector size of modern disk drives. I am guessing that when you created the blank VHDX file, the format option defaulted to 4KB. It's just a choice. Different sector sizes suit different purposes. 64K sectors are good for SQL.
You need to create a new VHDX with 512 sectors and migrate to that. The sector size of your VMs *must* match the sector size of your host to avoid performance warnings.
Note the sector size of the host and of EX01 is fixed in hardware.
Administration of Active Directory does not have to be hard. Too often what should be a simple task is made more difficult than it needs to be.The solution? Hyena from SystemTools Software. With ease-of-use as well as powerful importing and bulk updating capabilities.
I don't know if this question is still live/an issue, but I will answer anyway.
2012 added support for 4KB drives, which is the new sector size of modern disk drives. I am guessing that when you created the blank VHDX file, the format option defaulted to 4KB. It's just a choice. Different sector sizes suit different purposes. 64K sectors are good for SQL.
A fix is mentioned here:
http://social.technet.microsoft.com/wiki/contents/articles/13075.hyper-v-avoid-using-virtual-hard-disks-with-a-sector-size-less-than-the-sector-size-of-the-physical-storage-that-stores-the-virtual-hard-disk-file.aspx
You need to create a new VHDX with 512 sectors and migrate to that. The sector size of your VMs *must* match the sector size of your host to avoid performance warnings.
Note the sector size of the host and of EX01 is fixed in hardware.
Mike