How a database backup runs
Add it to a policy under More options, Database backup, and choose all databases or only some.
Satkosh checks there is room on the disk for the dump.
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.
It checks each dump is complete, in a folder only root or SYSTEM can read.
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