Satkosh

Calls: Monday to Saturday, 9 AM to 7 PM IST

Book a demo
Documentation

Database backups

Copying a database's files while it is running does not give a usable backup. So for MySQL, MariaDB and PostgreSQL, on Linux and Windows servers, Satkosh asks the database itself for a consistent copy at each backup.

Last updated 7 November 2026

How a database backup runs

Add it to a policy under More options, Database backup, and choose all databases or only some.

  1. Satkosh checks there is room on the disk for the dump.

  2. It dumps each database to a file of its own, plus the users and their permissions or the roles. People keep working: InnoDB and PostgreSQL tables are dumped in one consistent read. Tables without transactions, such as MyISAM, are locked while their database is dumped.

  3. It checks each dump is complete, in a folder only root or SYSTEM can read.

  4. It backs the dumps up with the policy's folders, then deletes them from the server.

Logins, checks and failures

  • Satkosh never stores a database password. The login stays on the server, in a file only root or administrators can read
  • In the policy, each server shows a tick when Satkosh can log in to its database, and a cross naming the problem when it cannot
  • If one database cannot be backed up, the folders and the other databases still are. The backup is marked failed, naming the database and the reason, and you get an alert

Restoring a database