Database Engine crashes during backup job

[Dito74]

I have a Windows 2000 server w/ SP4, MSSQL 2000 w/SP3 (with the backup database) and Arcserve with SP4 and all the recent fixes (applied trying to fix the problem). The drive is a Dell Powervault 122T Autoloader.
I run the full backup during the weekend and, I don't know when, the database engine crashes, the service, of course, it's stopped and when it's time to use a new tape, instead of choosing one of the rotation from the Media Pool, the job keep asking for a blank one.
I have no message whatsoever in the event viewer, no message into the Job Status Log that says that the engine was stopped.
When I go check, opening Arcserve Manager the DB Engine starts.
Don't know what to do, is there any other log I can look.
Tnx.

 

[davidmichel]

Not sure but here are a few thoughts that might help. Is the SQL Server that is used for the ARCserve Database on the same system? If not it might be a communication problem. Check the SQL error log. Turn debug on for the Database engine.

 

[Dito74]

SQL and Arcserve are on the same server and in the SQL error log I haven't found anything. Turning on debug on DB Engine now and waiting 'till next Friday, it usually happens after Friday at 7.00PM during the backup on the first tape (9 hours or so).

 

[davidmichel]

1) It would be better to enable the debug Friday before the backup. It can add a lot to the log.

2) So it works fine the whole week and just crashes Friday night, seems strange.

 

[Dito74]

I run the full backup between FRI and SUN.
MON thru FRI, I only run incrementals.

 

[Dito74]

Once again the DB Engine stopped. The full backup was running over the weekend and at midnight, DEBUG was on here's the message:

20031220 180010 *118 ** Summary for Job **
20031220 180010 *118 Prune Database Operation Successful.
20031220 180030 *118 Reschedule Prune Database Job for 12/21/03 at 6:00 PM.
20031220 210916 [ASDBAPI] Build: 1100.
20031220 210934 [SQL] SQL DBMS Version = 08.00
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-12/19/03,-25414,1)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-12/19/03,-25414,1,1400010,***_WLY)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-10/24/03,23441,2)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-10/24/03,23441,2,,)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-10/24/03,23441,3)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-10/24/03,23441,3,,)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-10/24/03,23441,4)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-10/24/03,23441,4,,)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(D-***-MON-11/24/03,-22928,1)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(D-***-MON-11/24/03,-22928,1,1300008,***_DLY)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(D-***-THU-10/30/03,-19536,1)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(D-***-THU-10/30/03,-19536,1,1300009,***_DLY)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-12/19/03,-25414,2)
20031220 210934 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-12/19/03,-25414,2,,***_WLY)
20031220 210939 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-12/19/03,-25414,2)
20031220 210939 [SQL] _ASDBCliGetTapeRecord(W-***-FRI-12/19/03,-25414,2,,***_WLY)
20031220 211248 N4212 [ASDBAPI] Logout from computer: ***
20031221 000017 DB Database Engine is Stopped.

I don't see what is causing this, the last activity comes at 21.12, the engine crashes at midnight. Does this help you?

 

[davidmichel]

The * before the job number indicates a database problem. So the problem started even before the db prune job. Check back in the log to see if you can find when the problem started.

 

[Dito74]

I had this problem since Job #1, September, but the engine never crashed and I had no idea the * means problem w/ DB.

The thing is that the server crashed those days and I re-build it from scratch, installing ArcServe again with SP and all the fixes. The DB was still saved on the D: partition and we re-used it.
Is there something I can run to fix the problem or find it? I never had this problem and now, I'm wondering if I should delete the whole DB and re-create a brnd new one.

 

[davidmichel]

That would probably be the best thing to do, and probably the quickest fix. Looks like you already put enough time into this.