Comments
Sort by recent activity
Gary,
All SQL Backup scheduled jobs should be retained even after an uninstall so this should not cause you too many problems.
If you have settings and templates you wish to preserve you can save the following in the registry :
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\<instance name>
HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<instance name>
I hope this helps. / comments
Gary,
All SQL Backup scheduled jobs should be retained even after an uninstall so this should not cause you too many problems.
If you have settings and templates you wish to preserve you can save t...
Hi Gary,
Are you encountering this error when trying to update the GUI or the Server Components?
If you uninstall and reinstall rather than doing an upgrade does it work?
Thanks / comments
Hi Gary,
Are you encountering this error when trying to update the GUI or the Server Components?
If you uninstall and reinstall rather than doing an upgrade does it work?
Thanks
Giggles220,
Have you deleted the client side cache in C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\SQL Backup\Server Data or is it still on your system?
If you have not deleted it would you be able to send it to support@red-gate.com quoting the reference above?
Andrew,
If you run into this again could you also do the same?
Thanks guys! / comments
Giggles220,
Have you deleted the client side cache in C:\Documents and Settings\<user name>\Local Settings\Application Data\Red Gate\SQL Backup\Server Data or is it still on your system?
If you hav...
Andrew,
If you could e-mail your screenshots etc to support@red-gate.com quoting reference F0014822 that would be useful.
Thanks! / comments
Andrew,
If you could e-mail your screenshots etc to support@red-gate.com quoting reference F0014822 that would be useful.
Thanks!
Hi,
This behaviour sounds extremely strange and I haven't encountered it before.
Was it just the one file that came up with this error or is it a regular occurrence?
Thanks / comments
Hi,
This behaviour sounds extremely strange and I haven't encountered it before.
Was it just the one file that came up with this error or is it a regular occurrence?
Thanks
Hi Cameron,
It looks like you are indeed bumping into a bug with the SQL Backup 5 GUI.
This generally occurs with large databases when the WITH VERIFY option is used.
Your database backup should have completed and verified successfully, you can check this by looking at the related SQL Backup log file located by default in :
%:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>
Closing and opening the GUI should return the timeline and In progress tab to normal.
Thanks / comments
Hi Cameron,
It looks like you are indeed bumping into a bug with the SQL Backup 5 GUI.
This generally occurs with large databases when the WITH VERIFY option is used.
Your database backup should ha...
If SQL Backup is asked to restore multiple files using a wildcard it uses the LSN information from the backup file header to put the backup files in the correct order for restoration.
If the LSN information can not be read, the files can not be put into the correct order and so the restore process fails.
Are no error messages recorded in the backup log files pertaining to writing LSN information?
What are the results of the following when run against the backup files which aren't being ordered correctly? EXECUTE MASTER..sqlbackup N'-SQL "RESTORE HEADERONLY FROM DISK = ''C:\Backups\LOG_Northwind.sqb''"'
EXECUTE MASTER..sqlbackup N'-SQL "RESTORE SQBHEADERONLY FROM DISK = ''C:\Backups\LOG_Northwind.sqb''"'
/ comments
If SQL Backup is asked to restore multiple files using a wildcard it uses the LSN information from the backup file header to put the backup files in the correct order for restoration.
If the LSN in...
Thank you for the info.
There is no fix for this in SQL Backup 5.4.
Unfortunately it doesn't matter if we were to sort the files by the first or last LSN, in this scenario an error would be thrown either way.
I have raised a bug/feature request for this so if two files are found with the same Last LSN, the first LSNs are also checked.
To workaround this at the moment you would have to restore each file individually.
Thank you for bringing this to our attention. / comments
Thank you for the info.
There is no fix for this in SQL Backup 5.4.
Unfortunately it doesn't matter if we were to sort the files by the first or last LSN, in this scenario an error would be thrown ...
Hi DonMan,
The issue which was fixed in SQL Backup 5.3 was the following :
Warning: System error 87 (The parameter is incorrect)
Are you encountering this in your backups using the 5.3 Server Components? If so could you please paste the log file.
If it was just your LSNs being out of sync for the restore, were there any messages regarding reading the Header/LSN information and this failing?
Thanks, / comments
Hi DonMan,
The issue which was fixed in SQL Backup 5.3 was the following :
Warning: System error 87 (The parameter is incorrect)
Are you encountering this in your backups using the 5.3 Server Compo...
Do you have the SQL Backup log files for the backup jobs on each of these files?
It looks like the LSN information isn't being written at the time of backup, the log files for the backup job should hold more information. / comments
Do you have the SQL Backup log files for the backup jobs on each of these files?
It looks like the LSN information isn't being written at the time of backup, the log files for the backup job should...