Solved

GRT Backup failing with  '-546 The log file sector size does not match the sector size of the current volumn.' error

Posted on 2011-03-08
3
2,181 Views
Last Modified: 2012-05-11
Hi,

My database backups have started to fail with Backup Exec 12.5 on SBS 2008.

The full error is  e00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information.

In the job log, it says: For additional information regarding this error refer to link V-79-57344-759
  V-79-57344-759 - Unable to complete the operation for the selected resource using the specified options.  The following error was returned when opening the Exchange Database file:  '-546 The log file sector size does not match the sector size of the current volumn. '

All the sectors in question (C Drive, D Drive, B2D Drive) are 4096K. I'm not sure what the problem is. The backup drive is a 3TB USB3 Drive from Western Digital. I'm wondering if it's flaky, but the error has been consistent over the past few days, and other backups are working.
0
Comment
Question by:jennx
  • 2
3 Comments
 
LVL 57

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 35074523
Pretty common with 3TB drives and Server 2008/Vista. Short answer is that drives above 2TB are using workarounds to present their space to the OS. MS added additional support to 2008 R2 and Win7, but that hotfix was not backported. I simply never recommend using 3TB drives.

A common thing you'll see is that the drive works at first (as the actual sectors being accessed are below the 2TB threshold) but as the snapshot/image gets larger, the merge process fails because the OS is now trying to access the high sectors and the compatibility issue arises. So even if your backups were working before with this drive, it doesn't necessarily indicate that the drive is fully compatible.

I'd try using a different drive temporarily and see if your problem is alleviated.

-Cliff
0
 

Author Comment

by:jennx
ID: 35084869
Interesting. What happens if I put two partitions on the 3TB drives?
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 35087923
Doesn't matter. It is a block-level issue and a compatibility problem with the OS and how some chipset drivers (including USB) try to present drives > 2TB.

-Cliff
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

776 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