rds.exe has 99% CPU during dbcheck ???

[rlee1]

NT4 SP6a, arcserve 2000 v7.0 build 1100 (sp4)

BU's started acting up, I was over due for running dbcheck. So I ran it as per instructions at

http://support.ca.com/techbases/as2000/as2k-1521.html

It was finding errors as I suspected. no problem.

But, part way thru dbcheck on astpsdat it appears like it is not doing anything and CPU is between 90 and 99% on rds.exe. (It's checking in astpsdat.002). I have never seen it "appear" to hang during a dbcheck and max out the CPU. Task manager says it's still running.

so, is it really running or is it hung up? It's been like this for 2 1/2 hours now. (at least end-users aren't complaining about slow server speed)

what's the downside risk for Ctrl-C on the dbcheck or end task on the rds.exe process?? blasting and loosing the db?

 

[rlee1]

it finally completed. now to see how long the keybuild takes

 

[databasebaba]

Move all the files in the temp folder of arcserve to a different location.

Then R*.* files in the database folder...

Then run the database utiliites ...

Dont run a anti virus during the database utilites since it takes more time.

DatabaseBaba

 

[fritz4000]

rds.exe stands for raima database service (ARCserve uses the raima database). The database utilities can take a long time, especially on the larger files in the database.

So you are aware: RDS.exe is a microsoft process and it may be on the same machine. I forget what the MS process is for.