Exchange 2007. eseutil /cc. JET_errLogSectorSizeMismatch

Consider this scenario.

You’ve had to recover email from an older version of Exchange. You’ve created a new domain, installed Exchange with the same organisation name and added a new Exchange server where the Storage Group and Database retains the same name and structure.

You’ve successfully restore from tape. However the Database isn’t mounted and fails to mount.

You’ve try to replay the logs from the restore.env file and you get this error

eseutil /cc

Operation terminated with error -546 (JET_errLogSectorSizeMismatch, the log file sector size does not match the current volume’s sector size) after 0.78 seconds.

You get the same error when you try to reply the logs manually using eseutil /r

The cause? The sector size.

As discussed in this blog post, the sector size and physical disk types for databases in an Exchange 2010 Dag need to remain the same across all volumes. I highly recommend taking the time to read the article in it’s entirety. https://blogs.technet.microsoft.com/exchange/2013/04/24/exchange-2010-database-availability-groups-and-disk-sector-sizes/

First. I had a look at my disks by running this command

fsutil fsino ntfsin DriveLetter:

Take note of my example below and the ‘Bytes Per Physical Sector’

>fsutil fsinfo ntfsinfo c:

NTFS Volume Serial Number :       0x1e6848246847f953
Version :                         3.1
Number Sectors :                  0x00000000077ccfff
Total Clusters :                  0x0000000000ef99ff
Free Clusters  :                  0x00000000004ba961
Total Reserved :                  0x0000000000000040
Bytes Per Sector  :               512
Bytes Per Physical Sector :       4096
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0

>fsutil fsinfo ntfsinfo D:

NTFS Volume Serial Number :
Version :                         3.1
Number Sectors :                  0x00000000077fefff
Total Clusters :                  0x0000000000effdff
Free Clusters  :                  0x0000000000c99b89
Total Reserved :                  0x0000000000000000
Bytes Per Sector  :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0

>fsutil fsinfo ntfsinfo e:

NTFS Volume Serial Number :
Version :                         3.1
Number Sectors :                  0x000000007cffefff
Total Clusters :                  0x000000000f9ffdff
Free Clusters  :                  0x0000000002edb5ec
Total Reserved :                  0x0000000000000000
Bytes Per Sector  :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0

The backup product had restored the logs required for the database onto the C:\. As this failed the database was in a ‘dirty shutdown state’ and eseutil /cc or eseutil /r failed

The ‘Bytes Per Physical Sector’ for the C:\ differed from the disks that held the database and logs

The fix was relatively simple. I moved the logs required for restore to the D: and reran eseutil /cc

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s