Backup job failing with error a0008488 Access is denied.

I'm having a problem where when backing up WinSvr2k, Exchange 2k Standard SP3 with BE Version 9.0 Rev. 4454 I started getting a error a0008488 Access is denied, along with the errors listed below after our misconfigured AV Symantec 9 ran a full scan on the exchange server.

This wasn't caught until after a full tape rotation had occurred, so restoring the IS is not an option. On this specific backup job the verify option was turned off. Also I've been able to restore random emails that needed to be restored without any error's. I've been doing a bit of research, and have came across anything from creating a new IS to scrapping the server and starting all over (not an option). The items that are being backup are as follows: Exchsrvr folder, MS Exch Mailboxes, MS Exch Public Folders, System State, MS IS. When I uncheck the IS it backs up everything without any errors.

Being that we are using Exchagne Standard we don't have the option to create another IS on the server, so I was considering the option of copying the EDB, STM, and log files to a temporary Exch Server long enough to delete the current Storage Group and create a new one, and then copy the EDB, STM, and log files back over to the orginial server. Before I went through that trouble I wanted to see if anyone has ran into this issue before and if so how you resolved it.

Completed status: Failed
Final error code: a0008488 HEX
Final error description: Access is denied.

Final error category: Security Errors

Backup - \\Server\Microsoft Information Store\First Storage Group Access denied to database Mailbox Store (Server).
Access denied to database Public Folder Store (Server).
Access denied to database Log files.

Backup - \\Server\Microsoft Information Store\First Storage Group WARNING: "\\Server\Microsoft Information Store\First Storage Group\Mailbox Store (Server)" is a corrupt file.
This file cannot verify.
WARNING: "\\Server\Microsoft Information Store\First Storage Group\Public Folder Store (Server)" is a corrupt file.
This file cannot verify.
WARNING: "\\Server\Microsoft Information Store\First Storage Group\Log files" is a corrupt file.
This file cannot verify.
Who is Participating?
SembeeConnect With a Mentor Commented:
I have never done a brick level backup in all the years that I have been working with Exchange. Haven't felt the need.
With the deleted item settings that Exchange provides, I can recover most things easily. With Exchange 2003 they become even more redundant - as you can use the recovery storage group.

You may find that by resetting the backup job, and possibly using another account for the brick level backups, that the problem is resolved. The information from Veritas isn't very useful on fixing the problem. If you have support with Veritas you might want to take it up with them.

This is a KB article that refers to the problem of system state being done at the same time.

That has specific circumstances when the problem comes up. I basically separate the jobs as standard practise, as it avoids the issue coming up.

If you do a backup with ntbackup of just Exchange, what happens?

You do know that are duplicating what you backup?
If you are backing up the information store, then you don't need to backup the public folders or mailboxes separately - they contain the store.

It is also recommended that the system state is done separately. I often do a backup to disk of the system state with ntbackup and then pickup the file with Backup Exec.

big_grasshopperAuthor Commented:
Sorry I forgot to mention that, it backs up the IS without any errors
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.

If the IS is backing up correctly, then there are no problems with the Exchange server itself.
Public folder and mailbox backups are provided by the vendor of the backup software - Microsoft doesn't provide those natively.

I don't do backups of Exchange outside of the information store as I don't see the point.
Based on the error message, you need to check the permissions of the account being used to access those components to see if it still has the relevant permissions.

big_grasshopperAuthor Commented:
Yep, I knew that I was duplicating my data; I was doing it for the purpose of single email restores. Doing a brick level backup has made it easy on me when needing to restore a single email.

I have to admit that I wasn't aware of the recommendation on backing up the system state separately. I did a real quick search on this, and didn't find anything specific, can you lead me in the right direction for some documentation on this issue.

I would agree with you about it being a permissions issue if I didn't know for a fact that the permissions hadn't changed for the account that was preforming the backup. Here's a link I found on the Veritas site that is the error word for word,, which the first cause they list of this issue is due to Anti-virus software accessing the Information Store at the same time as the backup. Unfortunately I know that I had mis-configured the AV to scan, and did not have the exclusions that needed to be there in order to do the AV scan. Also when I open backup exec to look at the restore options it list the IS status as corrupt. But I don't get any error's with NTBackup, which I might consider using NTBackup in place of backup exce, but the process to restore a single email becomes a bit longer. Before I forget I want to say thank you.
big_grasshopperAuthor Commented:
Unfortunately it was a policy decision that was made because they didn't want to allow exchange to retain deleted emails, for any length of time. So it's a necessary evil to use the brick level backup with veritas.

Also unfortunately I've already tried setting up a different job, both with the existing account and with a new account, and I got the same results. I had to laugh when I read Veritas suggestion to upgrade to the most recent version as a possible solution. And we haven't had support for some time, and I don't forsee us upgrading our product.

What do you think about the idea of moving the mailboxes to a temporary exchange server and deleting and re-creating a new storage group on the existing server?
I haven't had to diagnose this problem before as I don't do brick level backups. Therefore I cannot comment on whether it will fix the problem.

Exchange has all of these data protection features built in, yet people set policies that fail to use them - which simply amazes me.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.