Comments
Sort by recent activity
When the SQL Backup UI downloads the activity history from the SQL servers that are being backed up, it caches this in a SQL Lite database.
This is stored in C:\Users\[username]\AppData\Local\Red Gate\SQL Backup\Server Data\1.dat
I’ve used tools like Database .NET ( http://fishcodelib.com/Database.htm - disclaimer: nothing to do with us) to query this. The activityhistory table has the data that’s likely to be of interest.
Please note that this database schema is not a managed schema, and whilst it’s unlikely that it’ll change we can’t commit to not making changes that might break any custom integration done against them.
Best regards,
Colin. / comments
When the SQL Backup UI downloads the activity history from the SQL servers that are being backed up, it caches this in a SQL Lite database.
This is stored in C:\Users\[username]\AppData\Local\Red G...
Hi PDinCA,
Sorry for the delay, I can confirm that we understand the scenario you've described. I'm currently working on SQL Backup planning, and this is on my list of things to be looked into.
Best regards,
Colin. / comments
Hi PDinCA,
Sorry for the delay, I can confirm that we understand the scenario you've described. I'm currently working on SQL Backup planning, and this is on my list of things to be looked into.
Be...
Hi,
We have a v7.7 release of SQL Backup Pro in testing, which will include a fix for the SQBConverterGUI problem.
Thanks,
Colin. / comments
Hi,
We have a v7.7 release of SQL Backup Pro in testing, which will include a fix for the SQBConverterGUI problem.
Thanks,
Colin.
FYI, SQL Backup Pro v7.7 provides some improved support for AlwaysOn Availability Groups, as documented at http://documentation.red-gate.com/display/SBU7/AlwaysOn+Availability+Groups. Thanks - Colin. / comments
FYI, SQL Backup Pro v7.7 provides some improved support for AlwaysOn Availability Groups, as documented at http://documentation.red-gate.com/display/SBU7/AlwaysOn+Availability+Groups. Thanks - Colin.
RichardRayJH wrote:
...
Now, let me complicate things a bit. I do a similar thing to restore backups to a test server once a week to run DBCC CHECKDB on them and get another level of certainty as to the goodness of the backups.
Richard, just FYI, SQL Backup v7.0 supports integrated DBCC CHECKDB, meaning that the SQL Backup engine will run the command post-restore, and include the results in its output / email notifications. The beta version of v7.0 is currently available at http://www.red-gate.com/products/dba/sql-backup/version-7/version-7-beta.
Best regards,
Colin. / comments
RichardRayJH wrote:
...
Now, let me complicate things a bit. I do a similar thing to restore backups to a test server once a week to run DBCC CHECKDB on them and get another level of certainty a...
epetro wrote:
Step 1 would be simple if we were not using the <auto> variable.
There's some syntax in the SQL Backup engine which might help you here -- it allows you to do a RESTORE LATEST_FULL, to select the most recent full backup (there are other RESTORE_ keywords as well). Have a look here for more details.
In addition, SQL Backup v7.0 introduces further functionality to help in the area of backup verification. You can get a sneak preview via our Early Access Program, at http://www.red-gate.com/products/dba/sql-backup/eap-v7. If you try out v7.0, please let us know your feedback (there are links in the UI to our EAP feedback site).
Best regards,
Colin. / comments
epetro wrote:
Step 1 would be simple if we were not using the <auto> variable.
There's some syntax in the SQL Backup engine which might help you here -- it allows you to do a RESTORE LATEST_FUL...
Hi,
Yes, we're aware of this issue with the UI, and will obviously address this. Note that during the work to release v6.5, we tested the engine against the then-current CTP of "Denali", and it worked fine. So this is a UI issue, not an engine issue.
Best regards,
Colin. / comments
Hi,
Yes, we're aware of this issue with the UI, and will obviously address this. Note that during the work to release v6.5, we tested the engine against the then-current CTP of "Denali", and it wo...
Hi paule123,
The information in the requirements section of the product pages is out of date -- I'm sorry about this, and I'll try to get this remedied as soon as possible. SQL Virtual Restore v2.2 was released recently, with support for encrypted backup files created with SQL Backup v6.0 and above. There's further information on this in the product documentation (for eg, see here).
Best regards,
Colin. / comments
Hi paule123,
The information in the requirements section of the product pages is out of date -- I'm sorry about this, and I'll try to get this remedied as soon as possible. SQL Virtual Restore v2....
Hi paule123,
You could also consider using SQL Virtual Restore. This would allow you to do full backup verification (eg, including a DBCC CHECKDB), without taking up the disk space of a full restore, and in much less time. This can be scripted using native T-SQL syntax - for eg, you can do a virtual restore, run DBCC CHECK DB, and then drop the database. There's a UI 'wizard' included in the latest release that will help you construct the T-SQL syntax for this, that could then be used in a script.
Hope this helps,
Colin. / comments
Hi paule123,
You could also consider using SQL Virtual Restore. This would allow you to do full backup verification (eg, including a DBCC CHECKDB), without taking up the disk space of a full resto...
Hi,
I can confirm we’re currently working on adding support for encrypted SQL Backup files to SQL Virtual Restore; so SQL Virtual Restore will work with any backup made with SQL Backup v6, as well as backups made with SQL HyperBac, and native SQL Server (compressed or uncompressed).
In addition to the comparison page that petey referenced above, there’s a more details list of functional differences here.
Hope this helps.
Colin. / comments
Hi,
I can confirm we’re currently working on adding support for encrypted SQL Backup files to SQL Virtual Restore; so SQL Virtual Restore will work with any backup made with SQL Backup v6, as wel...