Comments
17 comments
-
Could you please let us know the exact version and edition of SQL Backup 3 that's used?
Thanks. -
It looks like 3.2 Standard
-
Thanks, it's definitely a bug. I'll post a patch tomorrow. Sorry about that.
-
You can download patch 6.2.0.1002 from here:
ftp://ftp.red-gate.com/patches/SQL_Back ... 0_1002.zip
You would need to stop the SQL Backup Agent service prior to replacing the existing copy (I would suggest renaming it in case you need it next time), after ensuring that no backups/restores are currently running.
Thanks. -
Is this the correct path? I'm getting 550 Folder /patches/SQL_Backup/SQB_6_2_0_1002.zip not found
I did have another ftp site given to me previously that is ftp://support.red-gate.com/Patches/SQL_Backup/ and I did find a SQB_6_2_0_1002.zip file dated 9/17. I guessed that was the one but I'm still getting the same error. -
One other observation. We started recommending that our users use the Pro version. This has a higher encryption - 256. When creating backups the user can choose between 128 or 256. Using the command line the "KEYSIZE" variable needs to be used. This is not recognized by the 3.2 Standard edition since you could not choose the encryption level. I think that might be where the problem might be.
-
Sorry about that, it should indeed have been ftp://support.red-gate.com/Patches/SQL_ ... 0_1002.zip.
IIRC, SQL Backup 3 only offerred 1 level of encryption, which was 256-bit, and there was only 1 edition. There were no other encryption levels offered, hence no support for the KEYSIZE option.
Starting with version 4, there were 2 levels of encryption, 128-bit and 256-bit. The Lite ediion didn't allow encryption at all, Standard allowed 128-bit and Pro allowed 128-bit and 256-bits.
I've tested 6.2.0.1002 to restore an encrypted backup file created using 3.2, and it works fine. Could you send me the first 1024 bytes of the backup file in question? You can use the 'Extract file header' function in the SQL Backup test utility,which you can download from here:
ftp://support.red-gate.com/Patches/SQL_Backup/SBaTU.zip
Thanks. -
When I try to use that utility I get a popup window that has the same error - Rijndael: Invalid key size - 0
I tested on files that we are able to process using ver 6.0 and the utility works fine.
We are able to process these files using SQL Backup 5.4 without any problems, so I know that there is nothing wrong with those files. I just don't want to downgrade the software on this particular machine. I've restarted the SQL Backup service to see if that would help but it does not. -
In that utility, select the 'Extract file header' from the 'Tools' menu item. Fill in the file names, and enter 1024 bytes to extract. Send the resulting file to me.
Thanks. -
I emailed the files to you.
-
Thanks, I received the files. I also requested for an additional piece of information from you.
Thanks. -
What else do you need? I thought you needed the header information only
-
Please try the updated patch from here:
ftp://support.red-gate.com/Patches/SQL_ ... 0_1002.zip
Thanks. -
That did the trick... Thanks
-
I ran into this problem back in September. I upgraded to version 6.3 and it appears that it cannot restore old SQL Backup files again. The patch I received for 6.2 worked, but seems like it was not included in version 6.3
-
-
I could not reproduce the error. I backed up a database using SQL Backup 3.2 with encryption and compression level 3, and successfully restored the database using SQL Backup 6.3.0.48.
Could you please send me a sample back up file that was created using 3.2, but cannot be restored using 6.3?
Thanks.
Add comment
Please sign in to leave a comment.
It's my understanding that you can restore a backup created with any version of SQL Backup with SQL Backup 6. We have some customers that are running an older version 3.0. And we cannot restore their data that is sent to us. This is the following error we are getting.
ERRORS AND WARNINGS
9/16/2009 10:05:53 AM: Error: Rijndael: Invalid key size - 0
This is how we're creating the backup:
-SQLBackupC -SQL "BACKUP DATABASE [dbase] TO DISK = 'C:\data_directory\dbase01.sqb', DISK = 'C:\data_directory\dbase02.sqb',DISK = 'C:\data_directory\dbase03.sqb',DISK = 'C:\data_directory\dbase04.sqb' WITH COMPRESSION = 3, PASSWORD = 'XXXXXXX', VERIFY"
and we are restoring with the following script
-SQL "RESTORE DATABASE [dbase] FROM DISK = 'D:\backup_directory\dbase01.sqb', DISK = 'D:\backup_directory\dbase02.sqb', DISK = 'D:\backup_directory\dbase03.sqb', DISK = 'D:\backup_directory\dbase04.sqb' WITH RECOVERY, MOVE 'dbase_Data' TO 'D:\dbase\dbase.MDF', MOVE 'dbase_Log' TO 'D:\dbase\dbase_log.LDF', REPLACE, PASSWORD = 'XXXXXXXXXX', MAILTO = 'email@dbase.com'" -E
Any suggestions would be great