Finalizing SQL Backup Assessment (Part 3)
After testing HyperBac yesterday in our SQL Backup tools series throughout this week, we realized that SQL Backup Pro is the way to go. The HyperBac compressed backups were not smaller than either SQL Server native compression or SQL Backup Pro. However, all three integrated well with our Ola Hallengren maintenance scripts. We also decided to do one native backup a week for disaster recovery purposes in case we cannot get the tool to work following a disaster. With a proprietary tool, my manager felt better in a DR scenario having at least one native backup, so ‘we gotta do what we gotta do’ to keep everyone happy.
I have recommended to Red Gate that they add more automation into the scheduling of Virtual Restore jobs to grab all of the databases in the job instead of individual jobs for each database. That I think is the only area I found to be lacking in the tool.
Enjoy your weekend.
Posted on December 7, 2012, in Maintenance and tagged Backup and Recovery, Maintenance. Bookmark the permalink. 2 Comments.
So are you recommending to your company to purchase Red Gate Backup? What is your reasoning, if so?
Personally, we were using Red Gate Backup until recently, but mostly for compression. After review, we have reverted to using all natives since we’re now almost completely on SQL 2008 R2 and can make use of native compression, which compresses about as much as Red Gate’s default settings. There wasn’t much of a value add for us from Red Gate’s tool.
Ours was about the same until we cranked up the compression and then we saw a considerable difference. Thanks Mike, how ya been?
On Fri, Dec 7, 2012 at 12:19 PM, SQL Swampland