Bobcares

Plesk CentOS 8 to AlmaLinux | Migration Tutorial

by | Jul 10, 2023

Perform these simple steps to ensure a smooth transition when migrating from Plesk in Centos 8 to AlmaLinux. At Bobcares, with our Plesk Hosting Support, we can handle your Plesk issues.

Steps to migrate from Plesk in CentOS 8 to AlmaLinux

1. Firstly, we must create a backup. It’s essential to make a backup of the Plesk server before beginning the move. The websites, databases, and any other relevant information should all be backed up. This makes sure we have a backup of the server in case there are any problems with the migration.

2. Then get the new server ready by creating a new server with AlmaLinux installed. This includes setting up network settings, installing AlmaLinux on the new server, and best practice-compliant server security. Also, we must confirm that the new server satisfies Plesk’s system requirements.

3. Now we must transfer the Plesk data from the CentOS 8 server to the new AlmaLinux server, including websites, databases, email accounts, and settings. There are a few ways to move the data, including using the built-in migration tools in Plesk or manually moving the data using programs like rsync or scp.

4. Following the completion of the data migration, Plesk should be set up on the AlmaLinux server. We can follow the AlmaLinux installation instructions after downloading the Plesk installer from the Plesk website. We should also be careful to select the same Plesk version that CentOS 8 did.

5. Transfer the data from the backup we made earlier to the newly installed Plesk. This includes changing back any customized configurations we had in place and restoring the website’s files, databases, and email accounts.

6. Now we must test the websites, databases, and email accounts to make sure they work properly on the new Plesk installation. Also, make sure that everything is functioning properly and resolve any problems that may emerge during the move.

7. Finally, when we’re ready to switch over, update the DNS records to refer to the new AlmaLinux server after making sure everything is working as it should on the new server. Incoming traffic will be forwarded to the new server as a result. As we gradually transition to the AlmaLinux server, we must remember to keep an eye on the DNS propagation.

[Looking for a solution to another query? We are just a click away.]

Conclusion

The article provides a 7-step method from our Support team to migrate from Plesk in Centos 8 to AlmaLinux, which ensures an easier migration process.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF