GRT based backups of Exchange 2007 fail with: The following error was returned when opening the Exchange Database file: '-1213 The database page size does not match the engine.

Article:TECH68840

Created: 2009-01-17

Updated: 2013-03-06

Article URL http://www.symantec.com/docs/TECH68840

Article Type
Technical Solution

Product(s)

Show all

Languages

Show all

Problem

GRT based backups of Exchange 2007 fail with: The following error was returned when opening the Exchange Database file: '-1213 The database page size does not match the engine.

Error

-1213 The database page size does not match the engine

The same error message is seen while expanding the information store if the Exchange backup using the Granular Recovery Technology (GRT) on tape is duplicated to disk.

Solution

In most cases the -1213 error can be resolved by the Backup Exec (BE) hotfixes and service pack mentioned below:

Backup Exec 12.0 for Windows Servers Service Pack 4
Backup Exec 12.5 for Windows Servers Hotfix 324011 & 337202

However, there have been some cases where these hotfixes do not resolve the issue. In those scenarios please follow the steps below.

The backup to disk location is heavily fragmented. Defragging this volume should allow the backup to succeed. Check the File Fragmentation listing to see how fragmented the files are. This a more accurate percentage listing to use. If File Fragmentation is high, the issue can occur regardless of what version of BE is being used.
This issue may also occur if DFS is filtering out I/O's before Backup Exec can see them. Setting the following registry key on the media server may resolve the problem:

Warning: Incorrect use of the Windows Registry Editor can have disastrous results on a server Operating System. Great care should be taken when making changes to a Windows Registry. Registry modifications should only be carried-out by persons experienced in the use of the Registry Editor application.

HKLM\SYSTEM\CurrentControlSet\Services\Mup\DisableDFS as a REG_DWORD, set it to 1.

Once the key is created, reboot the system. All DFS shares will still work. However, the side effect is that presumably all the I/O is being directed through the DFS server on which the share is visible. Thus I/O travels across the network twice.

NOTE: This DFS cause has not been observed in Backup Exec for Windows Servers version 2010