The following context is the one I have received from SQL Server Magazine that talks about a good backup tool in the market, study on: 

Third-Party Tool Enhances SQL Server Backup and Recovery
Microsoft SQL Server’s own backup and restore facilities are probably some of the most robust in the industry. So why consider purchasing a third-party backup tool? The answer, according to William Brewer, a SQL Server developer who has worked as a database consultant and business analyst for financial services organizations in London, is that, good as they are, SQL Server’s native backup and restore features meet only part of the myriad requirements for effectively maintaining a live database application.

The best third-party backup tools offer the extra features you’ll need to implement a full backup strategy. The more demanding your application environment is, the more attractive these features are—backup compression and encryption, a means to monitor backup and restore activities, the capability to set up a transaction log shipping schedule, and more. Before you consider how a third-party backup solution can provide a strong backup strategy, it's important to know the ins and outs of effective database management.

Effective Database Management: More than “Just the Basics”
A robust, efficient, and visible backup routine is only one aspect of effective database management. The DBA must also monitor database performance, resource requirements, blocking, security, and integrity, and record all changes to ensure that the application is running effectively.

The database recovery plan must be just as strong, including every detail, such as the scripts and simple 'cookbook' instructions to rebuild the production server without errors if data is lost. After all, someone without DBA knowledge will likely perform the recovery in an emergency.

Most production applications come with several ancillary configuration items, such as files, logs, registry settings, and directory structures, which must be carefully noted and recovered. Recovery should be automated where possible and rehearsed after every revision of the production software.

Finally, a central console is no longer a luxury for today’s DBA, who is often responsible for monitoring backup, recovery, and data integrity for 80 or more database servers. Monitoring so many servers using Management Studio or Enterprise Manager without missing critical details is difficult and time-consuming. Simply to view the history of a backup job in Enterprise Manager takes 5 mouse clicks. Routinely scanning 80 servers means 400 mouse clicks!

Following are some essential components for a complete backup and recovery strategy, whether for 1, 10, or 80 or more databases:

  • Recovery Model. You’ll likely use a full recovery model for production databases that require “point in time” recovery, and a simple model for system databases that are backed up frequently.
  • Data Retention. Be sure to know the specifications of your service-level agreement for data retention. Know when you need to destroy personal information, and how long to retain financial information, for example.
  • Data Archiving. You’ll generally need to copy backups, often using secure FTP, to a secure offsite archive. Deleting data also means deleting it from all archives and the primary backup location.
  • Data Integrity Checking. Whether you want to perform a full backup of a database or restore the database onto another server, you must review the integrity of the data.
  • Backup and Archive Security. Be sure to encrypt backups that contain financial or personal information.
  • Scheduling. You must archive and “version” database alerts and jobs in the production system (such as maintenance tasks and routine aggregations).
  • Replication, Mirroring, and Clustering. If you have databases configured across several servers, these databases typically require synchronization and reconfiguration before recovery can be effective.
  • Source Control. If a release goes wrong, you might have to revert to a previous version of software, including such routines as functions or stored procedures, on a production server. You must also retain up-to-the-minute data, including source and static data, along with alerts, jobs, and events.
  • Backup of File-Based Data. It’s important to back up text-based logs, such as the application log or the security log—they might prove vital if you need to construct a complete audit trail.
  • Notifications and Alerts. Email alerts for backups with errors are often required, but alerts may also be important for notification of all backup activities.
  • Reporting. A report of the backup history is a standard requirement for reference or for management reporting.

The Strengths of a Third-Party Backup Strategy
One third-party backup solution, SQL Backup Pro, from Red Gate Software, is built on top of Microsoft SQL Server’s native backup and restore and uses only published interfaces with Microsoft SQL Server, in much the same way as tape storage does.

SQL Backup Pro provides additional features that offer support in many of the key areas of a comprehensive backup strategy, as outlined above. For example:

  • Data archiving—SQL Backup Pro produces typically 50% to 90% smaller backup files than with native SQL Server backups (saves disk space and means faster and more economical off-site backups).
  • Backup security—SQL Backup Pro supports 128-bit and 256-bit key Advanced Encryption Standard encryption, using the Rijndael cryptographic algorithm.
  • Backup and restore scheduling and monitoring—SQL Backup Pro provides a graphical ‘timeline’ for a fast overview of completed backup and restore activities, and jobs scheduled; the timeline also displays failed activities and potential scheduling conflicts.
  • Remote SQL Server/SQL Server cluster database backup—Supported by SQL Backup Pro.

Such features and facilities offer a powerful and intuitive system at the ‘coalface’ level for backing up and restoring databases. SQL Backup Pro simplifies implementing your database maintenance plan, reduces the time and money you spend on backups, and increases your confidence that data security will not be compromised.

To read the complete technical paper by William Brewer that discusses the remaining components of effective database management and explains in depth how you might use SQL Backup Pro for a comprehensive backup and recovery strategy across your enterprise, click here.