We've tried CommVault SQL Server agent backups, but decided to go back to the SQL Server native backups which backed up later as .bak files using CommVault.

The main reason was that it's too hard to build disaster recovery strategy with CommVault backups. Other reasons:

- backups don't start at the same time (with CommVault backup model that our backup guys provided backup could start at 9 PM or 3 AM next day)

- possibility of human error when restored by non-DBA (as in last Indianrock's post)

- possibility of extra backup that can break recovery strategy when differential backups used

- additional CommVault licenses on all servers where database restore required

- we didn't have enough people trained well on CommVault, so if primary backup person wasn't available it was not easy for other guys to restore the database, so we ended up with granting most of the permissions on CommVault to DBA (on Database servers group)

- also, I didn't get good answer from our backup guys on my question: "What if CommVault server will fail? How long will it take you to recover/rebuild it?".