SQL backup JOB crash every wednesday on a specific server

[mathieu_alain]

Hi everybody,

I have a customer runniong Backup exec 12.5 on a Windows 2003 server. The remote server is Running Windows 2003 X64 with SQL 2005 STD

It's been like 3-4 wednesday in a row that this problem occur. We restarted the SQL server itself and even the backup exec server and the problem is gone till the next wednesday.

I have another SQL server that is backed up correctly everyday so I think the agent works fine. Here are the SQL error we have on the faulty server.

I'll like the beremote agent log as well. To be honest I don't know whats up. I believe we made Backup exec update ( simply liveupdate to install fixes) before it happen but I can't garantee it.

Here is the backup exec error :

Job ended: Thursday, July 07, 2011 at 2:54:19 AM Completed status: Failed Final error: 0xe000035f - The SQL Server backup interface has reported a problem. Further details can be found in the job log. Restarting the SQL Server service or the server may correct the problem. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-863

I found several solutions on this forum and since we have a "patch" for now. I'll call Symantec only if needed. We are kinda short in time/tech since it's summer sooooo.

Regards,

Mathieu

-------

Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 7/6/2011
Time: 11:04:47 PM
User: N/A
Computer: KORV03
Description:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=6592. Thread=7920. Client. Instance=. VD=Global\KORV_00__3162032e_3738_4c74_8138_08a014e516ae__SQLVDIMemoryName_0.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------

Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 7/6/2011
Time: 11:06:51 PM
User: N/A
Computer: KORV03
Description:
SQLVDI: Loc=SVDS::Open. Desc=Open(Control). ErrorCode=(2)The system cannot find the file specified.
. Process=924. Thread=8060. Server. Instance=MSSQLSERVER. VD=Global\KORV_00__3162032e_3738_4c74_8138_08a014e516ae__SQLVDIMemoryName_0.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 3201
Date: 7/6/2011
Time: 11:06:51 PM
User: KORVETTE\servicebackup
Computer: KORV03
Description:
Cannot open backup device 'KORV_00__3162032e_3738_4c74_8138_08a014e516ae_'. Operating system error 0x80070002(The system cannot find the file specified.).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 81 0c 00 00 10 00 00 00 .......
0008: 07 00 00 00 4b 00 4f 00 ....K.O.
0010: 52 00 56 00 30 00 33 00 R.V.0.3.
0018: 00 00 05 00 00 00 4b 00 ......K.
0020: 4f 00 52 00 56 00 00 00 O.R.V...
------

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 3041
Date: 7/6/2011
Time: 11:06:51 PM
User: KORVETTE\servicebackup
Computer: KORV03
Description:
BACKUP failed to complete the command BACKUP DATABASE KORV. Check the backup application log for detailed messages.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: e1 0b 00 00 10 00 00 00 á.......
0008: 07 00 00 00 4b 00 4f 00 ....K.O.
0010: 52 00 56 00 30 00 33 00 R.V.0.3.
0018: 00 00 05 00 00 00 4b 00 ......K.
0020: 4f 00 52 00 56 00 00 00 O.R.V...

[CraigV]

...can you check and see if there are any AV scans/SQL maintenance jobs running on this server on a Wednesday to eliminate that?

[mathieu_alain]

Not a AV Scan but there is a SQL maintenance job that start prior to this error. I just don't get why its only on Wednesday because that SQL job run everyday.

I changed the ressource order to see if that makes a difference.

Thanks,

[pkh]

What kind of SQL maintenance are you doing?  Unless you cannot help it, it would be better not to do any maintenance job when you are doing a backup.  It would slow both jobs down.  I think you should stop the SQL maintenance job on Wed. to see whether the job goes through.

[mathieu_alain · Accepted solution]

We change the server order and it works. I didnt see any SQL job that is specific to wednesday but well...

Problem solved !