Arcserve 2000 Backup Failure

[frdba]

I am trying to backup a SQL7 database with Arcserve 2000. This has been running successfully for several years, and just recently started bombing. I am able to backup files, and am able to merge and restore files from other servers. When the backup job executes it shows that it connects to the media, it will calculate the session for a couple of minutes then the job crashes and is placed on hold with no errors written to the arcserve activity log.

I found the following errors in the mssql7\errorlog.

Has anyone experienced this before?

2003-08-25 07:58:12.51 kernel BackupMedium::ReportIoError: write failure on backup device 'DBASQL70TID526VD0'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

2003-08-25 07:58:12.51 kernel BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'DBASQL70TID526VD0'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

 

[ACiDelic]

1. What errors do you see in the SQL agent log file (dbasql.log)?

2. If you don't see anything there, then you should turn on tracing. HKLM\SOFTWARE\ComputerAssociates\ARCserveIT\DSAgent\CurrentVersion\agent\dbasql70\Debug=3. This creates a file named dbasql.trc. You may be able to see the actual SQL Server error in the trace.

3. Did you change the password for the account you use to backup SQL Server?

4. What do you select in the GUI to backup SQL? The SQL agent?

 

[frdba]

1. dbasql70: 8/25/2003 11:16:59.750 Connect SQL70 Backup Agent.
dbasql70: 8/25/2003 11:17:0.62 Database UATFRP1 in Striping Backup Mode

I have yet to figure out what striping backup mode is....

2. I'll try this.

3. Passwords have not changed.

4. Yes, I am trying to backup through the SQL agent.

Thanks for you responses!

 

[Cyklops]

Something must have changed in your system, prior to these problems. Check out everything you can think of that might have caused this. Sometimes a single dll or other file change due to the installation of an application or update can be the cause.

regards