Red Gate forums: SQL Backup 6

Hi Peter, on a server in question that frozen this morning there is no log file?

However I have one from a different server that also froze this morning but its dated 27/05/2010

Do you still want it?

Hi Yasir,
Thank you for your forum post and sorry that you have encountered a problem.

Can please reply and copy the contents of the SQL Backup Log file? Right click the entry in the Activity Hostory and select show log. Hopefully the log file will contain all exit codes from Windows, SQL and SQL Backup to help accurately identify the cause.

I suspect this error:

Quote:

665: The requested operation could not be completed due to a file system limitation.

Is from Windows or SQL. From the notes I have on the SQL Backup Exit Codes, Exit Code 665 is used to indicate that a beta version of SQL Backup has now expired.

I found this Microsoft ARTICLE which may help you.

Many Thanks
Eddie

I received the files you sent. It looks like you are using an older version of SQL Backup (6.2.0.134). The issue you are encountering could have been fixed in a new version of SQL Backup. Could you please try using version 6.5.0.23, which you can download using this URL:

ftp://support.red-gate.com/patches/sql_backup/SQB_6_5_2_23.zip

The zip file contains two files:

SQBCoreService.exe
SQLBackupC.exe

To apply the patch, please follow the steps below:

1. Close all GUI connections to the SQL Server.
2. Ensure that no SQL Backup jobs are in progress.
3. Stop the SQL Backup Agent Service, or disable the cluster resource if on a cluster.
4. On the SQL Server where the SQL Backup server components are installed, navigate to the installation directory. Defaults are:

32-bit Machines - C:\Program Files\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>
64-bit Machines - C:\Program Files (x86)\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>

5. In the folder you will find an existing SQBCoreService.exe and SQL BackupC.exe. Rename the existing files, for example to OLDSQBCoreService.exe and OLDSQLBackupC.exe.
6. Now copy in the files extracted from the downloaded zip.
7. Restart the SQL Backup agent service/cluster resource, and ensure that it starts successfully.
8. Perform a test backup to ensure that all is OK.

Thanks Eddie,

Here is the log, please review

SQL Backup log file 7.2.1.82

-SQL "BACKUP DATABASE [***MY_DATABASE_NAME***] TO DISK = '\\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb' WITH NO_CHECKSUM, COMPRESSION = 0, THREADCOUNT = 3 "

----------------------------- ERRORS AND WARNINGS -----------------------------

4/9/2013 1:16:23 AM: Backing up ***MY_DATABASE_NAME*** (full database) to:
4/9/2013 1:16:23 AM: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb

4/9/2013 1:16:23 AM: BACKUP DATABASE [***MY_DATABASE_NAME***] TO VIRTUAL_DEVICE = 'SQLBACKUP_954A8C27-3EC8-4717-AA4F-0CE9CE20C0E2', VIRTUAL_DEVICE = 'SQLBACKUP_954A8C27-3EC8-4717-AA4F-0CE9CE20C0E201', VIRTUAL_DEVICE = 'SQLBACKUP_954A8C27-3EC8-4717-AA4F-0CE9CE20C0E202'
WITH BUFFERCOUNT = 18, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (***MY_DATABASE_NAME***), 4/9/2013 1:16:23 AM', DESCRIPTION = N'Backup on 4/9/2013 1:16:23 AM Server: ***MY_SERVER_NAME*** Database: ***MY_DATABASE_NAME***', FORMAT

4/9/2013 4:00:14 AM: Thread 0 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
4/9/2013 4:00:14 AM: Warning 210: Thread 0 warning:
WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb at position: 378928104448
4/9/2013 3:55:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:55:43 AM: Re-attempt: 1
4/9/2013 3:55:43 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:56:13 AM: Re-attempt: 2
4/9/2013 3:56:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:56:43 AM: Re-attempt: 3
4/9/2013 3:56:43 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:57:13 AM: Re-attempt: 4
4/9/2013 3:57:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:57:43 AM: Re-attempt: 5
4/9/2013 3:57:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:58:14 AM: Re-attempt: 6
4/9/2013 3:58:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:58:44 AM: Re-attempt: 7
4/9/2013 3:58:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:59:14 AM: Re-attempt: 8
4/9/2013 3:59:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:59:44 AM: Re-attempt: 9
4/9/2013 3:59:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 4:00:14 AM: Re-attempt: 10
4/9/2013 4:00:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 4:00:14 AM:
4/9/2013 4:00:14 AM: Thread 1 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
4/9/2013 4:00:14 AM: Warning 210: Thread 1 warning:
WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb at position: 378928104448
4/9/2013 3:55:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:55:43 AM: Re-attempt: 1
4/9/2013 3:55:43 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:56:13 AM: Re-attempt: 2
4/9/2013 3:56:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:56:43 AM: Re-attempt: 3
4/9/2013 3:56:43 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:57:13 AM: Re-attempt: 4
4/9/2013 3:57:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:57:43 AM: Re-attempt: 5
4/9/2013 3:57:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:58:14 AM: Re-attempt: 6
4/9/2013 3:58:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:58:44 AM: Re-attempt: 7
4/9/2013 3:58:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:59:14 AM: Re-attempt: 8
4/9/2013 3:59:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:59:44 AM: Re-attempt: 9
4/9/2013 3:59:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 4:00:14 AM: Re-attempt: 10
4/9/2013 4:00:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 4:00:14 AM:
4/9/2013 4:00:14 AM: Thread 2 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
4/9/2013 4:00:14 AM: Warning 210: Thread 2 warning:
WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb at position: 378928104448
4/9/2013 3:55:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:55:43 AM: Re-attempt: 1
4/9/2013 3:55:43 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:56:13 AM: Re-attempt: 2
4/9/2013 3:56:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:56:43 AM: Re-attempt: 3
4/9/2013 3:56:43 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:57:13 AM: Re-attempt: 4
4/9/2013 3:57:13 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:57:43 AM: Re-attempt: 5
4/9/2013 3:57:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:58:14 AM: Re-attempt: 6
4/9/2013 3:58:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:58:44 AM: Re-attempt: 7
4/9/2013 3:58:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:59:14 AM: Re-attempt: 8
4/9/2013 3:59:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 3:59:44 AM: Re-attempt: 9
4/9/2013 3:59:44 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 4:00:14 AM: Re-attempt: 10
4/9/2013 4:00:14 AM: WriteFile failed for file: \\***MY_BACKUP_PATH***\***MY_BACKUP_FOLDER***\***MY_SERVER_NAME***\***MY_SERVER_NAME***_***MY_DATABASE_NAME***_FULL_20130409_011623.sqb (665: The requested operation could not be completed due to a file system limitation)
4/9/2013 4:00:14 AM:
4/9/2013 4:00:14 AM: SQL error 3013: SQL error 3013: BACKUP DATABASE is terminating abnormally.
4/9/2013 4:00:14 AM: SQL error 3271: SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_954A8C27-3EC8-4717-AA4F-0CE9CE20C0E2:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
4/9/2013 4:00:14 AM: SQL error 3202: SQL error 3202: Write on "SQLBACKUP_954A8C27-3EC8-4717-AA4F-0CE9CE20C0E2" failed: 1117(The request could not be performed because of an I/O device error.)

What was the size of the incomplete backup file, and what file system format was the disk using?

Thanks.

This has been applied I will keep you posted.

I had upgraded from the older version already since my post start however I was running 6.5.1.9 not 6.5.2.23.

I will inform you if we experience any further freezing.

Is there a change log for 6.5.2.23?

Thank you

Thanks Peter,
The last full backup was failed at 480 GB and it should be 1.8 TB. The file system format is NTFS.

Googling turned up some possibilities:

- turning off NTFS compression
- defragmenting the disk

Error when attempting a restore. Version: 6.4.0.56

Could you please try patch 6.5.2.23?

ftp://support.red-gate.com/patches/sql_backup/SQB_6_5_2_23.zip

The zip file contains two files:

SQBCoreService.exe
SQLBackupC.exe

To apply the patch, please follow the steps below:

1. Close all GUI connections to the SQL Server.
2. Ensure that no SQL Backup jobs are in progress.
3. Stop the SQL Backup Agent Service, or disable the cluster resource if on a cluster.
4. On the SQL Server where the SQL Backup server components are installed, navigate to the installation directory. Defaults are:

32-bit Machines - C:\Program Files\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>
64-bit Machines - C:\Program Files (x86)\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>

5. In the folder you will find an existing SQBCoreService.exe and SQL BackupC.exe. Rename the existing files, for example to OLDSQBCoreService.exe and OLDSQLBackupC.exe.
6. Now copy in the files extracted from the downloaded zip.
7. Restart the SQL Backup agent service/cluster resource, and ensure that it starts successfully.
8. Perform a test backup to ensure that all is OK. Then test to see if the original error occurs.

Thanks for the reply Peter. What is this error? We have been using this version for almost 3 years, we have clients who are receiving backups from us in this version. Management is reluctant to make changes. Why did this error happen all of the sudden?

Thanks again,
David

I can't remember the cause, as it's been almost 2 years since 6.5 was released. Was version 6.5 able to restore from your backup file?

Hey Peter,

I switched out the files and the first transaction log backups came back with this error:

"Executed as user: dbo. SQL Backup failed with exit code: 667 SQL error code: 0 [SQLSTATE 42000] (Error 50000). The step failed."

Thanks,
David

Did this occur cause the transaction logs were on a different version than the full backups? Is the first action after the switch to take a full backup?

Thanks,
David

My apologies Peter,

The server that is taking the backup is running Redgate backup version 5.3.0.178. The server that we are attempting a partial restore on is running version 6.4.0.56. How would this change the solution to our problem? What cost/work is involved in upgrading version 5 listed above to the version to sent me 6.5.2.23?

Thanks for your time,
David

Version 6.5.2.23 can restore backups created in 5.3.0.178. The error you are experiencing (667), indicates that the SQL Backup trial period has expired.

Hello,

This has improve the reliablilty a treat but the issue we have now is that every so often the sql job stops and we get a 2KB transaction log generated with no LSN details. When this is transfered it stops log shipping for the database in question.

Can you assist further?

Could you please check if SQL Backup generated a stack trace file when the job failed, as described in my first post in this thread? If so, could you please send me that file, and also the 2 Kb trx log backup file that's generated?

Thanks.

E-Mail sent.

the stack trace attached file is from the DR server. Red gate has not generated a error file on the server where the 2KB file has been produced.

Could you please send me the SQL Backup log file for the backup that generated the 2 Kb file? The default folder where the logs are stored is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> on Windows 2003 and older, and C:\ProgramData\Red Gate\SQL Backup\Log\<instance name> on Windows Vista and newer.

Thanks.

RE: SQLBackup Issue - Service

RE: SQLBackup 6 Qustion backup error on large database 1.9 TB

RE: SQLBackup Issue - Service

RE: SQLBackup 6 Qustion backup error on large database 1.9 TB

RE: SQLBackup 6 Qustion backup error on large database 1.9 TB

RE: SQLBackup Issue - Service

RE: SQLBackup 6 Qustion backup error on large database 1.9 TB

RE: SQLBackup 6 Qustion backup error on large database 1.9 TB

Error: Rijndael: Invalid key size - 0, red gate

RE: Error: Rijndael: Invalid key size - 0, red gate

RE: Error: Rijndael: Invalid key size - 0, red gate

RE: Error: Rijndael: Invalid key size - 0, red gate

RE: Error: Rijndael: Invalid key size - 0, red gate

RE: Error: Rijndael: Invalid key size - 0, red gate

RE: Error: Rijndael: Invalid key size - 0, red gate

RE: Error: Rijndael: Invalid key size - 0, red gate

RE: SQLBackup Issue - Service

RE: SQLBackup Issue - Service

RE: SQLBackup Issue - Service

RE: SQLBackup Issue - Service