Backup Strategy

To Be Addressed

Find out where else work that needs to be preserved is stored - this includes code (github), db state, config, etc. Rather than backing up a whole server and all configuration details, using standard Linux Configuration Management tooling provides a way to back up the configuration ahead of time, so new infrastructure can be built in a repeatable manner. Making platform components stateless makes it more apparent what needs to be backed up.

3-2-1 backup strategy - 3 total copies of data, 2 of which are local but on different devices, and at least 1 copy offsite.

For a database, this can be idealized by having a replica written by your primary db, a periodic database dump, and a copy of this dump to another provider’s object storage.

The DO droplet is not an inherently fault-tolerant machine - hypervisor outages - occasional data losses happen.

Account Admin Access:

How do we keep one person from controlling critical elements? (Domains, Digital Ocean Counsel, Google Play) Ideally, nothing should be controlled by a single user rather GreenStand's board of directors should maintain control

Create a separate organizational account and transfer domain name ownership to the organization?

Backup Status:

treetracker.org - 188.166.33.48 (Digital Ocean droplet) DO backup ON dev.treetracker.org - 178.62.253.53 (Digital Ocean droplet) DO backup ON treetracker-api-dev - 45.55.4.155 (Digital Ocean droplets) DO backup ON

Github.com/greenstand: Not backed up