I know that I can use regular disk backups to protect against loss of data from hardware failure. My question is not about safety of the data, but being able to keep the forum alive when there is a hardware or datacenter issue.
If you are going down the entirely AWS route Amazon Elastic File System (EFS) is probably what you are after for storage, available across multiple Availability Zones (AZs) connected to multiple instances at the same time…
If you check out this map you can see that most / if not all AZs are in different data centres within the same region.
Yes, mounting the filesystem as an extra drive in Linux is fine. But discourse is hosted on the instance’s primary drive and naturally keeps user uploads there. I would need to tell it to keep the user uploads on the EFS drive, a non standard setting. Do you know how to do that?
Am i making the question clearer or proving i don’t understand!?
Drives are not mounted as drives - you are thinking of Windows…
You mount to a folder say /my-lovely-new-storage or /my/usr/home/complicated/path etc - you probably need to do a bit more reading up on mounting file systems in *nix environments.
In addition to this symlinks come in handy read up on those too.
Great! That’s the second thing i learned from you today
But… Still need to tell discourse to store the files there… Discourse itself cannot be installed on the EFS drive and run by several machines simultaneously, can it?
I think from what you have said you have a little mountain of a learning curve to join all the components together.
All I can say is: get your AWS calculator out and make sure it makes sense - the Official Discourse Hosting might be a better bet - once you factor in the cost of your time.