Brian-444611 wrote: Grant Fritchey wrote: Jeff Moden wrote:
Along with what Grant has stated and since they said it did "regular" SQL Backups, have them do a test restore using native tools only to prove it's a regular backup.
Also ask to see the plan for doing test restores of different databases on a regular basis as well as the DR Test Plan where they pretend the build the prod box is in was wiped off the face of the Earth, all replication had failed, and you need to stand up the DR Test site only from backups.
Yes to all this.
There should never be a fight as to what backup tool to use. It's all about meeting the restore and recovery requirements. Period. If they can. Great. If they can't. No, we're not using that.
Absolutely positively wrong. Another statement made by someone who probably has never run anything highly transactional with more than a 2 9s uptime requirement. Choosing the wrong backup solution can have performance impacts as my previous post just mentioned. There are about 50 other reasons why your statement is completely wrong as well all from performance perspectives of VLDBs.
I saw your rant - and while there can be issues with some of these, there are some that can work very well. The concern you have about backing up 'empty' space is not true for all solutions.
Using VSS allows for the freezing/thawing of SQL Server - which is supported by SQL Server and built into VSS. In fact, utilities that do not utilize a freeze/thaw method also utilize the VSS to perform 'native' backups under the covers. Redgates SQL Backup is one of those - as well as Quest Litespeed.
IBM has a product called SPP (Spectrum Protect Plus) - that uses VSS to freeze the database, snap, unfreeze - then performs a delta on that snapshot with the previous snapshot and creates a differential. That data is then deduped (if possible) and replicated to offsite storage with no impact on your production system. The only data included is allocated and used data in the data file(s) - empty space is removed.
As has been stated - work with the server/storage team to test and validate the proposed solution. If that solution can meet the businesses RPO/RTO requirements - and can prove it with a restore, then it is a valid solution and should be considered. If the solution cannot meet your RPO/RTO requirements then it doesn't matter how it works - it is not a valid solution for your environment.
And yes - I have managed several VLDB OLTP systems (10TB+) and have used native backups, Litespeed, Netapp SAN backups, IBM SPP and others quite successfully.