cBackup [siː ˈbækʌp] is network equipment configuration backup tool. It consists of two quasi-independent modules: web interface (core) and system service (daemon). We recommend running them both within a single appliance, but if you like, you can split them into separate shards. It's not required for Java daemon to be located in the same environment as web core - they are communicating via RESTful API and therefore can be separated from each other if really necessary.
Backup and version control
You can schedule backup process for equipment configuration, retrieving it by user-defined schedules. Also with its help you can track changes in text configurations which can be crucial for troubleshooting and disaster recovery processes, lowering possible downtime.
Customization and flexibility
We created highly customizable tool for network and system administrators. With cBackup you will be able to schedule and execute any custom tasks you need. If you can describe your task via CLI script and/or SNMP command sequence - you can schedule it in cBackup.
Transparency and reliability
We're system administrators and we do understand the importance of securing our configurations. Therefore cBackup works as standalone appliance, allowing you to take control of all data. Our development process is transparent and all code and translations are available open source.
Can I use cBackup on Windows?
We don't provide official support for cBackup on Windows yet. However, we consider Windows compatibility within our development process. Currently it is possible to use cBackup on Windows, but do it at your own and sole discretion. Official Windows support is on our roadmap but it's not our top priority at this moment.
Can I use Nginx instead of Apache?
Yes, you can. At this moment we don't provide RPM/DEB packages for Nginx, but you can use Nginx + PHP-FPM installing cBackup from .tar.gz source following instructions in the official documentation. It doesn't use SEF/mod_rewrite so it's pretty easy to run cBackup on Nginx.
Why PHP7? I have older version.
All our software and libraries are released with PHP 7.0 or newer support for a score of reasons. Except for performance, we are certain that outdated PHP versions hold back the progress and to a large extent, that legacy software and interpreter's versions are main reasons that PHP has such a disrepute in web developer's community.
PHP sucks
We are convinced that in every programming language it's possible to write garbage code or to create scalable, well-built and mission-related software. Programming language should meet certain requirements and the code has to be written as if the next maintainer is prone to sadism, has anger management issues and knows where do you live.
