Idera treats a backup of a SQL Server as if it is essentially a single backup job of each individual database. You can't see any metrics about how long it took you to backup the entire server. It doesn't handle restoration to different drives very easily, and it won't create folder structures if they don't exist already. It cannot be used to implement replication on another instance without first converting files back into SQL Server .bak files. There appears to be LOTs of shortcomings. [All of these short-comings are still very much present even after 6 months of feedback to Idera. No solution is in sight.] Still has a focus on individual databases and not for entire server recoveries. Have tried adjusting max threads values, but it seems to have little affect and Idera is still researching the issue.
