We all know that there’s already said and written a lot about backups, so there is no need to reinvent the wheel, just take it and do what you need to do. However, every time the system administrator faces the task of setting up backups, for many of them it hangs in the air as a big question mark. How do I properly backup my data? Where do I store backups? How to unify the backup process for a whole zoo of different software?

We solve a lot of problems with nxs-backup. There’s an ease of initial configuration with an ability to expand functionality through custom scripts. Backups can be performed not only for a specified period of time, but also taking into account the maintenance of a specific number of backups.

We just released a new 3.7.0 version and a such useful feature as integration with monitoring to get application metrics and job statuses in Prometheus compatible format. Because it's not enough to just do backups, you need to monitor that they are being done and that something can be recovered from them.

Previously it was only possible to send out log events via hooks with different levels configured and get information about errors or events of the right levels. The following metrics have been added in the new version: Backup file size; Correctness of backup acquisition; Backup acquisition time; Backup delivery correctness; Backup delivery time; Availability of a new version.

To differentiate metrics, nxs-backup identity such labels as project, server and others that you can check in the documentation.

We’re looking forward to improving our tool so we’d love to see any feedback, contributions, or report any issues you encounter!

Please join our chat in telegram: https://t.me/nxs_backup where you can discuss something about nxs-backup and ask any questions in the chat: https://t.me/nxs_backup_chat