Options
Cloud SQL Database Backups to S3 Storage
jcricegp
Posts: 18 Bronze 3
My company is making an increasing investment to the Amazon EC2 Environment. We are currently attempting to backup our EC2 SQL Server instances to S3 storage using third party applications to map the drive and then backing up the SQL Databases to this drive using SQL Backup Pro. We are getting mixed results. The main issues appear to be thread errors. I am including error log detail for three different error codes.
Is this configuration something that RedGate supports? Or do you have an alternative.
Thanks,
Error
Thread 0 error:
Error 605: Error creating backup file(s). No files could be created.
Warning 200: Thread 0 warning:
2/20/2017 2:06:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:06:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:07:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:07:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:08:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:08:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:09:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:09:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:10:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:10:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:11:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
Error
Thread 0 error:
Error 620: Error writing to backup file(s).
Warning 210: Thread 0 warning:
WriteFile failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb at position: 1024
2/19/2017 5:42:01 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:42:31 PM: Re-attempt: 1
2/19/2017 5:42:31 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:43:01 PM: Re-attempt: 2
2/19/2017 5:43:02 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:43:32 PM: Re-attempt: 3
2/19/2017 5:43:32 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:44:02 PM: Re-attempt: 4
2/19/2017 5:44:03 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:44:33 PM: Re-attempt: 5
2/19/2017 5:44:33 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:45:03 PM: Re-attempt: 6
2/19/2017 5:45:04 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:45:34 PM: Re-attempt: 7
2/19/2017 5:45:34 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:46:04 PM: Re-attempt: 8
2/19/2017 5:46:05 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:46:35 PM: Re-attempt: 9
2/19/2017 5:46:35 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:47:05 PM: Re-attempt: 10
2/19/2017 5:47:06 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_2441783C-D73D-4AC1-B7AC-8AC1967C8C67:" 29(The system cannot write to the specified device.).
Processed 416 pages for database '<DB>', file '<DB>' on file 1.
Processed 608 pages for database '<DB>', file '<DB>_INDEXES' on file 1.
Processed 2 pages for database <DB>', file '<DB>r_LOG' on file 1.
Error
2/15/2017 9:40:01 PM: Processed 10773552 pages for database '<DB>', file 'DISC_Data' on file 1.
2/15/2017 9:40:01 PM: Processed 2 pages for database '<DB>', file '<DB>_Log' on file 1.
2/15/2017 9:40:01 PM: BACKUP DATABASE successfully processed 10773554 pages in 2321.804 seconds (36.251 MB/sec).
2/15/2017 9:40:02 PM: Failed to read file header (\DBDUMP02J-S3-02ackupsTier4<ServerName>@<DB>@FULL@20170215@210044.sqb): The operation completed successfully. Read 0 bytes.
Is this configuration something that RedGate supports? Or do you have an alternative.
Thanks,
Error
Thread 0 error:
Error 605: Error creating backup file(s). No files could be created.
Warning 200: Thread 0 warning:
2/20/2017 2:06:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:06:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:07:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:07:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:08:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:08:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:09:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:09:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:10:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:10:50 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
2/20/2017 2:11:20 AM: Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
Warning 480: Failed to create output folder: \DBDUMP02J-S3-02ackupsTier4.
Error
Thread 0 error:
Error 620: Error writing to backup file(s).
Warning 210: Thread 0 warning:
WriteFile failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb at position: 1024
2/19/2017 5:42:01 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:42:31 PM: Re-attempt: 1
2/19/2017 5:42:31 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:43:01 PM: Re-attempt: 2
2/19/2017 5:43:02 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:43:32 PM: Re-attempt: 3
2/19/2017 5:43:32 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:44:02 PM: Re-attempt: 4
2/19/2017 5:44:03 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:44:33 PM: Re-attempt: 5
2/19/2017 5:44:33 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:45:03 PM: Re-attempt: 6
2/19/2017 5:45:04 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:45:34 PM: Re-attempt: 7
2/19/2017 5:45:34 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:46:04 PM: Re-attempt: 8
2/19/2017 5:46:05 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:46:35 PM: Re-attempt: 9
2/19/2017 5:46:35 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
2/19/2017 5:47:05 PM: Re-attempt: 10
2/19/2017 5:47:06 PM: FlushFileBuffers failed for file: \DBDUMP01F-S3-01ackupsTier4<ServerName>@<DB>@FULL@20170219@174151.sqb, error: A device attached to the system is not functioning.
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_2441783C-D73D-4AC1-B7AC-8AC1967C8C67:" 29(The system cannot write to the specified device.).
Processed 416 pages for database '<DB>', file '<DB>' on file 1.
Processed 608 pages for database '<DB>', file '<DB>_INDEXES' on file 1.
Processed 2 pages for database <DB>', file '<DB>r_LOG' on file 1.
Error
2/15/2017 9:40:01 PM: Processed 10773552 pages for database '<DB>', file 'DISC_Data' on file 1.
2/15/2017 9:40:01 PM: Processed 2 pages for database '<DB>', file '<DB>_Log' on file 1.
2/15/2017 9:40:01 PM: BACKUP DATABASE successfully processed 10773554 pages in 2321.804 seconds (36.251 MB/sec).
2/15/2017 9:40:02 PM: Failed to read file header (\DBDUMP02J-S3-02ackupsTier4<ServerName>@<DB>@FULL@20170215@210044.sqb): The operation completed successfully. Read 0 bytes.
Comments
Can you check the permissions of the SQL Backup Agent Service user account to the \DBDUMP02J-S3-02ackupsTier4 file directory? Does the user have read/write permissions to there?
Does the user also have the following permissions showcased in the documentation: https://documentation.red-gate.com/disp ... ermissions
Thanks!
Sean Quigley | Product Support Engineer | Redgate Software
Have you visited our Help Center?