Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1962
  • Last Modified:

The 'Microsoft Information Store' returned 'Instance not found error - Exchange Server 2003 - NTBACKUP

When I try to run NTBACKUP to backup Exchange 2003, I keep getting the below error message. I attached the error log. We have 2 tasks scheduled in Exchange Server 2003 to take both Normal (Full on weekly basis) and Incremental (Daily basis.) Those two tasks run normally until last week. After that both two tasks returned unsuccessfull error code.

We didn't made any changes to the server from past months. A long time (~6 months) back, we run the Exchange Store database deframentation.

I would appreciated if anyone can guide me on this. Thank you!
Backup Status
Operation: Backup
Active backup destination: File
Media name: "Exchange_Backup.bkf created 9/8/2010 at 8:48 AM"

Volume shadow copy creation: Attempt 1.
Backup of "EXCHANGE\Microsoft Information Store\First Storage Group"
Backup set #1 on media #1
Backup description: "Set created 9/8/2010 at 8:48 AM"
Media name: "Exchange_Backup.bkf created 9/8/2010 at 8:48 AM"

Backup Type: Normal

Backup started on 9/8/2010 at 8:48 AM.
Backup completed on 9/8/2010 at 10:44 AM.
Directories: 4
Files: 15
Bytes: 13,687,170,818
Time:  1 hour,  56 minutes, and  25 seconds
Backup of "EXCHANGE\Microsoft Information Store\Recovery Storage Group"
Backup set #2 on media #1
Backup description: "Set created 9/8/2010 at 8:48 AM"
Media name: "Exchange_Backup.bkf created 9/8/2010 at 8:48 AM"

Backup Type: Normal

Backup started on 9/8/2010 at 10:44 AM.
The 'Microsoft Information Store' returned 'Instance not found

' 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 9/8/2010 at 10:44 AM.
Directories: 0
Files: 0
Bytes: 0
Time:  1 second

----------------------

The operation did not successfully complete.

----------------------

Open in new window

0
SrinathS
Asked:
SrinathS
  • 4
  • 4
2 Solutions
 
golfwinsCommented:
Hello SinathS,

I think this is your problem. I hope this helps.

http://support.microsoft.com/kb/820272

Thanks!
0
 
SrinathSAuthor Commented:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Windows Server 2003 Service Pack 1.

We're running on Windows Server 2003 R2 Standard Edition. Also we performed several full backups earlier and didn't enountered this kind of situation.

I supect database defragmentation; Do you have any idea on Exchange database defragmentation? Thanks for your quick reply.
0
 
golfwinsCommented:
SrinathS

I think you need to delete the Recovery Storage Group. You shouldn't need to back this up. It was probably working fine, and then someone had the need to use the RSG and didn't delete it when done.
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
golfwinsCommented:
After doing a little more research, I'm fairly certain that the RSG is your problem. If you do not want to delete the RSG, then I found this link (Suggestion 1) that says it will remove the RSG from the NTBackup script. http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/f4bd73a656d2a518/424aa4d666f5c849?lnk=st&q=sbs+2003+backup+The+%27Microsoft+Information+Store%27+returned+%27Instance+not+found&rnum=4&hl=en#424aa4d666f5c849

I hope this helps!
0
 
SrinathSAuthor Commented:
The suggestion 1 seems to be simple, but we never encountered this kind of problem before. As I said earlier, we are able to take full backups normally until lastweek. I'll implement this tonight. I'll also try to restart the server.
0
 
golfwinsCommented:
Is it possible that one of your admins created the RSG to retrieve an old mailbox? Maybe someone was playing or tinkering around and created the RSG and just forgot to delete it. If you open Exchange System Manager and Browse to the RSG, you can right click the RSG and go to Properties. Then click the Details Tab and see when it was created. That may tell you if it coincides with the timing of your backup issue. Either way, i think deleting it, or excluding it will resolve your issue.
0
 
SrinathSAuthor Commented:
Finally I'm able to take full Exchange Server backup.
0
 
SrinathSAuthor Commented:
Deleting Recovery Storage Group (RSG) is a good solution for this. After I use the Microsoft Exchange Server 2003 Recovery Storage Group, do I need to delete its contents? YES.

Ref link: http://www.windowsitpro.com/article/tips/after-i-use-the-microsoft-exchange-server-2003-recovery-storage-group-do-i-need-to-delete-its-contents-.aspx
0
 
gorillyCommented:
I would just like to add to this that i had the same problem with an exchange server, i deleted the RSG and it didnt solve my problem, my problem was that due to low disk space both storage containers were not mounted, i needed to right click on them and select mount before the backup would take place. When they are not mounted they have a little red arrow on them. Hope this helps anyone in future.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

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