Backup Server

Sulli86

I am looking to run a backup server behind my firewall at home as I don't really want to have to pay another infrastructure provider to run backups (the storage requirements vs resources)

Has anyone gotten this working, either by using an overlay network (tail scale or similar) or just allowing through ports on their firewall? Or is it a requirement that all ports are open between servers?

xyzulu

No issues at all.
At this time enhance requires IPv4 ( soon to support IPv6 only) so you will need to open all ports to your other servers in your cluster. This isn’t hard with firewall rules at a network level.

rallisf1

I'm doing exactly that over tailscale. HOWTO:

In any new servers (including the backup server) make sure to connect to tailscale and add the "100..." range IPs of your other servers in its /etc/hosts, BEFORE installing enhance
In the backup server make sure to add the hard drive needed for backups BEFORE installing enhance
In your existing enhance servers connect to tailscale and add the "100..." range IPs of your other servers in its /etc/hosts. Then you either need to recreate the docker containers or (safer way) edit the /etc/hosts of the orchd containers. Since the container doesn't contain even vi your only option is to append >> to the file.

Known bugs:

Servers show the tailscale IP in the dashboard instead of the public
If you use the DNS role, creating or transfering websites might screw up their dns records and need manual editing afterwards (due to 1).

Sulli86

OK, I've set up an AWS instance for now, but... Is there a way that I can add the backup roll to all websites without moving the other services to default? Or does default mean just leaving it where it is?

Adam

Sulli86 OK, I've set up an AWS instance for now, but... Is there a way that I can add the backup roll to all websites without moving the other services to default? Or does default mean just leaving it where it is?

Default means leaving it where it is. You only need to set the backup role.

MarkD

Adam Yes that "Default" wording gave us the jitters the first time we did a backup migration, I think it would be clearer if the wording was No Change instead of Default on those dropdowns

8Dweb

MarkD For English, I actually prefer your suggestion. Good idea.