December 27, 2011 at 5:31 pm
Hi All,
Issue Scenario and Server Confgn:
Win Server 2003 Ent Edn with Sp2;
SS2008 Enterprise Edn, Version: 10.0.4000.0, Database whose backup is failing is of size=70 GB
From last few days one of the backup jobs configured to take backup on network disk, on our servers started failing with following messages:-
BACKUP DATABASE is terminating abnormally.
[SQLSTATE 42000] (Error 3013). The step failed.
In eventvwr it is captured:
1130(failed to retrieve text for this error. Reason: 1815)
[SQLSTATE 42000] (Error 3202)
Observations:-
1. Backup disk has more than enough free disk space (around 129 GBs)
2. On Running backup manually, it succeeds upto 80%, then suddenly failed with above error.
3. Small databases manual backup is also succeeding
Tried a lot to check for its cause, but not success yet, please help.
December 27, 2011 at 7:09 pm
You say this is a network disk, have you tried to backup to local disk?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 27, 2011 at 10:55 pm
Set your backup to compressed. Better yet, make that the server default.
That will reduce the size of the backup and the amount of data you have to send over the network.
December 27, 2011 at 11:29 pm
Some shots you need to try
1. Either free some space or change the disk drive where the backup log is being created.
2. How much estimated size would be of that db backup?
3. check what error log explained about it ?
4. post the complete error here.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
December 28, 2011 at 8:40 am
It’s worth reading following KB article.
Error message when you perform a database backup to disk or tape or a database restore from disk or tape: "3266," "3013"
December 28, 2011 at 8:51 am
Try this hope this one helps you out.
http://www.sqldbadiaries.com/2010/12/24/the-backup-data-is-incorrectly-formatted/
December 29, 2011 at 6:29 pm
Hi,
Thanks to all for response, however problem still there..
SQLRNNR : Yes, Taken database backup in compressed form on local disk
Michael : I have also taken backup using compression on Network..Ist time it succeeds but on next day it completed but also given following error:
"The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'FlushFileBuffers' "
Also physical backup file exists on network path as well.
As we donot have enough local isk space and backups need to be taken on Network drive only, please help how to rule out this problem.
December 29, 2011 at 7:34 pm
While running your backup across the network, get a netadmin to run wireshark and capture network activity between the host and network share. This is to try and rule out network disconnects or network latency that may be causing the problems.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 29, 2011 at 7:41 pm
ankur_libra (12/29/2011)
Hi,Thanks to all for response, however problem still there..
SQLRNNR : Yes, Taken database backup in compressed form on local disk
Michael : I have also taken backup using compression on Network..Ist time it succeeds but on next day it completed but also given following error:
"The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'FlushFileBuffers' "
Also physical backup file exists on network path as well.
As we donot have enough local isk space and backups need to be taken on Network drive only, please help how to rule out this problem.
This error is an indication of a network problem:
[font="Arial Narrow"]"The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'FlushFileBuffers' "[/font]
It really isn't a SQL Server problem; it's an issue with your network connectivity to the location you are backing up to. It could be a bad or improperly configured NIC card or switch port, but there are many other reasons why you can get this error.
December 30, 2011 at 4:14 am
Michael Valentine Jones (12/29/2011)
...This error is an indication of a network problem:
[font="Arial Narrow"]"The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'FlushFileBuffers' "[/font]
It really isn't a SQL Server problem; it's an issue with your network connectivity to the location you are backing up to. It could be a bad or improperly configured NIC card or switch port, but there are many other reasons why you can get this error.
Agree with you Michael.
I have already posted a pointer to KB article. It suggests following could be the cause of Error.
A filemark in the backup device could not be read. There are many reasons why you may encounter a filemark error. Some of the reasons include the following :
•A media failure may occur on the device where the backup is located.
•A write failure may occur during the creation of the backup.
For example, a loss of connectivity may occur during a network backup. Or, a failure of the IO path to flush the write to disk may occur after the write to disk was reported to SQL server as successful.
January 2, 2012 at 6:22 pm
Thanks All,
For a time being I am taking compressed backups on local hard disk. Also last day backup of same database to same network device occured successfully. :w00t:
As suggested by you, I will be checking the same and will update you all.
Regards,
Ankur
January 2, 2012 at 8:53 pm
Good - keep us posted with your findings.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply