Search results for query: *

set the job engine log type to "debug" and see what happens in log.

does the machine specific disk contain the NIC driver? If yes but failed, I guess that driver does not work under mini-win2000 env. if you do want to recover this machine, I think you may have a trial of replacing the NIC and modifying the machine specific disk files.

stop tape engine and delete all r*.* files. restart the tape engine.

have u tried applying the latest patch on the client agent side?

run "authsetup /p" under BAB installed folder.

Failed to connect to merge/scan daemon solution: 1. uagent not started. start it. 2. QO48072

first, it's not an option for AS but a independent component. it doesn't have to install on the same machine with AS. actually, I won't suggest you install them on the same machine even they can. there're two components of SRM: Applications Server (AS) and Windows Client. you have to meet the...

cstop rename/delete brightstor.log cstart

better provide the whole command line and its output.

as what I'd always say regarding to this kind of problem: 1. check CA CDL; 2. update the SCSI adapter driver; 3. disable the tape drive and changer in OS device manager; 4. apply the latest CA service pack and device support patch.

I guess it's E6300 problem but not relate to multiplexing. I try restoring multiplexing media successfully.

KaJuHe, are u sure the tapetest did erase the tape in pre job? what I'm thinking is the device group is opened at the beginning of the job starts. tapetest can't operate on the media w/ "group already open" error. to confirm this, execute a batch file instead of tapetest: tapetest -z -m1 d2...

as I know, you can only set a start point for rotation job via formating media.

I have to say it's HW related if just review this log file. of coz CA support can't and won't locate the HW problem just like that HP/Compaq engine won't suggest you apply what CA patch even there's. I did experience replacing the tape drive for several time and at the end proved to be HW...

normal procedure: 1. check CA CDL; 2. update the SCSI adapter driver; 3. disable the tape drive and changer in OS device manager; 4. apply the latest CA service pack and device support patch.

you should replace the DBNAME with the db name want to repair. and the command is case-sensitive. here's the exact command line excuted on my machine: C:\Program Files\CA\BrightStor ARCserve Backup>dbcheck -a -L casdb;admin;secret ASJOB

GUI: Reports->Job Reports-> Preflight Check Report CLI: pfc [options] [filenames] Usage : pfc [-cahost <hostname>] [options] [filename(s)] Options -allchecks :- Perform all checks on all Ready jobs in the job queue, in non-interactive mode -syschecks :- Perform system checks...

set AS services startup type to manual,SNMP services as well; reboot server; copy msvcrt.dll from AS cd-rom to winnt/system32.

if no important info with ur AS 2000 db, I'd suggest u initialize it. to minimize the effect caused, just init the "astpsdat" which is the most likely corrupt. u can still "merge" the media info (session info, etc.) back to the fresh db at later time. if u do want to fix the db, here's the...

you'd better provide ur software version and patch level since there's known issue of similar symptom and certain patch addresses it.