jennx
asked on
GRT Backup failing with '-546 The log file sector size does not match the sector size of the current volumn.' error
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
-Cliff
ASKER