Earlier quoted context omitted.
This used to be true, but GCP forced their hand in January of 2024 with https://cloud.google.com/blog/products/networking/eliminatin... AWS matched a few months later: https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-i... I'm not trying to convince you to stay (I work for neither anymore!), just wanted to note that you can technically request a waiver. I'm not sure how this works in practice though. Like, i…
Have you tried to use the DTO? I did. They make you fill in a form saying you'll migrate all services (despite the blog post saying that isn't necessary), and then they take up to 12 weeks to make a decision. In my case they rejected it on a formality after 2 weeks and said to try again (the timer starts again). So in my case that would have been 14 weeks plus the time to migrate away. The egress costs are equivalent…
Migrating from DigitalOcean to Hetzner
431–440 of 454 posts
Re: Migrating from DigitalOcean to Hetzner
#432Earlier quoted context omitted.
It depends on the service and how critical that website is. Sometimes it's completely acceptable that a server will run for 10 years with say 1 week or 1 month of downtime spread over those 10 years, yes. That's the sort of uptime you can see with single servers that are rarely changed and over-provisioned as many on Hetzner are. Some examples: Small businesses where the website is not core to operations and is more…
What struck me though is that OP did so much work to migrare the server with zero downtime. The _single_ big server. Something’s off here.
Re: Migrating from DigitalOcean to Hetzner
#433The migration sharing is admirable and useful teaching, thank you! I see the DigitalOcean vs Hetzner comparison as a tradeoff that we make in different domains all day long, similar to opening your DoorDash or UberEats instead of making your own dinner(and the cost ratio is similar too). I work in all 3 major clouds, on-prem, the works. I still head to the DigitalOcean console for bits and pieces type work or proof o…
Not sure if I understand what you’re trying to say, but Hetzner's Console works just like that too.
Re: Migrating from DigitalOcean to Hetzner
#434Tried to sign-up for Hetzner. Says I need to provide my official ID for "enhanced verification". Yeah, right.
Re: Migrating from DigitalOcean to Hetzner
#435I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…
I’ve been experimenting with letting a local agent manipulate my remote servers using https://bower.sh/zmx-ai-portal What’s exciting is how simple cli tools can be so impactful to dev workflows
Re: Migrating from DigitalOcean to Hetzner
#436Congrats on doing this successfully, but your setup is amateur. This would have been infinitely easier if you were using IaC (Terraform/Ansible), containerized applications (that you're not already doing that is madness), and had a high-availability cluster setup in place already. It sounds like avoiding downtime is important to you, yet there's no redundancy in the existing stack at all, and everything is done by ha…
Re: Migrating from DigitalOcean to Hetzner
#437If you’re migrating a large MySQL database and you’re not using mydumper/myloader, you’re doing it the hard way. If you aren't using xtrabackup you are doing it wrong. I recently migrated a database with 2TB of data from 5.7 to 8.4 with about 15 seconds of down time. It wouldn't have been possible without xtrabackup. Mysqldumper requires a global write block, I wouldn't call blocking writes for hours a "zero downtime…
Re: Migrating from DigitalOcean to Hetzner
#438I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…
Wow a Claude add embedded into a Hetzner add. How deep does this go?
Or maybe it's just advertising/astro-turfing. At some point it has to be obvious.
Re: Migrating from DigitalOcean to Hetzner
#439Earlier quoted context omitted.
Have you tried to use the DTO? I did. They make you fill in a form saying you'll migrate all services (despite the blog post saying that isn't necessary), and then they take up to 12 weeks to make a decision. In my case they rejected it on a formality after 2 weeks and said to try again (the timer starts again). So in my case that would have been 14 weeks plus the time to migrate away. The egress costs are equivalent…
If you're in the EU and subject to the law, it might be easier to just transfer the data out and then sue them to get your money back.
Re: Migrating from DigitalOcean to Hetzner
#440I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…
I got a dedicated VPS just for the one thing and it did everything. I don't have a perfect understanding of possible openings that might have been left by misconfiguration. The data in question is so trivial that it doesn't matter to me if it's read so long as my VPS doesn't become party to a botnet and I can monitor to make sure that doesn't happen and shut it down if it does.