February 14, 2011 at 10:23 am
I have a differential backup that runs fine one day then fails the next or it runs ok for several days then fails. The database part of the backup runs fine but when it starts to do the log backup I get the following error:
(Message 3211) Processed 7 pages for database 'tracehostdb', file 'tracehostdb_log' on file 7. [SQLSTATE 01000] (Message 4035) The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'FlushFileBuffers' on 'tracehostdb(\\waseca-db2\SQL_Backups\Siemens_database_backup\tracehostdb.bak)'. [SQLSTATE 42000] (Error 3634) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
I have increased the memory and also enabled parallelism to help with this issue. Anyone else having this problem or know what to do to fix it?
thanks,
JG
February 14, 2011 at 7:46 pm
I would guess that you have a flaky connection to your remote share, hence why SQL Server was unable to write the backup data successfully.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
February 15, 2011 at 1:19 am
janet.gillespie (2/14/2011)
I have a differential backup that runs fine one day then fails the next or it runs ok for several days then fails. The database part of the backup runs fine but when it starts to do the log backup I get the following error:(Message 3211) Processed 7 pages for database 'tracehostdb', file 'tracehostdb_log' on file 7. [SQLSTATE 01000] (Message 4035) The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'FlushFileBuffers' on 'tracehostdb(\\waseca-db2\SQL_Backups\Siemens_database_backup\tracehostdb.bak)'. [SQLSTATE 42000] (Error 3634) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
I have increased the memory and also enabled parallelism to help with this issue. Anyone else having this problem or know what to do to fix it?
thanks,
JG
You have problem in your network drive. ask your N\W team to help you.
I have a question
Why you want take the backup to N/W drive/folder?
Instead of,
backup the Db to local then move it to N/W.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
February 15, 2011 at 7:35 am
The jobs were setup before I took this position. I am looking to correct issues as they stand before redoing jobs.
February 15, 2011 at 8:34 am
I have seen this regularly, and it can be a pain to solve without a lot of trial and error. I am struggling with it right now on a server in the environment I inherited.
For starters, the network is a good place to start. Ask the following questions:
1. What other processes are going on? Is a defrag being performed on the remote disk? Does a re-set of a switch/router/etc. etc. occur?
There are many things that can be causing a network glitch.
2. How much memory is being allocated to the OS on SQL Server? This may need to be increased.
3. The settings or driver of the nic card may need to be upgraded.
4. If this is Enterprise edition, turn on compression.
As for backing up locally, and then copying, that doesn't make a lot of sense. If the issue is caused by the network, it will still appear. It adds more steps to the process. It increases the time required before the tape backup can run. The local disk space requirements go up.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
February 15, 2011 at 11:41 am
I will definitely look at trying to pinpoint the network issues. I have already increased the memory and it didn't make that much of a difference. I also agree that the local copying and then moving is just extra work and would not change network issues.
February 15, 2011 at 7:33 pm
janet.gillespie (2/15/2011)I also agree that the local copying and then moving is just extra work and would not change network issues.
The main objective is to get a backup made consistently. That is not happening for you now. Also, there are so many possible points of failure with regards to a network, compared to a local disk. Thus, you may address one specific network issue now, but other issues may come up in the future.
With regards to the hassle of copying the file, you may want to consider using 3rd party tools. Robocopy is useful in synchronizing folders, and can tolerate network interruptions. 3rd party SQL Server backup tools, like Red Gate's* SQL Backup, can create smaller backup files by compression, and also copy those files to remote shares and also tolerate intermittent network interruptions.
* A company I work for.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
January 13, 2014 at 5:21 am
Try this
Go to Start > Run > Regedit and find the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
If there is a value for SessTimeout , backup the current value and then change it to 360 . If the value is not there please create a new registry key by right clicking select new/DWORD , name the Dword SessTimeout and set it to a value of 360.
Please reply the status of your issue once you done.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply