Discussion Locked

Backup Exec 7.3 Exchange Mailbox backup

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

We have the backup Exec Exchange Agent, and every night we back up the MS Exchange Directory, Information Store, and mailboxes. However the backup of the mailboxes began to fail at the beggining of this week, the message in the log is as follows: -
Unable to attach to \\SIA01\Microsoft Exchange Mailboxes.
Access is denied.

This started to happen I believe because I accidently (through ignorance) deleted what now turn out to be the Backup Exec Service account from the MS Exchange mailbox.

I tried to recreate this account, but to no avail. When I reboot the server and go into backup exec and create a job to backup all the mailboxes I can see all the mailboxes, and they all get ticked, but the job still fails. I have also had the following message: -

Unable to attach to \\SIA01\Microsoft Exchange Mailboxes.
The specified network name is no longer available.

Please can anyone help and talk me through this slowly (as I have no Exchang manuals, and little knowledge)

8 replies

by aaron_wurthmann

I have done something similar before in your exact same configuration. I can't remember what I had to so to fix it and I don't have my notes infront of me. Here is what I highly suggest, because for me back up are essential they are a high priority..
Call Vertas tech support, it may cost you $90 per incident and may 30 minutes of their time, it is worth it. Sure you could reinstall or check the passwords and accounts of all of the services you are running but tech support for Veritas is your best bet. Hope that helps

by mike.brooks

I did phone Veritas in the end, they were having all sorts of problems with their billing system (support was free), but also their phone systems kept cutting out after about 10 minutes of support time. However they pointed me to a web page that proved instrumental in solving the problem.

by calves

Try this.
You said that you created a new username, right?
Create a exchange account for this username, give the username, administrator and logon as service rights.
Go to services icon on control panel and double click on each bacexec service, and for the ones that requires a service logon and password, replace with your newly created usename and password preceeded by the domain name and a slash (domain\username)

Good luck!

by mike.brooks

As you know I did not create a new username, I'm sorry but the above answer did not help much - thanks anyway.

by leo.valmores

In addition to Answer 2, make the newly created account have these basic/advanced user's rights : 1.) Logon as Service 2) Act as part of the operating system 3)Back up files and Dirs 4) Restore files and Dirs.

Hope this helps

by terminator

Basically deleting the Backup Agent Service Account stops Backup Exec from communicating with Backup Agent, 3 sotutions,

1)If you have documentation just recreate the service account for Backup Agent with the same name as b4, make sure is administrator, logon locally, logon as a service, restart Backup Agent for Exchange service from control panel and that should do the trick
2)If you haven't got documentation, just recreate the account with any name with all the attributes mentioned b4 andgo to services, backup agent for exchange , properties and specify the new account under logon as, restart service
3)If that doesn't work(it should), reinstall backup agent for exchange again on the top of your current installation and install it again, but don't forget if you reinstall with a different name as b4 you might not be able to retrieve stuff from previous backup

Good luck

by mike.brooks

Most of the problem was in Exchange and having a unique mailbox name - then attaching this to the service acount then within exchange giving the service account the role of permissions admin over the Recipients. Then attaching the mailbox from within Backup Exec. I think you are close enough to get 50% for effort.

This discussion is closed to new replies.