Configuring database backups

As seen so far, OneOps has a complex architecture and relies on many databases to provide optimum functionality as we have seen before. Again as with deployment, for database backup, the steps needed to back up a single machine installation and an enterprise installation are different.

Backing up a standalone OneOps installation

For a standalone installation, the three main postgres databases you need to back up are activitidb, kloopzapp, and kloopzdb. You can access these databases directly by logging in to your OneOps server and then doing a sudo as the postgres user:

# sudo su - postgres
-bash-4.2$ psql
Postgres=# l

Once you issue these commands, you can see these databases listed along with the default postgres database. Now you can design chef recipes to take backups or installation puppet or ansible and automate the backup process. However, in accordance with the KISS principle, the simplest way you can set up backups is to use the built-in postgres command...