Thank you for your reply.
I will submit a feature request for us to consider seeking SAP certification.
The following link is to user testimonials we have published on our web site:
http://www.red-gate.com/products/SQL_Ba ... onials.htm
To help you understand how Red Gate SQL Backup performs a backup, I have added some simple notes to explain the similarities between a backup performed by native SQL Server backup and one performed by Red Gate SQL Backup:
1. SQL Backup makes use of the SQL Server Virtual Device Interface(VDI), that Microsoft supply for third party backup / restore software to communicate with SQL Server.
2. When you perform a backup using native SQL Server, you issue a T-SQL BACKUP command to SQL Server, with the relevant options set.
SQL Server then generates the relevant backup data and writes them out to disk or tape.
3. When you perform a backup using SQL Backup, SQL Backup issues a T-SQL BACKUP command to SQL Server, with the relevant options. The command is almost similar to that used when using native SQL Server backup. One difference is that instead of the DISK option, SQL Backup uses the VIRTUAL_DEVICE option e.g.
BACKUP DATABASE pubs TO VIRTUAL_DEVICE = '<some unique value>' WITH DIFFERENTIAL
4. SQL Server then generates the relevant backup data, but does not write it out to disk or tape. Instead, it informs SQL Backup where the backup data can be found. SQL Backup then compresses this data, optionally encrypts it, and writes it out to disk.
5. The backup data is generated by SQL Server in all cases. SQL Backup does not generate any backup data.
6. The backup data that is generated by SQL Server is identical in both the above cases.
7. Because the backup data is identical, you can perform the same tasks using SQL Backup as you would using native SQL Server backups e.g.
a. Perform full, differential, transaction log, partial, filegroup backups and restores, STOPAT, PAGE restores etc, as long as SQL Backup supports the required SQL Server option.
b. Run RESTORE VERIFYONLY, RESTORE HEADERONLY, RESTORE FILELISTONLY commands.
c. Backup a SQL Server 2000 database and restore the database on a SQL Server 2005 instance.
You can download and evaluate a full working copy SQL Backup Professional Edition for 14 days, to see if it is suitable for your needs. If required we can extend this evaluation period.
As per my previous reply, if you do decide to evaluate SQL Backup, I recommend that you evaluate SQL Backup in a test environment.