E8604 error - Exchange Agent & Microsoft cluster

[markherring]

Has anyone out there actually got the Arcserve 2000 Exchange Agent working with Microsoft clusters? We have tried it and always get the E8604 message - insufficient privileges error. We have tried using the documentation on the CA web site but to no avail

much appreciated

 

[ARCserveGuru]

Active active? or active passive?

guru

 

[markherring]

It is actually active/active. Thank you for your quick response. Finally on Friday we got this working - it was a real pig to sort out and by CA's own admission the documentation is not great! If anyone is doing this then I can give some advice

 

[ARCserveGuru]

Heya, have you written in docco on it? If you have it would be nice to see. I have set this up before on an active/active exchange and from what I recollect it requires two exchange agents (in case of failover) both of which accessing the IS.

guru

 

[markherring]

Hi again

we have 2 models - one using a standard network backup to a remote backup server - this one just needs the Arcserve exchange agent on each node of the cluster and the enterprise edition on the backup server. The 2nd model is a SAN backup solution where you have a primary and secondary backup servers - this needs to have the full product - ie: AE, SANO, Tape Library Option and Exchange Agent on both nodes in the cluster plus the same again on our Primary SAN server (because CA did not recommend having a SAN primary on a cluster node).

We got it working by throwing away most of the CA documentation then installing Arcserve from the same account as the one we used to install Exchange. According to CA it is supposed to work if you give it rights on Exchange and setup local accounts on machines but it kept failing with E8604 messages.

The only relevant piece of info on the CA site is a relatively new document which details that you must setup the Arcserve account both in the domain plus on each local node - with the same password. Plus also assign "logon as a service", "logon locally" and "act as part of the operating system" rights to all of these domain and local accounts. You also need to assign the correct permissions to the arcserve$ account - ie: give the domain user and the local users explicit full control permissions to this share! Then you have a chance that it will work.

We are preparing documentation but I'll have to hack it around to make it a document that can go to the outside world. The important bits are in the paragraph above though

 

[ARCserveGuru]

Excellent, thanks for that. The only concern would be the express permissions being given to the arcserve$ share. If you give domain users and local users full control there is a bit of a security risk.

But why do these need full control? I am sure you could find a way around this by assigning specific rights to the local created user on each node.

anyway, happy its working....

guru