Exchange 5.5 Backup agent

[Systest01]

I am trying to configure the exchange 5.5 backup agent. I am getting this message.

" Failed to read exchange server name from registry"

Running Arcserve 2000
Windows 2000 server
Service pack 4

The Exchange Server is running on a different machine running
Windows 2000 Advanced server
SP4
Exchange 5.5
The Exchange backup agent configured without any error messages on the Exchange server.

Any help would be appreciated

jpeterson@systest.com

 

[mohamdr]

I undersand from the above that problem happening while trying to authenticate the exchange service.

I think you have installed arcserve exchange agent and you didn't apply sp4 on it.

try to apply the latest Service pack which is SP5 from support site and then try to re-authenticate again.

 

[fritz4000]

Where are you seeing the error? You stated that:
The Exchange backup agent configured without any error messages on the Exchange server.
That is the only place you would configure the exchange agent. If you are trying to configure the agent on a machine without exchange, when the agent goes to the registry to get information on exchange, it would make sense that the error you noted would appear.

 

[Systest01]

The error is happpening when I go into arcserve and attempt to select the Exchange Brick level, so that it can be backed up. the error message shows up right after I put in the exchange agent user name and password.

 

[brendaluv]

we had this problem a while ago...the only difference was that everything was running on the same box...solution : re-installed Arcserve + the Agent.

good luck.

 

[Systest01]

This Is a fresh new installation of both the agent and arcserve it self. Recently de-installed and then re-installed.

Any other Ideas that might work?

 

[brendaluv]

You can try the following, i spoke with one of our teck...and he suggested the following :

NT-AS6: Title: Database Corruption

Product: ARCserve 6.x for Windows NT
Version: 6.x

DESCRIPTION:

If you look in the Activity log, do you see an asterisk (*) next to the JobID number? If so, then this indicates that the ARCserve Database is not being written to. If this is the case, then there may be database corruption.

If you do not see an asterisk, then see if there are any *.CAT files in the ARCSERVE\TEMP directory. If there are then there seems to be a problem Merging the CAT file into the database. Go to a DOS prompt, and in the ARCserve directory, run MERGECAT.EXE. Look in the Activity log when it is done and let us know if you get any messages.

Fix Corruption:


Try stopping the ARCserve Engines and then delete the following files, found in the database directory.

The three files are:

rdm.chk - checkpoint image file
raaaaaaa.chg - Change log file
rdm.chi - Change log indicator file

These files are index files that will be recreated the next time ARCserve starts. Sometimes these files become corrupt and cause these types of problems.

If that does not fix the problem, then there may be database corruption. Follow these steps to try and fix the corruption:

Edit the Velocis.ini file, it is found in the ARCSERVE\DATABASE subdirectory.

Below is a portion of an average Velocis.ini, change the AsyncRead value as follows:

[SERVER]
ServerName=ARCSERVE
Archiving=1
AsyncRead=1 <--- Change the 1 to 0
AsyncTransactions=0
AsyncWrite=1
ChangeLogBufSize=262144
ChangeLogDevice=catdev
CheckPointDevice=catdev
CheckPointThreshold=40

What this is doing is changing the way Raima processes threads. Basically, the default way is to &quot;queue&quot; the threads to be processed at a later time. When this is done, this can cause a bottleneck and the symptom is Failed to Login to db ec=1034. When you change the AsyncRead to 0, you are telling Raima to process its jobs immediately so that there is no queue.

Sometimes the Database file RDS.EXE hangs up. This file should unload when you stop the ARCserve Database Engine. If it doesn‘t you can reboot the server or Use the NT3.51 resource Kit to Kill the RDS.exe.

With ARCserve 6 you can Check and repair corrupted database by executing the Dbmgr.exe in the ARCserve home directory. If a database is corrupt and will not repair you will be forced to Re-initialize the Database from the ARCserve Server Admin. Click on the Database Engine Tab then click on Operation and a menu option will drop down. You will see the Initialize database option.

 

[mohamdr]

brendaluv,
what you are saying is totaly not related to this problem at all.

 

[fritz4000]

It sounds as if ARCserve cannot read the registry on the remote machine (could be a permissions issue with the ARCserve system account). Make sure the system account is a member of Domain Admins (primary group), backup operators and Adminsistrators groups. Also assign the permissions Log on as a service, Act as part of the OS and Log on locally in the domain and each machine.

Good Luck.

 

[brendaluv]

like i said in the post...our techie mentionned that doing this might resolve. Sorry about the confusion.