How can we help you today? How can we help you today?
Dave Farmer
Activity overview Badges (0) Posts (1) Comments (4)

Comments

Sort by recent activity
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. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup exit code: 610
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 se...
0 votes
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. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup exit code: 610
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...
0 votes
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 [Test] TO DISK = '<folder><AUTO>.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: <folder>FULL_LIVE_Test_20170306_102636.sqb 3/6/2017 10:26:36 AM: BACKUP DATABASE [Test] 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: <serverinstance> 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: <folder>FULL_LIVE_DJFTest_20170306_102636.sqb at position: 0 3/6/2017 10:26:36 AM: WriteFile failed for file: <folder>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: <folder>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: <folder>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: <folder>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: <folder>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: <folder>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: <folder>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: <folder>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: <folder>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: <folder>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: <folder>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. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup exit code: 610
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...
0 votes
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 = [<file name>]"' EXEC master..sqlbackup '-sql "RESTORE VERIFYONLY FROM DISK = [<file name>]"' 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 : <server name> Database name : <database name> 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: <filename.sqb> ReadFile failed for file: <filename.sqb> 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... / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup exit code: 610
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 stan...
0 votes
Total activity
6
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1