Red Gate forums: SQL Backup 6

RE: SQL Backup Agent restarting unexpectedly....

petey — Tue, 21 May 2013 00:52:46 GMT

Do you mean that when a single instance fails over e.g. Instance A, then both SQL Backup Agent-A and SQL Backup Agent B restart on Instance A's active node?

SQL Backup Agent restarting unexpectedly....

CorrinHarris — Mon, 20 May 2013 16:17:50 GMT

We have 2 clustered instances of SQL that can shares nodes. Normally instance A runs on node 1 and instance B runs on node 2. Both have their own Redgate SQL Backup Agent services set up and running as clustered resouces, SQL Backup Agent-A (on node 1) and SQL Backup Agent-B (on node 2) . However we have noticed that when an instance fails over - both SQL Backup Agents seem to start/restart on the active node - we would have expected just one to start - there are no disk dependencies etc. This also happens when we manually fail back.

The only error we can find is as follows:-
Faulting application SQBCoreService.exe, version 6.5.1.9, time stamp 0x2a425e19, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x000a000d, process id 0x1b30, application start time 0x01ce4ffceedb85c0.

Any assistance would be appreciated...

RE: SQLBackup Issue - Service

petey — Mon, 13 May 2013 15:06:15 GMT

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

Kendall359x — Mon, 13 May 2013 12:24:44 GMT

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.

RE: SQLBackup Issue - Service

petey — Mon, 13 May 2013 02:22:51 GMT

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.

RE: SQLBackup Issue - Service

Kendall359x — Thu, 09 May 2013 08:06:13 GMT

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?

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

petey — Wed, 08 May 2013 03:22:48 GMT

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.

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

dklein9930 — Mon, 06 May 2013 16:59:44 GMT

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

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

dklein9930 — Mon, 06 May 2013 13:54:37 GMT

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

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

dklein9930 — Mon, 06 May 2013 13:46:42 GMT

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

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

petey — Fri, 03 May 2013 01:15:32 GMT

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?

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

dklein9930 — Thu, 02 May 2013 19:43:10 GMT

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

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

petey — Thu, 02 May 2013 08:38:41 GMT

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.

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

dklein9930 — Wed, 01 May 2013 19:49:04 GMT

Error when attempting a restore. Version: 6.4.0.56

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

petey — Wed, 17 Apr 2013 00:43:17 GMT

Googling turned up some possibilities:

- turning off NTFS compression
- defragmenting the disk