Hello,

Indeed spinning up a new Droplet from a backup sounds like a plan.

Regarding the database, I would recommend moving your Database to a separate Droplet or using DigitalOcean managed databases. That way your database would be external and your two Droplets would be connecting to the same database and you would not have to set up database replication. So it would be something like this:

Regarding the storage sync, you could do one of the following:

• Lsyncd: For similar setups, I’ve been using lsyncd and it works pretty well, you can take a look at this tutorial here on how to do that:

https://www.digitalocean.com/community/tutorials/how-to-mirror-local-and-remote-directories-on-a-vps-with-lsyncd

One problem that I’ve had in the past is that if there are too many files to be synced, you might start hitting some Kernel limits which could cause unexpected behavior.

• NFS: Another thing you could do is to use NFS and mount a shared directory on your second Droplet:

https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nfs-mount-on-ubuntu-18-04

Regards,
Bobby

Thanks @bobbyiliev , I had the impression this was a little harder than just dropping the droplets in the loadbalancer. I was expecting a little more of automation :)