Options
Trouble with ClusterSharedVolume in Azure
Dave Farmer
Posts: 6
I have SQL Backup 8.4.1.527 installed on a SQL Server 2016 cluster in Azure with Cluster Shared Storage (using CSVFT file type) mounted as a sub-folder of the C: drive.
I've detailed the problem in reply to another thread https://forums.red-gate.com/viewtopic.php?f=20&t=78193&start=15 as the error I first saw was "SQL Backup exit code: 610", but I think it appropriate to start afresh as that was about previous versions of the software.
I cannot backup to the cluster storage:
and I cannot restore from it either:
If I backup to the local C: drive it works fine, if I move the .sqb file to the C: drive I can restore perfectly well, so it seems the cluster shared storage drive is the issue.
My Azure estate depends on this CSV for all the database files, backups included - is there anything I can do to get it to work? Is there anything you guys ate Red Gate can do to fix the problem in a new version?
The same errors occur when I attempt to restore a .bak
More data:
Native backup from SSMS works - backup and restore both fine with files on cluster or local storage.
SQL Backup .sqb fine if always on local storage, never on cluster storage.
SQL Backup .sqb on local storage, copied to cluster storage: restore fails.
SQL Backup .sqb converted to .bak on local storage: works.
SQL Backup .sqb on local storage then copied to cluster storage and converted to .bak: cannot restore (restore dialog doesn't see a backup set in the file to be restored)
SQL Backup .sqb on local storage then copied to cluster storage and converted to .bak which is then copied back to local storage: cannot restore (restore dialog doesn't see a backup set in the file to be restored)
It seems that when using SQL Backup, any process using the cluster storage breaks the restore.
I'm going live in a month, and I really need a backup/restore solution in place before then...
I've detailed the problem in reply to another thread https://forums.red-gate.com/viewtopic.php?f=20&t=78193&start=15 as the error I first saw was "SQL Backup exit code: 610", but I think it appropriate to start afresh as that was about previous versions of the software.
I cannot backup to the cluster storage:
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.
and I cannot restore from it either:
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
If I backup to the local C: drive it works fine, if I move the .sqb file to the C: drive I can restore perfectly well, so it seems the cluster shared storage drive is the issue.
My Azure estate depends on this CSV for all the database files, backups included - is there anything I can do to get it to work? Is there anything you guys ate Red Gate can do to fix the problem in a new version?
The same errors occur when I attempt to restore a .bak
More data:
Native backup from SSMS works - backup and restore both fine with files on cluster or local storage.
SQL Backup .sqb fine if always on local storage, never on cluster storage.
SQL Backup .sqb on local storage, copied to cluster storage: restore fails.
SQL Backup .sqb converted to .bak on local storage: works.
SQL Backup .sqb on local storage then copied to cluster storage and converted to .bak: cannot restore (restore dialog doesn't see a backup set in the file to be restored)
SQL Backup .sqb on local storage then copied to cluster storage and converted to .bak which is then copied back to local storage: cannot restore (restore dialog doesn't see a backup set in the file to be restored)
It seems that when using SQL Backup, any process using the cluster storage breaks the restore.
I'm going live in a month, and I really need a backup/restore solution in place before then...
Comments
Thanks for posting on the Redgate forums.
I believe you have an open ticket on this issue which is being investigated. Currently the investigation will continue there rather than on the forums. I will update this post when we have a resolution.
Dan Bainbridge
Product Support Engineer | Redgate Software