Question Locked

Backups of Exchange 2003 failing w/ Veritas Backup Exec 9.1

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am attempting to backup my EXCHANGE MAIL server (Windows 2003) using Backup Exec 9.1 over the network and the job is failing. I have gotten multiple failure types..."unable to attach to \\MAIL\Microsoft Exchange Mailboxes or Microsoft Exchange Public Folders" ..."error:a000848c- unable to attach to one of the drives"....and also "Logon Account "\\domain\Administrator" failed to access \\MAIL\Microsoft Exchange Mailboxes. Access is denied."
I am not sure if it's a rights/permissions issue, a password issue, or a configuration issue. Or all 3???? Also, what are the files/directories that I should be backing up on an Exchange Server??? The Microsoft Information Store\First Storage Group (which includes the Microsoft Mailbox Store and the Microsoft Public Folders Store)? Or the directories "Microsoft Exchange Mailboxes" and "Microsoft Exchange Public Folders" (which I can't get access to? Any help would be greatly appreciated.

15 replies

by normh3

Did you purchase the Exchange Agent for Backup Exec? If you did, did you create a user account with mailbox rights to run the backup?

by churdoo

BE 9 very finicky with Exchange Server.

What you select in your seletion list depends on how granular you want to be able to restore. In other words, if you back up the Storage Group / Mailbox STORE and Public Folder STORE, then you're able to restore the databases IN THEIR ENTIRETY only. This protects from a whole server crash or exchange database corruption, but does not protect against an individual mailbox becoming corrupted or a bonehead user deleting all of their email (or a terminated user deleting all of their email and contacts before they walk out).

By selecting "Microsoft Exchange Mailboxes" and "Microsoft Exchange Public Folders" you're able to backup and restore individual mailboxes and public folders, and dig down to individual items within the mailboxes or folders. Hope this clarifies things.

I think the best chance of success is to create a separate user account (not Administrator) to do at least the Exchange portion of the backups -- it's a good idea to use the separate account for the files portion of the backup as well. I think Administrator has some DENY permissions on the Stores that interfere with using it for Exchange backup. Follow this symantec article:
http://seer.entsupport.symantec.com/docs/249456.htm

by rgeils

I am new to AD and Exchange management, so please bear with me... There is a Backup Exec user id set up in AD. Does it need to be on the local box as a backup admin, as well as in AD? It is a member of the groups "All Exchange Accounts" and "Domain Users". Should it be in the "Backup Operators" group as well? Do you know what other groups?. Also, I deleted the previous network admin from the Domain Admin Group and all others so he could no longer gain access to the network, but afterwards, I went to the Mail Server and noticed that the Backup Exec Services were gone. Like it isn't installled any more. This is a new server that he built. Could his ID be tied to this in some way? I can no longer even see the Exchange Stores through Backup Exec. Confused....

by normh3

Besides checking to see if you have the Exchange Agent, have you checked to see if the Remote Agent is installed on the server in question? You also neeed to verify what account is being used to run the backups.

by churdoo

We don't know enough about your network to be able to tell you definitively, but I'll hit here what I can.

The BE Services would not disappear just by removing the old ID; something else must have happened, but without the Remote Agent service, you will not be able to see the infostores in the BE selection list. Does the agent show up in Add/Remote programs on the Exchange server? Re-install the remote agent if you have to, from your BE server, it's under Tools I think, near the bottom of the menu "install remote ..." or something like that. This may or may not require a reboot of the Exchange server so don't install the agent within production hours.

Is the Backup Exec user the one specified in the credentials section of the backup job? I think you said in your prior post that Administrator was being used. You want to be consistent with your use of the backup user account, from the credentials of the BE services on the server, to the Backup Operators Groups, Exchange Administrators, to the Credentials defined in BE in the Job.

Hope this gets you closer but post back more questions/info if necessary.

by rgeils

I checked the server and it is installed. Last night it stopped for some reason. What would cause this failure? How do I verify what account is being used to run the backups? What rights/groups should that ID be in?

by rgeils

Hi Churdoo, I have added the bexecacc user to the backup operators group and it is already a member of the "All Exchange Accounts" group and the "Domain Users" account. Does it need to be added locally to each Server as well? Or added to the Administrators Group (Or Domain Admin group...what's the difference?). All other servers use the "System Logon Account" as backup credentials. How do I know what (or who) is the System Logon Account? I think it would be better to use the bexecacc id to log in to ALL servers that are being backed up. Do you agree? Where do I have to put this ID to guarantee it will have access for all backups on all servers being backed up? Thanks-rich

by rgeils

I am still having authentication issues. I changed exeerything over to the bexecacc user id and I am still having authentification failures. the ID is only a member of the Administrators group and the Domain Administrator's group. Yet I still get "access denied" for this ID and also the Administrator ID when I try to access the Exchange Mailboxes and Exchange Public folders through Backup Exec. Any suggestions? Need help, because right now, no mailboxes are being backed up.

by rgeils

I don't know which of the following fixed my problem but I did the following:L
1. loaded Outlook 2003 on the backup server.
2. configured the bexecacc user to receive mail on the backup server.
3. created a local user id "bexecacc" on the Exchange Server and added him to the Administrators group.
4. added the local bexecacc id to the Security Tabs of the Mailboxes and Public Folder giving it Full Exchange Administrator rights.
4. In AD, gave the user Full Exchange Administrator rights.

So, I am now able to backup mailboxes. :)

Thanks!

by rgeils

yes, I created the mailbox from my pc and was able to open another user's mailbox using the bexecacc ID. I just installed Outlook on the Backup Server last night, hoping that it might change things, but nothing changed. All other servers that are being backed up are using a system logon account. Is the system logon account any id that is an administrator to the local box or a specific ID with specific rights?

by Member 19291532

I will go into more details tomorrow, but I'm trying all of the same things here, and I've verified all the steps in the Seer articles at Symantec, but I'm not getting anywhere. Backup Exec bites.

This discussion is closed to new replies.