Knowledge Base

Restore operation errors with exitcode 680

Category: Troubleshooting & error messages
Date: 20 Mar 2009
Product: SQL Backup
When restoring a database, you may get the following result :

exitcode 680
sqlerrorcode 0

Warning 170: No LSN information contained in file:
'LOG_(local)_DATABASE_NAME_20090304_051003.sqb'

Warning 170: Log files are not in sequence:
'LOG_(local)_DATABASE_NAME_20090304_053003.sqb' and
'LOG_(local)_DATABASE_NAME_20090304_054002.sqb'

Restoring DATABASE_NAME (transaction logs) on INSTANCE_NAME instance from:


  F:\BACKUPS\Temp\LOG_(local)_DATABASE_NAME_20090304_051003.sqb

The media set for database 'DATABASE_NAME' has 1 family members but
only 4 are provided. All members must be provided.

SQL Backup exit code: 680

When restoring multiple transaction log backups, SQL Backup reads to SQL Backup header file of each to find its LSNs. When SQL Backup finishes backing up a database, it populates its' own header, but this operation can sometimes fail, leaving the header empty. The header information is used to place the files in the correct order.

If SQL Backup can't read the LSN information from the header or there is no LSN information in the header, it can not put the files into the correct order, so errors can occur.

The easiest way to restore these files is to restore them one at a time using WITH STANDBY in date order using the extended stored procedure. This will negate the need for the SQL Backup header and restore these troublesome files in order.

Alternatively, try using the SQBHeaderFix utility on the files to see if they can repair it. The SQBHeaderFix utility can read the Native SQL Backup header and recreate the SQL Backup header using that information.

You can download this utility from:

ftp://support.red-gate.com/Patches/SQL_Backup/SQBHeaderFix.zip