When duplicating a Microsoft Exchange Granular Restore Technology (GRT) image to tape "database system error (220)" is generated.
|Article:TECH222782|||||Created: 2014-07-08|||||Updated: 2014-07-08|||||Article URL http://www.symantec.com/docs/TECH222782|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Duplication of a Microsoft Exchange GRT image to tape generates a "database system error (220)". If the "Enable message-level cataloging when duplicating Exchange images that use Granular Recovery Technology" option is unchecked the duplication completes successfully.
From the Admin log on the Master Server:
11:04:22.342 [7656.4816] <16> build_catalog_for_virtual_browse_images: db_IMAGE() failed: database system error (220)
Windows 2008 R2 Standard
The ncflbc log from the Master/Media Server shows “ese.dll” fails to load. This library is needed to access the Exchange database data that is stored in the backup image. This Microsoft library was copied from the original Exchange server to the backup image. NetBackup loads ese.dll from the backup image.
The nblbc log for a successful bpduplicate shows ese.dll load successfully:
Here is an example of ese.dll failing to load:
13:05:19.630 [[fsys\jet] ] <from Producer> LoadLibraryEx failed for U:\backups\exchange2010\allusers\full\1369274436\_vv_NETBACKUP0\Microsoft Information Store\Mailbox Database 0885238300\ese.dll. 0x36b1, The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
This is due to a conflict between the C runtime (CRT) library on the system and the CRT library needed by the DLL.
Defining another server as the Exchange Proxy Host selection may resolve this issue.
The GRT cataloging information needs to access your Exchange Server during the process - it uses the nblbc process
If it cant get to your exchange server then you will need to allocate a GRT Proxy Host to use.
From the host properties of the client(s) > Exchange > Add a server to the Exchange Granular Proxy host selection.
This must be a Windows Server and can be a Media Server or even a NBU client but will need NFS configuring in the same way as the original Media Server backing it up had.
Article URL http://www.symantec.com/docs/TECH222782