A manufacturer of a high-end switch was looking for a management system that would meet the needs of a large data center, specifically - scalability, fault tolerance, and high availability. During their evaluation process, they
observed that NetMan not only offered a very comprehensive and complete set of management features but it was also highly fault tolerant since it had a very reliable and efficient disaster recovery engine that was able to backup all
its user configuration and inventory data.
One of the key features that impressed them was the way the NetMan backup engine was designed. It was designed and built so that it is able to efficiently capitalize on the built-in tools that are available in most common databases.
By using these tools, the NetMan backup engine can save significant amount of time during each backup cycle without missing any critical data. In addition, it was designed so that when the core NetMan information was backed up, it also
automatically backed up the "customization" that was performed to the NetMan technology as well. This in turn saves quite a bit of time for the customization team.
NetMan's backup component uses an efficient transaction locking mechanism, which when backing up ensures that the backup doesn't have any partially filled tables. It also allows performing of backups on the fly i.e. allows users to
request for backups in an adhoc manner (whenever they perform an unplanned activity). Once a backup is taken, NetMan automatically transfers the file to the configured file-server which speeds up the recovery after a disaster.
The other key highlight of the NetMan's backup component is its efficiency in managing the backup files i.e. the NetMan backup component doesn't just stop at backing up the files, it also manages the backup files. For example, users
can configure the backup component to maintain only the last "n" backup files in the file-server. Based on the configuration, NetMan backup component automatically clears old backups as and when new backups are created. This option
saves a lot of time for the network administrator since they do not have to worry about the growing disk-usage in the file-server and also helps them avoid periodic manual cleaning up of backup files.