Moving Hetzner Cloud Server to other location

[timconsidine]

Whenever I have moved the Cloudron server, I have simply :

• left original Cloudron server running
• ensured all apps have backups
• installed Cloudron on new server
• changed DNS of all domains
• performed a restore according to the docs BUT NOTE the restore option is tiny text and easy to miss
• after testing, delete original server

It's been seamless.

However, I note your intention to keep the IP address.
I guess this is important for you.
I think your approach is "non standard" but your situation might justify it.
Don't Hetzner have an ability to move the IP addresses from server A to server B (allowing a more standard Cloudron restore) ?
In any (all) case, I would move Step 3 to Step 7 - don't delete anything just in case.

[Kubernetes]

Thanks for your feedback @timconsidine

I didn't think about that option to use the Cloudron restore. How is the Cloudron license migrated from the old to the new server?

Keeping the IP address is key to me, as the reputation for e-mail is quite good for it and there might be some more use cases where have this ip whitelisted and so on.

Hetzner does have an ability to move the IP address, but I think it only works when deleting the server - but you might be right, maybe I just need to reassign the ip to the new server. So I would not need to delete the old server first. Good hint!

[Kubernetes]

I just realized, that I cannot take over the IP address from datacenter in Nürnberg to Falkenstein. So I have to change the ip address with migration.

[robi]

@Kubernetes yes, networks are generally bound to each DC. It was surprising that server images could be moved across too.

Since your server is going to be a dynamic IP in the short term, just turn on that feature before the image migration, so it updates everything for you.

If going the restore route, there's no need.

If open to going the migration between two running servers route, depending on the number of apps, if a smaller amount (<20?), they can be manually moved via their backup config downloads and imports.

For a larger number, I wanted to automate it via the API with N8N in another thread from server B to A, but didn't get too far as the API docs weren't done. (happy to collaborate on this to get it working..)

[Kubernetes]

@robi Great hint with the dynamic IP feature! Thanks!

I think I will go for the migration with changing the IP also.

With N8N I have no experience, so I may not be a help with that. Sorry

[robi]

@Kubernetes said in Moving Hetzner Cloud Server to other location:

With N8N I have no experience, so I may not be a help with that. Sorry

nothing a quick video can't get you up to speed on quickly ;-]

[Kubernetes]

@robi Ok, could you link your thread pls?

[robi]

@Kubernetes For you, sure.. https://forum.cloudron.io/post/67715

[ccfu]

Is there a particular reason you want to move your Cloudron from Nuremberg to Falkenstein? I would have thought it would be easier to move the storage boxes from Falkenstein to Nuremberg (if you really need everythting in one DC) so you don't need a new IP.

[Kubernetes]

I think for perfomance reasons it's better to have them in the same datacenter. Unfortunately there are no Storageboxes available to book for DC Nuremberg. That's why I want to migrate to Falkenstein.
However, I just started the migration process and the IP of the new cloud server seems to be okay in terms of reputation

[Kubernetes]

Migration went fine within 39 Minutes in total (37GB Snapshot)
The DynDNS Feature didn't work for me. So I initiated the DNS Sync and it seems everything works fine again - but in Falkenstein now
Thanks guys!

[ccfu]

That was quick and good to know if I ever need to migrate. I also have servers in Nuremberg and storage boxes in Falkenstein, though so far I haven't had any performance issues.

[robi]

@Kubernetes said in Moving Hetzner Cloud Server to other location:

The DynDNS Feature didn't work for me. So I initiated the DNS Sync

I recently had an emergency IP change as it seems the upstream network provider was swapped, and had the DynDNS feature enabled which worked for the Cloudron server itself, but not for the hosted sites.

To fix it I also had to resync DNS for 100+ sites.

@girish why doesn't DynDNS feature update all the records for all the sites that no longer match?

IMO the manual Sync should not be required.

[girish]

@robi as in, update records which cloudron didn't create/doesn't maintain?

[robi]

@girish quite the opposite, it created all of them but did not maintain them after the IP change.

[girish]

@robi dyndns is run as a cron job every 1 hour. This was changed last release to run every 10 mins.

[Kubernetes]

@girish Ahh, this explains it. I was not patient enough and was assuming DynDNS is triggered when IP is changed

[robi]

@Kubernetes same here, or at least on reboot, like a run once, then on cron.

@girish that was the odd part, the dashboard domain had the IP set right, but all other sites didn't and needed re-syncing