24 hours later, I'm back!

Summary of the previous episodes:

1. 3 days ago, my old dedicated server started spewing error messages about the CPU.
2. On a hunch, I ran backup-manager with my existing configuration that's supposed to send the compressed database dump + files to an FTP backup server.
3. I contacted my hosting provider to figure out the error.
4. Answer was quick: "we can't physically intervene on the server, and the same offer isn't available anymore, you have to pick a new offer".
5. I pick an upgrade, no answer for a day.
6. A day ago, they made the new server available to me, and immediately removed access to the old server from my account, including the attached FTP backup storage.
7. Asked the support to restore access either to the old server or at least the FTP storage. At this point I've lost all my Internet history from 2009 onwards.
8. The "Customer Excellence Specialist Level 2" throws his hands in the air, saying that the CPU errors are making either SSH or KVM impossible.
9. 12 hours ago, they restored my access to the server and the FTP storage. No luck, last backup on that server dates back to 2019. Server's IP is "very pingable" according to support, but no remote connection is possible.
10. Through the hosting provider console, I rebooted in rescue mode. No luck, still no remote connection. I switch back to regular mode with a new reboot.
11. I start to receive emails from my third-party monitoring system that my web sites are available again!
12. I jump on my terminal, the remote connection works! I don't know how much time I have, I stop the web server to save CPU cycles. I found the fresh local backup files. I start to download them locally. 25 GB at 500 kB/s, it's not looking good. I try to access my old server from my new server directly, transfer rate is 50 MB/s, we're getting somewhere.
13. The archive is compressed with LZMA, but I'm unable to expand the archive, lzma reports an succint error.
14. Pushing my luck, I start a full MariaDB database backup on the old server. Meanwhile, I start copying the old server's files onto the new using scp. Wrong choice, permissions and symbolic links aren't preserved. Started again with rsync with better success.
15. Importing the database backup was straightforward, works right out of the box with the already existing user credentials.
16. I finish importing the files, fire the web server after fixing several unmet dependency issues, and here I am again!

Phew. Did you miss me?

#SysAdmining #SysAdmin #IDontKnowWhatImDoing