hi leute,
hab das Problem mittlerweile gelöst:
Also als erstes müsst Ihr mal alle Arcserve Dienste auf "Deaktiviert" stellen und den server neu durchstarten!
Danach löscht ihr die Files, aus dem Systemverzeichnis von Arcserve:
rdm.chk - checkpoint image file
raaaaaaa.chg - Change log file (alle files die rbbbb, rcccc, rddddd usw. heissen)
rdm.chi - Change log indicator file
Danach die Dienste wieder auf automatisch starten und neu durchstarten, danach liefs bei mir wieder!
Wie das Problem auftaucht hab ich aber auch nicht herausgefunden, hab danach die Sicherungsabläufe zeitlich weiter auseinander geschoben und jetzt gibts keine Probleme mehr!
Hier noch der Text aus dem ich die Lösung kopiert habe:
Fix Corruption:
Try stopping the ARCserve Engines and then deletethe 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 recreatedthe next time ARCserve starts. Sometimes these files become corrupt and causethese types of problems.
If that does not fix the problem, then there maybe database corruption. Follow these steps to try and fix the corruption:
Edit the Velocis.ini file, it is found inthe ARCSERVE\DATABASE subdirectory.
Below is a portion of an average Velocis.ini, change the AsyncRead value asfollows:
[sERVER]
ServerName=ARCSERVE
Archiving=1
AsyncRead=1 <--- Change the 1 to 0
AsyncTransactions=0
AsyncWrite=1
ChangeLogBufSize=262144
ChangeLogDevice=catdev
CheckPointDevice=catdev
CheckPointThreshold=40
MaxCachePages=22400 [default is 5600]
MemoryLimit=134217728 [default is 33554432]
What this is doing is changing the way Raima processesthreads. Basically, the default way is to "queue" the threads to beprocessed at a later time. When this is done, this can cause a bottleneck andthe symptom is Failed to Login to db ec=1034. When you change the AsyncReadto 0, you are telling Raima to process its jobs immediately so that there isno queue. Sometimes the Database file RDS.EXE hangs up. This file should unloadwhen you stop the ARCserve Database Engine. If it doesn't you can reboot theserver or Use the NT3.51 resource Kit to Kill the RDS.exe.
With ARCserve 6 you can Check and repair corrupteddatabase by executing the Dbmgr.exe in the ARCserve home directory. If a databaseis corrupt and will not repair you will be forced to Re-initialize the Databasefrom the ARCserve Server Admin. Click on the Database Engine Tab then clickon Operation and a menu option will drop down. You will see the Initialize databaseoption.