SQL Backup exit code: 610

andriancruz · January 27, 2015 12:59PM

Hi Everyone

I'm a newbie to redgate and first time to use the tools. I hope someone can help me to solve my issue. I'm trying to execute RESTORE FILELISTONLY but i'm getting error: SQL Backup exit code: 610 any idea what it means?

Thanks & Regards,
Andrian

petey · January 27, 2015 7:36PM

Could you please post the entire output from SQL Backup when you encounter that error, together with the RESTORE FILELISTONLY command you are trying to run? Thanks.

andriancruz · January 29, 2015 5:45PM

Hi Peter,

Thank you for your the reply.

Below are the script I'm using to restore the database using FILELISTONLY command. I'm using query analyzer using MSSQL Management Studio.

--Script:
EXECUTE master..sqlbackup '-SQL "RESTORE FILELISTONLY FROM DISK = ''DriveFilename.sqb''"'
GO

--Results:
Msg 1, Level 15, State 1, Line 0
Reading filelist of "Drive:Filename.sqb"

ReadFile failed for file: DriveFilename.sqb at position: 0
1/29/2015 2:38:06 PM: Re-attempt: 1
1/29/2015 2:38:36 PM: Re-attempt: 2
1/29/2015 2:39:06 PM: Re-attempt: 3
1/29/2015 2:39:36 PM: Re-attempt: 4
1/29/2015 2:40:06 PM: Re-attempt: 5
1/29/2015 2:40:36 PM: Re-attempt: 6
1/29/2015 2:41:06 PM: Re-attempt: 7
1/29/2015 2:41:36 PM: Re-attempt: 8
1/29/2015 2:42:06 PM: Re-attempt: 9
1/29/2015 2:42:36 PM: Re-attempt: 10
1/29/2015 2:42:36 PM: SetFilePointerEx error: The parameter is incorrect.

1/29/2015 2:43:06 PM: SetFilePointerEx error: The parameter is incorrect.

SQL Backup exit code: 610

Hope you can help me to my issue. Thanks a lot

Regards,
Andrian

petey · February 1, 2015 8:30PM

Could you pls run a RESTORE SQBHEADERONLY command and post the output e.g.

EXECUTE master..sqlbackup '-SQL "RESTORE SQBHEADERONLY FROM DISK = ''DriveFilename.sqb''"'

Also, what is the size of the backup file, and what is the type of disk that the file is residing on? Is it a network share, a local drive, or a SAN etc?

Thanks.

andriancruz · February 2, 2015 10:01PM

Hi Peter,

Thank you for the email.

The size of the backup file was 900+ MB and the file location sitting on SAN. Below are the results after execution: Thanks a lot!

SQL Backup v7.3.2.12

Reading SQB file header of "DriveFilename.sqb"

Error 560: File is missing or not accessible: DriveFilename.sqb.sqb

SQL Backup exit code: 560

(6 row(s) affected)

name value

exitcode 560
sqlerrorcode 0

(2 row(s) affected)

Regards, Andrian

petey · February 2, 2015 10:22PM

The error message indicates that SQL Backup could not find the file. Does the SQL Backup Agent service startup agent have access to the network share?

andriancruz · February 3, 2015 6:50PM

Hi Peter,

I'm able to execute the RESTORE SQBHEADERONLY and no issue found.

SQL Backup v7.3.2.12

Reading SQB file header of "Drive:Filename.sqb"

Backup group ID : 67803373
File number : 1 of 1
Threads : 7 (multi-threaded file)

Backup type : 1 (Database)
Native backup size : 9.281 GB
Database size : 10.990 GB
Backup start : Monday, February 02, 2015 12:06:13 AM
Backup end : Monday, February 02, 2015 12:08:35 AM

Server name : Servername
Database name : Databasename

First LSN : 13281000000067800037
Last LSN : 13281000000069400001
Checkpoint LSN : 13281000000067800037
Database backup LSN : 13281000000062800037

(21 row(s) affected)

name value

exitcode 0
sqlerrorcode 0
filename001 DriveFilename.sqb

(3 row(s) affected)

But when execute RESTORE FILELISTONLY I'm still getting same issue:

Msg 1, Level 15, State 1, Line 0
Reading filelist of "DriveFilename.sqb"

ReadFile failed for file: Drive:Filename.sqb at position: 0
2/3/2015 3:42:48 PM: Re-attempt: 1
2/3/2015 3:43:18 PM: Re-attempt: 2
2/3/2015 3:43:48 PM: Re-attempt: 3
2/3/2015 3:44:18 PM: Re-attempt: 4
2/3/2015 3:44:48 PM: Re-attempt: 5
2/3/2015 3:45:19 PM: Re-attempt: 6
2/3/2015 3:45:49 PM: Re-attempt: 7
2/3/2015 3:46:19 PM: Re-attempt: 8
2/3/2015 3:46:50 PM: Re-attempt: 9
2/3/2015 3:47:20 PM: Re-attempt: 10
2/3/2015 3:47:20 PM: SetFilePointerEx error: The parameter is incorrect.

2/3/2015 3:47:50 PM: SetFilePointerEx error: The parameter is incorrect.

SQL Backup exit code: 610
LogicalName PhysicalName Type FileGroupName Size MaxSize

Regards, Andrian

petey · February 3, 2015 10:16PM

Could you please run some tests for me using the SQL Backup Test Utility? You can download the test utility from here.

From the main menu, select the 'Tools > Check file integrity' item. Fill in the details of the backup file, and click on the 'Start' button. Does the validation run successfully? Then select the 'Tools > Misc tests' item from the main menu, enter the path to the network share where the backup file is located, and click on the 'Process button'. What is the reported disk sector size?

andriancruz · February 3, 2015 11:26PM

Hi Peter,

Yes, after the the file integrity check "File Is Valid" and the Disk sector size is 4096 bytes after Misc tests.

Regards, Andrian

petey · February 4, 2015 2:03AM

Hi, this was a bug addressed in SQL Backup 7.4 and newer. The current version of SQL Backup is 7.7. Could you please try updating SQL Backup, and see if you can then successfully read the file list from the backup file? Details of release 7.7 can be found here.

andriancruz · February 17, 2015 10:02PM

Hi Peter,

Thanks a lot for the help. After updating SQL Backup we're able to read now the files.

Cheers!

Regards, Andrian

trac · June 18, 2015 4:09PM

Hello everyone,

We are having the exact same issue as the original poster, including the results of RESTORE FILELISTONLY, RESTORE SQBHEADERONLY, and the test utility. Except we are running version 7.7. If it helps we are running SQL 2012 on Windows Server 2012 R2.

Any help would be appreciated.

Thanks in advance,
Kevin

petey · June 22, 2015 8:18AM

Could you please try patch 7.7.0.109 and let us know if it addresses your issue? You can download the patch from here:

ftp://support.red-gate.com/patches/sql_ ... _0_109.zip

To install the patch, stop the SQL Backup Agent service after ensuring no backup or restore jobs are running. Rename the existing executable files in the SQL Backup server components folder, then copy the files from the zip archive into that folder. Start the SQL Backup Agent service, and try running the restore commands.

trac · June 22, 2015 12:09PM

The patch worked, thanks. Will this patch be safe to update normally in the future?

petey · June 22, 2015 1:36PM

Yes, all subsequent patches and major/minor releases will include this patch.

Dave Farmer · March 1, 2017 1:09PM

I'm setting up new servers in Azure, and am having the exact same issue with SQL Backup 8.4.1.527 and SQL Server 2016 on Azure VMs
I have some databases I've set up on one of my new servers (a standalone server), I'm backing them up, copying the .sqb files to another new server (2-node active/passive cluster) and attempting to restore it there. The file selection dialog hangs for a while then reports failure with the "SetFilePointerEx error: The parameter is incorrect." error.

I've tried running these:

EXEC master..sqlbackup '-sql "RESTORE SQBHEADERONLY FROM DISK = &#91;&lt;file name&gt;&#93;"'
EXEC master..sqlbackup '-sql "RESTORE VERIFYONLY FROM DISK = &#91;&lt;file name&gt;&#93;"'

On the server that took the backup, both run fine but on the one where I've copied the file and want to restore, the headeronly works fine:

Backup group ID     : 266133037
File number         : 1 of 1
Threads             : 15 (multi-threaded file)
 
Backup type         : 1 (Database)
Native backup size  : 11.700 GB
Database size       : 15.625 GB
Backup start        : Wednesday, March 1, 2017 5:33:33 PM
Backup end          : Wednesday, March 1, 2017 5:34:14 PM
 
Server name         : &lt;server name&gt;
Database name       : &lt;database name&gt;
 
First LSN           : 167413000000754400106
Last LSN            : 167413000000760800001
Checkpoint LSN      : 167413000000754400106
Database backup LSN : 167413000000730400149

...but the verify gives the same error people have reported here:

Verifying file:
  &lt;filename.sqb&gt;
 
ReadFile failed for file: &lt;filename.sqb&gt; at position: 0
3/1/2017 5:53:43 PM: Re-attempt: 1
3/1/2017 5:54:13 PM: Re-attempt: 2
3/1/2017 5:54:43 PM: Re-attempt: 3
3/1/2017 5:55:13 PM: Re-attempt: 4
3/1/2017 5:55:43 PM: Re-attempt: 5
3/1/2017 5:56:13 PM: Re-attempt: 6
3/1/2017 5:56:43 PM: Re-attempt: 7
3/1/2017 5:57:13 PM: Re-attempt: 8
3/1/2017 5:57:43 PM: Re-attempt: 9
3/1/2017 5:58:13 PM: Re-attempt: 10
3/1/2017 5:58:13 PM: SetFilePointerEx error: The parameter is incorrect.
 
3/1/2017 5:58:43 PM: SetFilePointerEx error: The parameter is incorrect.
 
 
SQL Backup exit code: 610

SQL Backup service is running as a cluster admin user, and I've given explicit permissions on the folder containing the file.
I downloaded the SQL Backup Test Utilities application and ran that (on the server where I cannot restore) - it reported the file was OK.
I can restore the file on the original server just fine.

I'm stuck for ideas now...

petey · March 2, 2017 10:37AM

Could you please run some tests for me using the SQL Backup Test Utility? You can download the test utility from here.

Select the 'Tools > Misc tests' item from the main menu, enter the path to the folder where you copied the backup file to, and click on the 'Process button'. What is the reported disk sector size?

Dave Farmer · March 3, 2017 10:31AM

petey wrote:

Could you please run some tests for me using the SQL Backup Test Utility? You can download the test utility from here.

Select the 'Tools > Misc tests' item from the main menu, enter the path to the folder where you copied the backup file to, and click on the 'Process button'. What is the reported disk sector size?

512 bytes, same as the folder the backup was originally written to.

Dave Farmer · March 6, 2017 5:42AM

Further information... SQL Backup on the cluster - the one that can't read the file from elsewhere, also cannot backup. The log is as follows:

SQL Backup log file 8.4.1.1038
 
-SQL "BACKUP DATABASE &#91;Test&#93; TO DISK = '&lt;folder&gt;&lt;AUTO&gt;.sqb' WITH CHECKSUM, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, THREADCOUNT = 15, VERIFY "
 
-----------------------------  ERRORS AND WARNINGS -----------------------------
 
 
3/6/2017 10:26:36 AM: Backing up Test (full database) on LIVE instance to: 
3/6/2017 10:26:36 AM:   &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb
 
3/6/2017 10:26:36 AM: BACKUP DATABASE &#91;Test&#93;  TO VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC01', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC02',
 VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC03', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC04', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC05', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A
1A5-1AC6B41132BC06', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC07', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC08', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC09', VIRTUAL_DEVICE = 
 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC10', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC11', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC12', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC1
3', VIRTUAL_DEVICE = 'SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC14' WITH BUFFERCOUNT = 30, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (Test), 3/6/2017 10:26:36 AM', DESCRIPTION = N'Backup on 3/6/2017 10:26:36 AM  Server: 
 &lt;serverinstance&gt;  Database: Test', FORMAT, CHECKSUM
 
3/6/2017 10:31:36 AM: Thread 14 error: 
Error 620: Error writing to backup file(s).
3/6/2017 10:31:36 AM: Warning 210: Thread 14 warning: 
WriteFile failed for file: &lt;folder&gt;FULL_LIVE_DJFTest_20170306_102636.sqb at position: 0
3/6/2017 10:26:36 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:27:06 AM: Re-attempt: 1
3/6/2017 10:27:06 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:27:36 AM: Re-attempt: 2
3/6/2017 10:27:36 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:28:06 AM: Re-attempt: 3
3/6/2017 10:28:06 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:28:36 AM: Re-attempt: 4
3/6/2017 10:28:36 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:29:06 AM: Re-attempt: 5
3/6/2017 10:29:06 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:29:36 AM: Re-attempt: 6
3/6/2017 10:29:36 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:30:06 AM: Re-attempt: 7
3/6/2017 10:30:06 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:30:36 AM: Re-attempt: 8
3/6/2017 10:30:36 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:31:06 AM: Re-attempt: 9
3/6/2017 10:31:06 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:31:36 AM: Re-attempt: 10
3/6/2017 10:31:36 AM: WriteFile failed for file: &lt;folder&gt;FULL_LIVE_Test_20170306_102636.sqb (87: The parameter is incorrect.)
3/6/2017 10:31:36 AM: 
3/6/2017 10:32:06 AM: SQL error 3013: BACKUP DATABASE is terminating abnormally.
3/6/2017 10:32:06 AM: SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_803D64F7-69C4-49C0-A1A5-1AC6B41132BC14:" 29(The system cannot write to the specified device.).
3/6/2017 10:32:06 AM: Processed 360 pages for database 'Test', file 'Test' on file 1.
3/6/2017 10:32:06 AM: Processed 3 pages for database 'Test', file 'Test_log' on file 1.

Dave Farmer · March 6, 2017 5:54AM

Further information...
The folder the .sqb was on, and the backup target are both on blob storage that is presented through the C: drive (I don't now the technical details and the consultant who set it up is unavailable for a week now!), but it's presented as C:ClusterStorageVolume1 as a Mounted Volume with CSVFS file system. According to Microsoft "Cluster Shared Volumes (CSV) enable multiple nodes in a failover cluster to simultaneously have read-write access to the same LUN (disk) that is provisioned as an NTFS volume", so should be visible as NTFS, but SQL Backup appears to be having a problem with it.

mcdasa · October 12, 2017 2:41AM

We had a exact same issue on Azure enviroment.
We raided number of disks(32 disks) using storage space.
And same error occured and none of restore commands worked. (SQL Backup exit code: 610)

So we finally attached single disk(which created in Azure Console and no raid applied) to vm and no errors occured at all worked perpect.

But this considered critical issues if redgate backup needs to use on Cloud Enviroment.
need to fix asap I Think.

Thank you.

SQL Backup exit code: 610

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk