Server moving without immediatly delete the website at the old server

Thomas_W

Not all customer use the DNS Server from the system. Especially bigger companies use own DNS Server. There it's difficult to move the website without downtime.

It would be great if it's possible to have the option to move them so that the website is at the new and the old IPs available. So they can change the DNS when they have time, the website keeps online and the old data can be deleted after. Of course there is a risk of data loose if somebody makes changes at the old server.

GoSuccess

I think what you're referring to is already on the roadmap:

Proxy on server migration. When a website is moved between servers, the old server will proxy requests to the new server until the DNS is updated.

I just asked @Adam about this yesterday, and this feature will likely be released this year. Before that, however, the focus is on the PostgreSQL support, which will be released soon.

Nickske00

Keeping a website available in two places will also mess up the database (unless you use a third server as database) if it is for example a shop. You get orders on the 'old' server that will not appear in the 'new' server. If you can plan a move lower the ttl for the a/aaaa records before the move and you will face very little downtime.

Adam

Nickske00

Exactly. Another hypothetical scenario, your customer is running a subscription based SaaS. It has a cron job which runs on the 1st of the month and charges everyone's credit card for the monthly subscription. If the site is in 2 places, the cron runs twice and the customers are charged twice.

If you need a website to exist in 2 places, the easiest way to do this is to create a second cluster. On the first cluster, click "..." then "download website data" on the website dashboard. Upload the backup to the new cluster and import the site there.

Proxy on server migration is still a planned feature.