# Databases how-to guides

Source: https://docs.quake.ai/docs/databases/how-to
Markdown: https://docs.quake.ai/docs/databases/how-to.md
> Procedures for deploying, connecting to, backing up, restoring, and branching PostgreSQL and MySQL/MariaDB databases on Quake AI.

---

# Databases how-to guides

Procedures for running a relational engine on Compute and Block Storage.

<DocsSectionLinks section="databases/how-to" />

## Deploy a database

- [Deploy the self-managed PostgreSQL template with OpenTofu](/resources/deployments/deploy-self-managed-postgres-template)
- [Deploy the MySQL/MariaDB database template with OpenTofu](/resources/deployments/deploy-mysql-database-template)
- [Self-Managed PostgreSQL template reference](/resources/iac-templates/self-managed-postgres)
- [MySQL/MariaDB Database template reference](/resources/iac-templates/mysql-database)

## Operate PostgreSQL

- [How to restore PostgreSQL from a self-managed-postgres backup](/docs/automation/how-to/restore-postgres-from-backup)
- [How to emulate a branchable Postgres workflow](/docs/automation/how-to/branchable-postgres-workflow)

## Supporting procedures

The instance, volume, and network operations a database depends on live with their own services: [Compute how-to guides](/docs/compute/how-to) for instance lifecycle and Docker Compose, [Block storage how-to guides](/docs/block/how-to) for volume snapshots and capacity, and [Network how-to guides](/docs/network/how-to) for security group rules and bastion access. To copy dumps off the database volume, see [Back up to Quake AI object storage](/docs/object/migration/backup-to-quake-ai).