Error when using ntbackup with Exchange 5.5

[jon246]

I am running Exchange 5.5 on a Windows 2000 server. I was able to backup the Exchange Information Store using ntbackup, but then unexpectedly the backups stopped and every time I try I get this error was in the Application Log:

Microsoft Exchange services returned 'Access is denied.' from a call to 'BackupPrepare()' additional data 'SERVER'

Any ideas?

 

[Americas911]

What is the event id and the source in the event log?

 

[jon246]

Source: NTBackup
Event ID: 8010

 

[Americas911]

I wish I had good news for you, but look at this.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;156715

Sorry, you may have to copy and paste that in your explorer.

 

[jon246]

Thanks for your link, but it lists a different error message and says it is a problem with remote backups. I forgot to mention earlier that I tried all the backups locally.

 

[fuego007]

Make sure the System account has full control permissions on all your Exchange directories, especially the ones containing your databases.

 

[jon246]

Thanks for the help. One of the other admins tried to do a remote backup when I wasn't looking. Although this isn't the specific problem that Microsoft describes with remote backups, it looks like it was similar.

We reset the server and now the backups work great again.

Just another Microsoft nuance: DO NOT USE NTBACKUP ON EXCHANGE REMOTELY.

Thanks again for all the help.

 

[SimonDavis]

NT backup as a rule won't work reliably on Exchange - a good part of the reason being that the message store is often locked (in use).

I'd seriously look at getting the right software to do this. You really need software that is designed for exchange.

In the meantime, I'd check to see if your messages really are getting backed up - if there's any doubt (which I have to say there is), don't wait for a disaster to verify your backups!

 

[fuego007]

The version of NTBackup that gets installed with Exchange does an excellent and reliable job of backing up the Exchange databases. If you attempt to use the plain-Jane version that is installed by NT from another computer to do this, you must stop the IS and DS and perform an Off-line backup. The NTBackup interface may not be as sexy, and you can't do brick-level backups with it, but it is as good as any other product for doing what it does. It's also not hard to schedule backups using the AT command or the Task Scheduler.

Bob

 

[jon246]

I agree with you SimonDavis. Without using a product like BackupExec, if an individual mailbox were corrupted, my only option would be to restore the entire information store to a temporary server. Also, NTBackup does not have a notify function to alert an administrator if a backup fails (at least not any way that I know of).

Thanks to all of you for your advice.

 

[patrickrouse]

Jon246, before you go off buying stuff you don't need you should get the correct information.

1. NTBackup backs up Exchange just fine, it's even written by Veritas, the smae people who make BackupExec

2. You need the NTBackup Program that's installed with Exchange, as the normal version isn't aware of the Information Store, so you wouldn't be able to do online backups.

3. The recommended process for restoring one mailbox is to restore the IS to a DR Server, export the mailbox with Exmerge or Outlook to a PST, then import back to the original Info Store.

4. Brick-level Backup = BAD. Don't believe me, just search the Internet for the words Brick-level & exchange and you should be easily convinced. Just because the option exists to backup individual mailboxes with the Backup Exec Exchange Agent, doesn't mean it's the best method.

The Exchange Agent for Backup Exec can cause your backup window to grow tremendously, as it backs up the mailboxes individually with total disregard for the Single Instance Storage driver that Exchange uses to keep a 1MB attachment in 100 mailboxes from taking up 100MB in your database. When you backup using the Brick-level (indiv. mailbox) option, you extract the contents of the mailbox from the IS.

This is BAD.

If you use Exchange 2000 or 2003 there's almost no need for these, as a deleted mailbox isn't purged for 30 days after it's deleted.

Turn on the DumpsterAlwaysOn key in the registry so you can restore items other than the inbox using Outlook, and you'll likely never need to restore a mailbox.