• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2454
  • Last Modified:

NTBackup Gives Error When Backing Up Information Store

My NTBackup routine backs up to a hard drive on another server. Everything in the backup routine works fine, except the backup of the Microsoft Information Store. I have tried with both the Storage Group unmounted and with it mounted, and it does not work either way. I get one of two errors. Last time I ran it with the information store mounted I got this error:

Backup Type: Copy
Backup started on 10/17/2004 at 4:45 PM.
The 'Microsoft Information Store' returned 'Backup is already active.
' from a call to 'HrESEBackupSetup()' additional data '-'The 'Microsoft Information Store' returned 'Functions called in an invalid sequence.
' from a call to 'HrESEBackupClose()' additional data '-'
The operation was ended.
Backup completed on 10/17/2004 at 4:45 PM.
Directories: 0
Files: 0
Bytes: 0
Time:  1 second

That was actually the first time I have seen that error though. This is the error that I normally get when I run NTBackup, and the one that I got the last time I ran a backup routine with the stores unmounted:

Error: PENGUIN\Microsoft Information Store\First Storage Group is not a valid drive, or you do not have access.
0
Grime121
Asked:
Grime121
1 Solution
 
munichpostmanCommented:
You see these errors because NT Backup activates all Volume Shadow Copy service backup writers, including the backup writer used for Exchange Server 2003. By doing so, Exchange Server 2003 is in a "backup in progress" state even though Exchange Server 2003 is not selected as a component of the volume shadow copy backup. The Backup utility does not release Exchange Server 2003 from "backup in progress" state until the backup operation is completed.

The Backup utility does not use the Volume Shadow Copy service to back up the Exchange Server 2003 information store. The Backup utility uses the Exchange Server 2003 online backup streaming API to back up the Exchange Server 2003 information store. Because the Volume Shadow Copy service has already locked the Exchange Server 2003 information store for backup, the streaming API cannot bind to the databases hence the error message.

To resolve this issue backup the Operating system and Exchange in two separate jobs. So you can one for the system state and another for Exchange.

http://support.microsoft.com/kb/104169/EN-US/

http://support.microsoft.com/kb/327948/EN-US/
0
 
Grime121Author Commented:
Yep, that did it. I seperated the two backup jobs and disabled the Volume Shadow Copy on the Exchange backup routine. I don't know why I didn't think of that earlier.... Thanks a lot. :)
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now