cancel
Showing results for 
Search instead for 
Did you mean: 

Backup error SQL - Help me

Former Member
0 Kudos

I error with the backup of SQL, whenever agendo the backup in the DB13, he returns with the error below:

                      • Task history information ***********

For run: 20071223 20:00:00

Status: 0 (failure) (see DB error log)

Message: 3013

Severity: 16

Duration: 1 hour, 48 minutes, 3 seconds

Last msg: Executed as user: ANTILHAS\Administrator. ...DBCC

printed error messages, contact your system admini

strator. [SQLSTATE 01000] (Message 2528) Processe

d 3468800 pages for database 'PRD', file 'PRDDATA1

' on file 1. [SQLSTATE 01000] (Message 4035) Proc

essed 3287880 pages for database 'PRD', file 'PRDD

ATA2' on file 1. [SQLSTATE 01000] (Message 4035)

Processed 3337560 pages for database 'PRD', file '

PRDDATA3' on file 1. [SQLSTATE 01000] (Message 403

5) Processed 3392000 pages for database 'PRD', fi

le 'PRDDATA4' on file 1. [SQLSTATE 01000] (Message

4035) Processed 1879 pages for database 'PRD', f

ile 'PRDLOG1' on file 1. [SQLSTATE 01000] (Message

4035) BACKUP DATABASE successfully processed 134

88119 pages in 6395.229 seconds (17.277 MB/sec). [

SQLSTATE 01000] (Message 3014) Cannot open backup

device 'prd_full'. Device error or device off-lin

e. See the SQL Server error log for more details.

[SQLSTATE 42000] (Error 3201) VERIFY DATABASE is

terminating abnormally. [SQLSTATE 42000] (Error 30

13). The step failed.

Here is the Log SQL:

2007-12-23 21:48:06.64 spid134 BackupDiskFile::OpenMedia: Backup device '
alaska\e$\prd_full.BAK' failed to open. Operating system error = 32(The process cannot access the file because it is being used by another process.).

2007-12-23 21:48:06.64 spid144 BackupMedium::ReportIoError: read failure on backup device '
alaska\e$\prd_full.BAK'. Operating system error 64(The specified network name is no longer available.).

2007-12-23 21:48:06.64 spid144 Internal I/O request 0x2CE53928: Op: Read, pBuffer: 0x00000000, Size: 94, Position: 51019212887767344, RetryCount: 753218864, SubIoCount: 753218880, UMS: Internal: 0x0, InternalHigh: 0x0, Offset: 0x2BD40578, OffsetHigh: 0x2CE539A0, m_buf: 0x2CE539A8, m_len: 1, m_actualBytes: 0, m_errcode: 64, BackupFile: n/a 2007-12-23 21:48:06.64 backup BACKUP failed to complete the command BACKUP DATABASE [PRD] TO [prd_full] WITH INIT , NOUNLOAD , NAME = N'prd_full', SKIP , STATS = 10, NOFORMAT DECLARE @i INT select @i = position from msdb..backupset where database_name='PRD'and type!='F' and backup_set_id=(select max(backup_set_id) f2007-12-23 21:50:23.14 spid144 BackupDiskFile::OpenMedia: Backup device '
alaska\e$\prd_full.BAK' failed to open. Operating system error = 64(The specified network name is no longer available.).

Someone I know what I can do to solve this problem?

Thanks

Edited by: Ademir de Souza on Jan 3, 2008 2:52 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

It seems you have network problems between the system backing up and the target system.

Was a backup running on a target system?

--

Markus

Former Member
0 Kudos

Yes, the backup runs on sql and written over the network in another machine on the network.

You think it is better to save the backup locally and then record the server on the network?

Thanks

markus_doehr2
Active Contributor
0 Kudos

The problem here is:

If a another program (e. g. tape backup, virus scanner etc.) is running on the target system, it will "lock" the file and thus producing this error. Finally the system will stop backing up with a network error message because the target system doesn't pick the packets.

I would do the backup locally - but on a different disk than the database files are residing on.

Markus