Posts
Sort by recent activity
6.4 Upgrade Registry Surprise
It appears that with version 6.4 the registry location for 64 Bit machines was moved from "HKLM\SOFTWARE\Wow6432Node\Red Gate\SQL Backup" to "HKLM\SOFTWARE\Red Gate\SQL Backup". While most of the...
Assertion failure
Red Gate Support -- at this point this is just an FYI more than a problem.ERROR - full backup [multiple databases] on ServerName\InstancName at 1/6/2010 12:14:29 AM
SQL Backup log file 6.3.0.48
-SQ...
Warning 445: Breaks Log Shipping Resiliency
I had a CopyTo failure in log shipping that required manual intervention. I was able to track down the issue from the log indicating that at that specific time it failed to write the entry into th...
Version 6.2 Minor Bug Fixes?
Latest version 6.2.0.134
Released 8/11/2009
SQL Backup 6.2 is a minor upgrade, introducing object level recovery for SQL Backup (.sqb) backups. This is useful if you want to recover individual da...
Trying to reinstall SQB v5 after testing SQB v6 pre-release
I have reinstalled SQL Backup v5 on our Development server but I can't seem to get the license to reactivate. I get the following error:
Activate License - Failed
=========================
Process...
Two issues introduced in 6.x release
ISSUE #1
I am getting a lot of CE Database corruption errors that I didn't get in the previous release from multiple instances on our development PolyServe matrix.
6/24/2009 1:45:03 PM:
6/24/2009 1...
GUI performance with 6.0
I am dissappointed 6.0 still wants to pull server data down to local cache. I just started playing with it an hour ago. And it is still trying to bring down server data to local cache. That's wi...
Log Shipping MOVETO failures
Occasionally I run into an issue where a log shipping file gets restored and then recopied into a the destination directory. When this happens, a subsequent restore fails because the .sqb file alr...
Deadlock Breaks Log Shipping
When the full backup and the transaction log backup run at the same time, I sometimes get the following error:
SQL error 3014: SQL error 3014: BACKUP LOG successfully processed 1 pages in 0.019 sec...
The SQL Backup 5 GUI is a Resource Hog
It seems that whenever I open the GUI it takes a long time to syschronize all registered SQL Server instances before it becomes usable. The more instances I add, the worse the problem gets.
It see...