Two errors...

[jem2112]

Hopefully someone can help. I am running ARCServe 2000 V7.0 (Build 1086) SP3 and Exchange V5.5 SP4. I get the following error when I try to restore an Exchange Information Store. I am trying to restore the PRIV.EDB only and redirect it to another location.

E8605 Failed to start restore. (DBNAME=Information Store\D:\exchsrvr\MDBDATA.PRIV.EDB, EC=Backup Agent Error -- (323) "Cannot stop a MS Exchange Server Service".)

I also get the following error when I try to do a brick level backup. I looked at other posts on this one and nothing seemed to work for me.

E8602 Failed to read from database. (DBNAME=Individual Mailboxes\UserName\Calendar, EC=Backup Agent Error -- (68) "Error status in named pipe.".)

Any thoughts would be greatly appreciated.

Thx,

-Jim

 

[sujmer]

First you need to apply SP3 patch for AS2000 on the exchange
server to update the exchange agent.

Then in the restore manager destination tab you need to
uncheck the option "Restore Files To Original Location" &
then drill down to your exchange server the same way you backed it up.

For the backup error you need to download & apply the patch
"QO13760.CAZ" from the CA Web site..

Jim.

 

[jem2112]

No luck with the QO13760.caz patch. I also tried the "NEW" SP4 with no luck either. This is getting quite frustrating. I've also uninstalled and reinstalled the ARCServer 2000 software. Any other thoughts?

-Jim

 

[jem2112]

I disabled the Anti-Virus, did a test and the brick level backup worked. I set up scripts to disable and then re-enable the InoculatIT services before and after exchange is backed up. Will run with the full job this weekend to verify it all worked. I'm running eTrust InoculateIT, this is another CA product....argh!?!?!

 

[ARCserveGuru]

Listen,
Any antivirus would of made this occur, it's all about the time it takes to scan the individual files, and as such the agent times out with (error in named pipes) or whatever. Frustration is not warranted as NAV would have caused the same problem, Symantec, etc.... Also, you can reset the timeout period for the agent (which is modified in an exchange server registry key).

G