• Skip to primary navigation
  • Skip to main content
  • Skip to footer

JH Tech Services

A knowledgebase

  • Portfolio
  • Knowledgebase
  • About

Exchange and BackupExec “Database was not found, or could not be accessed.”

May 27, 2009 by jer0dh

First Storage Group  Database was not found or could not be accessed

Exchange 2003
Symantec Backup Exec 11D

Getting above error on Full backups sometimes.  On the full backups that get the error, cannot see individual mailboxes when I try to restore from them.

Copied mapi32.dll from exchange server to c:program filessymantecbackup exe folder as suggested by following link
http://www.symantec.com/connect/forums/grt-quotdatabase-was-not-found-or-could-not-be-accessedquot

Also, suggests running ISINTEG on the Exchange database…offline, though.  I’ll have to wait and see about this.

Found
that Symantec Endpoint did not have exceptions to not scan the Exchange folders.  Added this.

Time of backup is around 8:45am on Saturday morning.  Mailbox maintenance occurs around 3am to 7am.  Disabled Saturday morning and added an hour to maintenance for other days.

It appears to be backing up the exchange message store based on the size of the backup, but it’s probably just not granular.

Symantec also recommended this article http://support.microsoft.com/kb/304101 and applying Registry setting 1.  This had already been done.  PagedPooleMaximum was set to 60.  I changed this to 40 and restarted.
Antivirus was already set to NOT scan the disk locations this backup is set to backup to.
Will see what next backup does.
If it is an issue with the paged pool memory and a restart resolves it and since this is a dedicated backup server, a simple weekly restart script might also do the trick.
  • Knowledgebase
  • Uncategorized

Footer

  • Portfolio
  • Knowledgebase
  • About

© 2023