Steve Jones - SSC Editor - Wednesday, November 22, 2017 4:36 PM
SQL Server native backups (yes... I'm using 2016 Enterprise Edition and not everyone has the Enterprise Edition) does a fine job of using compressed backups and restores even to NAS if you have a good "pipe". It's part of how I've been able to backup 2TB of databases in a single threaded fashion in just a couple of minutes over an hour.
I also agree that SQL Backup is a fine product and can easily be setup and instances added back. However, as with all such centrally controlled backups, if the box that the backups are on goes down, there is a time lag between that event and the time you can get a new instance online unless you have a hot standby ready and waiting (and a lot of people don't) capable of doing an automatic flop. During that time and depending on the system resources, the databases involved, and the type of traffic the databases are exposed to, you can have several log file explosions in the time it takes to get your centralized backups working again. If no log files explode, you may certainly have to go back to many of the systems to resize the log files back to "normal" because rebuilding the log file during a restore, even in the presence of instant file initialization, is a very expensive part of doing any restore.
It would be interesting to do a head-to-head race of tuned native compressed backups with RG SQL Backup for marketing purposes. Has RedGate done such a test and published such results somewhere?
--Jeff Moden
Change is inevitable... Change for the better is not.