Solved

Hyper-V - Bytes Per Physical Sector

Posted on 2013-11-13
3
917 Views
Last Modified: 2014-11-12
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.

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

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

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

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,
0
Comment
Question by:SimonBrook
  • 2
3 Comments
 
LVL 17

Accepted Solution

by:
Mike T earned 500 total points
ID: 40007888
Hi,

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
0
 
LVL 1

Author Closing Comment

by:SimonBrook
ID: 40260762
Thanks for the help
0
 
LVL 17

Expert Comment

by:Mike T
ID: 40261014
You're welcome. Thanks for the points.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
VCenter migration issue 10 51
Recycle MSExchnge powershell app Pool 2 16
E-mail delayed during DNS server reboot 8 35
Lync 2010 4 19
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

785 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question