Backup Issue

[kodaksmile]

Hello,

I am receiving an error on only one of my databases when the Veritas Backup occurs it is as follows:

BackupMedium::ReportIoError: write failure on backup device 'LOCATION_ACTIVITY_DB_00__543f34cd_e04e_4d82_8877_72f2da3e618e_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

All of the other databases are backing up to tape fine but, this one is blowing up. Any ideas? It is only about 2 gig so it isn't really large.

Thanks

 

[JayKusch]

If you are using a backup device, I would try recreating the device and see if it shakes loose. Let us know what you find.

Thanks

J. Kusch

 

[kodaksmile]

No I am not using a backup device per say it is going through the backup exec sql agent.

 

[JayKusch]

Ahhh I see. Well, most but not all, DBAs usually try not to use backup utilities to pull backup sets straight from the database. Some of us use the native SQL Server backup commands to create the backup files to disc. We then run a utility, like Veritas, to spool our backup files from disc to tape.

The reason for this is just what you are running into. There can be all kinds of issues w/ connectivity, competing applications, open files .....

The other reason that you may want to backup to disc first and then to tape is that restores are far faster from disc than from tape. Of course this is all dependant as to weather you have enough spare disc space, or a reserve backup server, to create the backup files too.



Thanks

J. Kusch

 

[kodaksmile]

I would if I could -- this is the company wide protocol that I am trying to change....You know how that goes

 

[JayKusch]

Have you tried to drop and then recreate the job w/in Veritas?

Thanks

J. Kusch

 

[SQLBill]

You stated:

All of the other databases are backing up to tape fine but, this one is blowing up.

Which database is it? A system database or a user database? Do you have the Backup Exec Agent for SQL Server?

BTW-TEK-TIPS has a Veritas: Backup Exec forum also, it's FORUM481.


-SQLBill

 

[kodaksmile]

It is a user database and yes the backup exec agent for sql server is installed.

 

[SQLBill]

Where did this error appear? On the SQL Server server or the Backup Exec server?

Have you checked the Windows Event logs? The SQL Server Logs? The Backup Exec Error logs?

-SQLBill

 

[kodaksmile]

The error shows up in both the sql log and the event log (on the sql server) -- the backup exec log also shows an error.

 

[SQLBill]

Is the error the same in all three places? How about the job history in BE? (right click on the failed job and select job history).

-SQLBill

 

[kodaksmile]

The history in be says error reading file. the other 2 locations have the identical error message (sql and windows event log)

 

[SQLBill]

Can you post the full job history from BE? It sounds like the problem is with BE not being able to access the database. It could be that the Backup Exec account doesn't have permissions to the user's database.

-SQLBill

 

[kodaksmile]

======================================================================
Job server: JRCH-BACK1
Job name: .Tape Micros Daily
Job started: Monday, January 26, 2004 at 6:00:51 AM
Job type: Backup
Job Log: BEX05096.xml
======================================================================

Drive and media information from media mount:
Robotic Library Name: DELL Library
Drive Name: DELL TapeDrive 2
Slot: 1
Media Label: 000087
Media GUID: {F8461A6A-512B-4259-A2D8-F162054543D0}
Overwrite Protected Until: 2/9/2004 8:42:02 PM
Appendable Until: 12/31/9999 12:00:00 AM
Targeted Media Set Name: Bi-Weekly Tape Backup
======================================================================
Media operation - append.
Hardware compression enabled.
======================================================================
\\CASPOS1\D: Local Disk
Family Name: "Media created 1/25/2004 10:48:57 AM"
Backup of "\\CASPOS1\D: Local Disk"
Backup set #32 on storage media #1
Backup set description: "Micros Daily"
Backup Type: DIFFERENTIAL - Changed Files
Backup started on 1/26/2004 at 7:14:22 AM.
Network control connection is established between 172.16.0.151:4338 <--> 172.16.0.51:10000
Network data connection is established between 172.16.0.151:4349 <--> 172.16.0.51:3655
Backup completed on 1/26/2004 at 12:55:24 PM.
Backed up 2298 files in 1180 directories.
Processed 7,163,747,514 bytes in 5 hours, 41 minutes, and 2 seconds.
Throughput rate: 20.0 MB/min
----------------------------------------------------------------------
Network control connection is established between 172.16.0.151:4338 <--> 172.16.0.51:10000
Network data connection is established between 172.16.0.151:1200 <--> 172.16.0.51:4849
CASPOS1
Family Name: &quot;Media created 1/25/2004 10:48:57 AM&quot;
Backup of &quot;CASPOS1 &quot;
Backup set #33 on storage media #1
Backup set description: &quot;Micros Daily&quot;
Backup Type: DATABASE - Back Up Entire Database
Microsoft SQL Server Agent: Started
Backup started on 1/26/2004 at 12:55:25 PM.
The media operation was terminated by the user.
Error reading file data.
Error reading file data.

 

[SQLBill]

This line:

The media operation was terminated by the user.

shows me that you or another user stopped the backup job. And that makes sense with this error:

I/O operation has been aborted because of either a thread exit or an application request

Backup Exec was stopped, so that's an 'about because of an application request.'

-SQLBill

 

[kodaksmile]

May have been a timeout issue then because the job status shows as failed and on other jobs shows as cancelled when it has been cancelled by a user. This job normally only takes an hour at the most so the fact it ran for over 5 hours is odd in itself. Also when jobs are cancelled there are normally no entries in the sql log.

 

[JayKusch]

I see that you are appending to the tape, could the backup media have ran out of room????

Thanks

J. Kusch

 

[kodaksmile]

But, I have 5 other databases that back up successfully from that same server. No it doesn't appear to be running out of room on the tape.