Evaluate MX and DB storage persistence

[katefike]

DONE WHEN

• Done when we know what work is necessary to redundantly backup storage for the MX and DB.
• Another important aspects of backups is knowing that you can actually utilize them and recreate prod in a pickle. Storage persistence goes hand-in-hand with CD and B/G Deployments.

WORK NEEDED

• Ensure named volumes persist after containers are removed and rebuilt.

  • Create a docker volume for the mx container #28

• Create Backup Jobs

  • Create a DO droplet backup job #123
  • Create a DB backup job using pgbackrest #122
  • https://community.commvault.com/self-hosted-q-a-2/postgresql-block-level-backup-snap-without-log-backup-6669

• Blue/Green Deployments

  • Create a CD workflow #72
  • Do B/G deployments #124