Thursday, March 29, 2012

BACKUP failing! HELP!

I'm trying to backup a SQL 7.0 database to a network server (NT) from
Enterprise Manager and am getting the following error:

Title bar: Microsoft SQL DMO (ODBC SQL State: 42000)
Message: Backup or restore operation terminating abnormally.

The SQL Log has the following message:
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\myserver\bu_sql$\bu_mydb1.bak'. Operating system error 64(The
specified network name is no longer available.).

When I run a scheduled job that backs up mydb1, it fails with the
following message: Processed 50968 pages for database 'mydb1', file
'mydb1_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1
pages for database 'mydb1', file 'mydb1_Log' on file 1. [SQLSTATE
01000] (Message 4035) Backup or restore operation terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

This appears to a network problem but the transaction log dumps from
the same database to the same network share work fine as does a full
backup of a different database (on the same SQL Server).

The file bu_mydb1.bak is being created on the network drive. The
network drive has plenty of available space. The file is only 423MB
and the share has 9GB free space.

Any ideas?jeff.strange@.lrc.state.ky.us (Jeff) wrote in message news:<7dafc839.0401130705.1dc48e96@.posting.google.com>...
> I'm trying to backup a SQL 7.0 database to a network server (NT) from
> Enterprise Manager and am getting the following error:
> Title bar: Microsoft SQL DMO (ODBC SQL State: 42000)
> Message: Backup or restore operation terminating abnormally.
> The SQL Log has the following message:
> BackupDiskFile::RequestDurableMedia: failure on backup device
> '\\myserver\bu_sql$\bu_mydb1.bak'. Operating system error 64(The
> specified network name is no longer available.).
> When I run a scheduled job that backs up mydb1, it fails with the
> following message: Processed 50968 pages for database 'mydb1', file
> 'mydb1_Data' on file 1. [SQLSTATE 01000] (Message 4035) Processed 1
> pages for database 'mydb1', file 'mydb1_Log' on file 1. [SQLSTATE
> 01000] (Message 4035) Backup or restore operation terminating
> abnormally. [SQLSTATE 42000] (Error 3013). The step failed.

There is an MS document that says your destination/remote server 'is
under stress' and you are getting i.o hits, based on error 3013. You
might look at the scheduling of the backup job.

The 3013 error says your remote disk drive 'is user stress'.
Basically, it is a timing/timeout because of the amount of disk
activity on the remote server.
> This appears to a network problem but the transaction log dumps from
> the same database to the same network share work fine as does a full
> backup of a different database (on the same SQL Server).
> The file bu_mydb1.bak is being created on the network drive. The
> network drive has plenty of available space. The file is only 423MB
> and the share has 9GB free space.
> Any ideas?

No comments:

Post a Comment