The Status of Your Backups with Backup Ninja

The Status of Your Backups with Backup Ninja

Profile picture for user LukasVileikis
Lukas Vileikis
10 June 2021


Monitoring the status of database backups is a near-daily task of almost every database administrator or even a developer. In this blog post we will figure out why the monitoring of the status of your backups is so important.

Why Backup and Why is it Important to Monitor Backup Status?

Before actually telling you how you should monitor the status of your database backups, we should probably tell you why you should backup your data in the first place. Backing up your data is a proven and tested way to make sure that your data is always at hand and can be recovered in case any kind of disaster comes your way. Disasters can range from natural causes (e.g floods or fires) to human-related issues, say, theft, power outages or other things. Backing up your data helps you ensure that you have an option in the event of primary data failure.

Monitoring the status of your database backups, however, is also important because if you don’t know whether your backups were successful or not, you will be next in line for trouble the next time you want to recover your data - monitoring the status of database backups should be a part of your data backup and recovery strategy whatever happens. We will now look into how that can be accomplished using Backup Ninja.

Monitoring Backups with Backup Ninja

Backup Ninja can be your reliable partner in your backup journey. Backup Ninja can not only help you back up your MySQL, PostgreSQL, MariaDB, MongoDB, Percona and TimescaleDB data, but also help monitor the status of your database backups. To do that, simply log in to your Backup Ninja account, then click Schedules in the left pane:


In this part of Backup Ninja you will be able to see the schedules of your backups and also monitor their statuses. To monitor them, click View. Here’s what you will see:

MongoDB BackupsMongoDB Backups

As you can see, Backup Ninja provides you with a bunch of useful information including the backup type (backups can either be partial or full), the backup method (in this case, mongodump was used), when the backup schedule was last executed too. You can also see whether the backup is encrypted or compressed, what name template it has, on what server did it run and when it is scheduled to run the next time. Knowing these things should make your backup monitoring journey way smoother - the hassle is now taken off your hands.

With that being said, keep in mind that schedules can also be edited - if you wish, you can edit the schedule name, the backup method, you can select a different server to perform the backup on, switch the backup type from full to partial or vice versa.

Editing a Schedule with Backup Ninja

If you want to, you can select a different storage location to store backups in, you can even rename them, make them use compression or encryption if you so desire!

Backup Ninja Schedules


Monitoring the status of your backups is a near-daily task of almost every developer or a database administrator. When monitoring your backups, it’s important to keep in mind that your backups should be easily recoverable, and if desired, easily modified too - modification in this case means that you should have the option of renaming the backups, making them use compression or encryption, store them in different locations etc. - Backup Ninja allows you to do all of those things, at ease. Give Backup Ninja a try today or if you’re still not sure, have a look through the documentation - that should help.