Centos 7 to Almalinux

Kati

Verified User
Joined
Sep 16, 2021
Messages
9
Hello, I have several servers where I have thousands of accounts hosted, we want to update our OS to almalinux (since centos 7 will disappear soon), is there a massive way to perform the migration? Similar to the cpanel import tool that we have in the administration panel

On my machines I also have Jetbackup but many times in massive restores Jetbackup generates random R's.

What do you recommend I do?
 
I am creating a server with Almalinux to replace the machine that has Centos 7 (which is already at the end of its useful life), and I want to migrate all the accounts to the new server
 
Follow this mini guide:
 
Be careful with Elevate. I have successful migrated CentOS 7 to Almalinux 8 on multiple servers. But just tried with one server to Almalinux 9, there were several issues: network missing (have to manually configure again, even that, the settings seem to be disappeared after rebooting), needed to rebuild several services such as exim, php, etc. Haven't got much time for debugging, and trying with other servers. Just wanted to share my little experience. BTW, DirectAdmin server is still not fully supported by Elevate project yet.
 
But just tried with one server to Almalinux 9,
Did you try from Centos 7 to Alma 9 or from Alma 8 to Alma 9?

However, seems he's migrating to a new server so that is better than elevating.

DirectAdmin server is still not fully supported by Elevate project yet.
How is that related with the DA server? Can you enlighten me on that what you mean by this?
Or do you just mean you have to run a ./build all after elevation?
 
Did you try from Centos 7 to Alma 9 or from Alma 8 to Alma 9?
The server was installed CentOS 7 originally. Then I elevated it to Almalinux 8. Running for a while, and then elevated to Almalinux 9.

However, seems he's migrating to a new server so that is better than elevating.
Yes, I just noticed that :)

How is that related with the DA server? Can you enlighten me on that what you mean by this?
Or do you just mean you have to run a ./build all after elevation?
Basically, Elevate checks software on server. Because DA builds its own versions, the configuration is different than standard installations. That's why Elevate can remove some software or create some conflicts. I was not running
Code:
./build all
again, but tried to see which components were effected.
 
Back
Top