The authentication templating, allowing one record of users/passwords. When the passwords for devices are rolled over for security reasons, there is only a single location for updating these passwords within Backbox.
Backbox supports a large number of products that are being run. Not only the Cisco networking equipment, but Check Point firewalls, Cisco Firewalls, FortiGate firewalls, and Cisco Unified Communication software such as Call Manager and UCCE.
The ability to view the backups, meaning that you can pull specific lines of configuration out of an old backup, and use that to revert configuration that has changed, or alternatively as a base template for either replacement or additional devices.
The Backup retention is a useful feature that allows a larger amount of granularity when reverting config changes - If the config has changed a while ago, and only just been picked up, the solution allows us to revert to an older copy, before the config change was made.
The scheduling allows tiers of devices to be backed up on different schedules.
Although the Interface was originally clunky, in the older versions, the interface in the newer versions is much more usable.
Some products require pushing backups to BackBox, as opposed to BackBox pulling the backup from the appliance, meaning that it relies on the backup configuration of the appliance itself. This works against the idea of having backup configurations in a single location, and means that you have to ensure that all the appliances are configured correctly. When appliances are replaced, the backup settings on the new appliances have to be configured.
Backups of networking infrastructure, including Cisco switches (both Catalyst and Nexus ranges), Cisco ASA appliances, FortiNet FortiGate appliances, Check Point appliances and open servers, Cisco Unified Communciation software such as CallManager and UCCE for Call Centers.