Backup during re-index

• Erin.

  SSCertifiable

  Points: 5237

  More actions

  August 19, 2013 at 3:06 pm

  #281358

  We have a database that at times can take up to 18 days to re-index. The database is in simple recovery model and runs a full backup every 12 hours to storage directory not on this SQL Server. Randomly the backup will fail with the following error messages to SQL logs.

  Error: 18210, Severity: 16, State: 1.

  BackupIoRequest::ReportIoError: write failure on backup device 'PATH\FileName.bak'. Operating system error 2(The system cannot find the file specified.).

  Error: 3041, Severity: 16, State: 1.

  BACKUP failed to complete the command BACKUP DATABASE dbname. Check the backup application log for detailed messages.

  Error: 3634, Severity: 16, State: 2.

  The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'SetEndOfFile' on 'PATH\FileName.bak'.

  Error: 3634, Severity: 16, State: 2.

  The operating system returned the error '64(The specified network name is no longer available.)' while attempting 'FlushFileBuffers' on 'PATH\FileName.bak'.

  I feel this must be a network connection issue, but our network engineers are not seeing anything on their end. Is it possible re-index could cause something like this?

• Gail Shaw

  SSC Guru

  Points: 1004504

  More actions

  August 19, 2013 at 4:06 pm

  #1642893

  Nothing to do with reindex.

  The reason's given. "The specified network name is no longer available.", the network dropped and the backup failed as a result.

  p.s. 18 days to reindex? What's that, a 100+TB database you have there?

  Gail Shaw
  Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
  SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

  We walk in the dark places no others will enter
  We stand on the bridge and no one may pass