Exchange Backup Logon failure

[frdba]

We upgraded to Exchange 2003 and are using Brightstore Acrserve v9 build 2020.

when trying to backup the information store we get the following error:

E8601
Failed to connect agent. (AGENT=dbaexchis, EC=1385)
E8601
Failed to connect agent. (AGENT =\\EXCHSVR\dbaexchis, EC =Logon Failure: the user has not been granted the requested logon type at this computer.)


This is the first time I've ever installed the Exchange backup agent, so I'm assuming I'm missing something somewhere. Where does the dbaexchis come from? This isn't an id that we setup, and we can't seemd to find it on the server. We don't want to do brick level backups, so I didn't configure a mailbox account for that. Does that need to be setup whether or not we backup using that option? I am using an admin id to connect so it should have backup rights, and I verified that it can back up files on the exchange server. It's definitely an agent problem. I've looked and only found docs on Exchange 2000 - should these same instructions work for 2003?

Thanks for any help!

 

[speshalyst]

Hi,

IS Arcserve installed on the Exchange server ?

If you are backing thru the netowrk..
on the Backup manager. browse to your exchange server.
rightclick and put in the ARCserve system account..

expand the server..

rightclick on the Exchange DB Icon (golden platters) and put in the same credentials..

Start the Backup agent RPC server service on the Exchange server with the arcserve system account..


So it Shall be Written!
So it Shall be Done!!

 

[frdba]

All I have on the Exchange server is the Exchange agent. I didn't install the arcserve manager. Is that my problem?
I am backing up through the network, and it didn't like me using the backup servers' arcserve credentials.

Thank you for your help.

 

[speshalyst]

Hi,

Is this Exchanger server a DC ?

If not ...
On the backup manager.. browse to this server..
right-click .. security.. server_name\administrator..

essentially we are using the local admin of the exchange server. Does this expand the server ?

If it is a DC.. try using the Domain\administrator..

there should be some user account it like..

cheers


So it Shall be Written!
So it Shall be Done!!

 

[frdba]

The exchange server is not a dc. However, it is on a different domain than the backup server. I can connect to the exchange server and backup files, but not through the agent. I've tried all combinations of servername/admin, domain/admin. What worked backing up the files was domain\administrator.

I'm walking through the steps of creating a mailbox for dbagent, like the exch 2000 documentation says, but I think it is just used for brick level backups- which we don't want to do.

does the administrator account actually have to be listed as a member of the backup operator group, or is that just understood?

 

[speshalyst]

Hi,

Do these 2 domains have trusts enabled ?

can you domain admin of the backup server to the domain admins group of the Domain where Exchange is ?

Administrator should be a part of the backup operators.. but add it explicitly.. just in case

So it Shall be Written!
So it Shall be Done!!

 

[frdba]

Thank you for all your help yesterday!

I'm still trying to get our guy to give the ID domain admin rights. I would like to make sure I'm giving them to the right user.

From what I understand, since I'm not doing brick level backups, I do not need to configure a mailbox to use. So I need to figure out what credentials the exchange agent wants.

Does the ID that the backup server Arcserve Account runs with need to also exist on the exchange server? and is this the one that needs backup operator rights and domain admin rights?

I think along the way I may have confused myself and may be focusing on the wrong ID.

Thanks so much!

 

[speshalyst]

Hi,

You do not have to configure the Exchange agent..

However, the account you condigure as the ARCserve system account has to meet certain requisites..

Check the following link for the details...

http://supportconnect.ca.com/sc/kb/...&docid=266822&bypass=yes&fromscreen=kbresults

So it Shall be Written!
So it Shall be Done!!

 

[frdba]

Thank you for the link. That is exactly what I needed to show our ops guy. Well, I found out that there aren't any trusts between the two servers. So I'm getting the ops guy to open it up for me.

Thanks again and I'll let you know if it works.

 

[frdba]

Thanks for all your help speshalyst. Trusts between the servers will not be allowed, so I have placed a separate tape drive within the domain the exchange server is in.

Then I'll take it from there..