Joomla Migration to Google Cloud: Step-by-Step Guide

Install LAMP or LEMP on the new server before migration

A ready Google Cloud server requires installing the same software stack, such as LAMP or LEMP, that the existing Joomla site currently uses.

Your goal is to ensure the new Google server has all the servers and packages that are the same as the current server. We’ve listed some helpful posts that you can use to install Apache, Nginx, MySQL, MariaDB, or PHP.

You may want to use some other posts when installing LAMP or LEMP on Ubuntu Linux.

• How to install Apache on a Google Cloud server (alternative to Nginx)
• How to install Nginx on a Google Cloud server (alternative to Apache)
• How to install PHP on a Google Cloud server
• How to install MySQL or MariaDB database server

You can use the posts above to install the same servers and packages you have installed on your current server. However, use the identical posts mentioned above to install specific packages on your new server.

Once all the packages are installed, you can transfer content from your current server to the new one.

Configure your new Google server similar to your current server

To make sure your Joomla site works correctly after moving to Google Cloud, you need to set up the new server to be just like your old one.

• Apache directory: /etc/apache2/
• Nginx directory: /etc/nginx/

Your PHP configuration should also be identical to your current server’s PHP settings. Use the post above to install a specific PHP version and all the modules on your current server.

• PHP directory: /etc/php/

Your MySQL or MariaDB configurations should also mimic your current server. Validate each file, directory, and other data to ensure your new server is no different from your current server before migration.

• MySQL / MariaDB directory: /etc/mysql/

Once you have that done, you can continue with the migration process.

Back up current server data and database before migration

First, you need the Joomla website content and database content. Back up the website content as well as the content in the database.

Stopping new changes before the Joomla backup ensures the backup accurately reflects the site's state at that specific moment. This prevents data discrepancies.

Joomla content backup requires logging onto the server using SSH, a secure computer connection method. After connecting to the current server's SSH console, users run specific commands to back up Joomla content. This backup process targets the `/var/www/html/` directory, which typically stores website files.

When you run the commands below, a backed-up file named current-server-backup.tar will be created with your Joomla content.

Database backup uses a root account or an account with full database access. This full access ensures all database information is saved before migrating Joomla to Google Cloud, a process completed at version 3.9. This backup protects your data.

To backup all databases on the server, you run the commands below:

A file named `all_databases_backup.sql` creates a complete copy of all your website's data. Storing this backup file in the current working directory ensures immediate accessibility for the migration process.

You should now have two files: current-server-backup.tar and all_database_backup.sql.

Copy the current server’s content to the Google Cloud server

Copying current server content to the new Google Cloud server is the next step. Users can transfer tar and SQL data files to the new server using several methods.

You can use the rsync command from the new server by SSHing it and a command similar to that shown below (changing the host names as needed).

While connected to your Google Cloud console, run the commands below to connect to your current server and copy over the backed-up content.

Secure Copy Protocol (SCP) securely copies Joomla website files. The SCP command `scp -r /path/to/local/joomla/files username@google_cloud_ip:/path/to/remote/directory` uses encryption to protect website data during transfer. This method encrypts data during transit.

scp user@old-server.com:/home/<username>/all_database_backup.sql /home/username/
scp user@old-server.com:/home/<username>/current-server-backup.tar /home/username/

If you can’t get the files using SSH, then you can use the wget command to download the files to your new Google Cloud server.

You must copy the files to the current server web server root directory to be able to use the commands below.

cd ~
wget http://old-web-site.com/all_database_backup.sql
wget http://old-web-site.com/current-server-backup.tar

Once the files are copied to your new server, continue to extract them below and import the database content into your database server.

Restore the current server’s content to the Google Cloud server

After backing up your Joomla site, you’ll restore that backup onto your new Google Cloud server, placing the files and database in the correct spots.

tar -xvf current-server-content.tar
sudo cp -rf /var/www/html/ /var/www/html/

Next, run the commands below to import the database content to your servers.

Commands must run after copying server and database information to the Google Cloud server. These commands set correct file and folder permissions on the Google Cloud server. Setting these permissions ensures the Google Cloud server's settings match the original server's setup, preventing website access problems.

Before restarting the web server, confirm that all settings on your old server match precisely with the settings on the new Google Cloud server. This verification step ensures a smooth transition for your website and confirms that your migration is complete.

sudo systemctl restart nginx
sudo systemctl restart apache2

If you get an error, make sure to resolve it.

Update your DNS and point your domain to your new Google server IP address

Once your Joomla site is running on Google Cloud, you’ll update your domain’s DNS settings to point visitors to the new server’s IP address.

Once your local test is successful, log in to your DNS provider portal and update the DNS A record to point to your new server IP address.

If everything works, you can continue fine-tuning your new server to ensure everything is configured correctly.

And that’s how you migrate your Joomla site to Google Cloud.

Conclusion:

This Joomla migration guide explains how to move a Joomla website to a Google Cloud server. Users can share feedback or report errors using the comment form located below the guide.

You migrate your Joomla website to Google Cloud, ensuring zero downtime during the transfer.

Joomla website migration moves your Joomla installation, database, and files to a new hosting place. This careful process ensures your Joomla website remains visible to visitors during the move, a strategy vital for business continuity.

Joomla migration to Google Cloud Platform (GCP) involves moving your website. GCP offers a suite of cloud computing services. This Joomla migration guide covers moving Joomla sites from local computers or other servers to GCP.

You’ll prepare your GCP environment and configure your Joomla application for a smooth move. The process begins with setting up your Google Cloud server and concludes with updating your domain’s DNS records to point to the new host.

Taking inventory of a Linux server before migration

Before you move your Joomla site to Google Cloud, it’s important to check what’s currently running on your old Linux server.

These are what you’ll need to gather from your current server:

• Web server and version number
• Database server and version number
• PHP and related modules
• Other servers and services and how they’re configured

If you’re using Apache, here’s how to check its version on Ubuntu.

apache2 -v

For more in-depth checks and installation steps, check out this guide:

How to check and install specific Apache versions on Ubuntu Linux

If you’re using Nginx, here’s how to check its version on Ubuntu.

nginx -v

For more in-depth checks and installation steps, check out this guide:

How to check and install specific Nginx versions on Ubuntu Linux

To check what version of PHP is installed and how to install a specific version on Ubuntu Linux, read the post below:

How to check and install specific PHP versions on Ubuntu Linux

Whether you’re running MySQL or MariaDB, the post below shows you how to determine which version of MySQL or MariaDB runs on Ubuntu Linux.

How to find what version of MySQL or MariaDB runs on Ubuntu Linux

How to set up and connect to your Google Cloud server

After checking your current server, you’ll set up your new Google Cloud server, which is like getting a virtual computer ready for your Joomla site.

Your Google Cloud server, also known as a Compute Engine instance, lets you connect using SSH, a secure command-line interface, right from your browser within the Google Cloud Console.

SSH from the browser supports the following:

• Web browsers
  • The latest version of Google Chrome
  • Firefox
  • Microsoft Edge
  • Microsoft Internet Explorer 11 and later
  • Safari 8 and later. Note that Safari is not supported in private browser mode.
• Virtual machine configurations
  • All Linux VM images are natively available in Google Cloud.

No additional software or browser extensions are needed. Log in to Google Cloud Console and go to Menu ==> Compute Engine ==> VM instances.

In the list of virtual machine instances, click SSH in the row of the instance that you want to connect to.

Alternatively, you can open an SSH connection to an instance by clicking its name and SSH from the instance details page.

An SSH terminal window with the Ubuntu Linux instance created in the series’s second post will open.

You should now be able to run commands in Ubuntu Linux created on the Google Cloud server.

Install LAMP or LEMP on the new server before migration

A ready Google Cloud server requires installing the same software stack, such as LAMP or LEMP, that the existing Joomla site currently uses.

Your goal is to ensure the new Google server has all the servers and packages that are the same as the current server. We’ve listed some helpful posts that you can use to install Apache, Nginx, MySQL, MariaDB, or PHP.

You may want to use some other posts when installing LAMP or LEMP on Ubuntu Linux.

• How to install Apache on a Google Cloud server (alternative to Nginx)
• How to install Nginx on a Google Cloud server (alternative to Apache)
• How to install PHP on a Google Cloud server
• How to install MySQL or MariaDB database server

You can use the posts above to install the same servers and packages you have installed on your current server. However, use the identical posts mentioned above to install specific packages on your new server.

Once all the packages are installed, you can transfer content from your current server to the new one.

Configure your new Google server similar to your current server

To make sure your Joomla site works correctly after moving to Google Cloud, you need to set up the new server to be just like your old one.

Ensure the web server (Apache or Nginx) settings are on old and new servers, including the same directory structure and Virtual Host or Server block content.

• Apache directory: /etc/apache2/
• Nginx directory: /etc/nginx/

Your PHP configuration should also be identical to your current server’s PHP settings. Use the post above to install a specific PHP version and all the modules on your current server.

• PHP directory: /etc/php/

Your MySQL or MariaDB configurations should also mimic your current server. Validate each file, directory, and other data to ensure your new server is no different from your current server before migration.

• MySQL / MariaDB directory: /etc/mysql/

Once you have that done, you can continue with the migration process.

Back up current server data and database before migration

A complete backup of all website files and the database from your current server is essential before migrating a Joomla site to Google Cloud. This Joomla site backup protects your data during the move. This backup ensures you can restore your Joomla site if any issues arise during the Google Cloud migration.

First, you need the Joomla website content and database content. Back up the website content as well as the content in the database.

Stopping new changes before the Joomla backup ensures the backup accurately reflects the site's state at that specific moment. This prevents data discrepancies.

Joomla content backup requires logging onto the server using SSH, a secure computer connection method. After connecting to the current server's SSH console, users run specific commands to back up Joomla content. This backup process targets the `/var/www/html/` directory, which typically stores website files.

When you run the commands below, a backed-up file named current-server-backup.tar will be created with your Joomla content.

Database backup uses a root account or an account with full database access. This full access ensures all database information is saved before migrating Joomla to Google Cloud, a process completed at version 3.9. This backup protects your data.

To backup all databases on the server, you run the commands below:

A file named `all_databases_backup.sql` creates a complete copy of all your website's data. Storing this backup file in the current working directory ensures immediate accessibility for the migration process.

You should now have two files: current-server-backup.tar and all_database_backup.sql.

Copy the current server’s content to the Google Cloud server

Copying current server content to the new Google Cloud server is the next step. Users can transfer tar and SQL data files to the new server using several methods.

You can use the rsync command from the new server by SSHing it and a command similar to that shown below (changing the host names as needed).

While connected to your Google Cloud console, run the commands below to connect to your current server and copy over the backed-up content.

Secure Copy Protocol (SCP) securely copies Joomla website files. The SCP command `scp -r /path/to/local/joomla/files username@google_cloud_ip:/path/to/remote/directory` uses encryption to protect website data during transfer. This method encrypts data during transit.

scp user@old-server.com:/home/<username>/all_database_backup.sql /home/username/
scp user@old-server.com:/home/<username>/current-server-backup.tar /home/username/

If you can’t get the files using SSH, then you can use the wget command to download the files to your new Google Cloud server.

You must copy the files to the current server web server root directory to be able to use the commands below.

cd ~
wget http://old-web-site.com/all_database_backup.sql
wget http://old-web-site.com/current-server-backup.tar

Once the files are copied to your new server, continue to extract them below and import the database content into your database server.

Restore the current server’s content to the Google Cloud server

After backing up your Joomla site, you’ll restore that backup onto your new Google Cloud server, placing the files and database in the correct spots.

tar -xvf current-server-content.tar
sudo cp -rf /var/www/html/ /var/www/html/

Next, run the commands below to import the database content to your servers.

Commands must run after copying server and database information to the Google Cloud server. These commands set correct file and folder permissions on the Google Cloud server. Setting these permissions ensures the Google Cloud server's settings match the original server's setup, preventing website access problems.

Before restarting the web server, confirm that all settings on your old server match precisely with the settings on the new Google Cloud server. This verification step ensures a smooth transition for your website and confirms that your migration is complete.

sudo systemctl restart nginx
sudo systemctl restart apache2

If you get an error, make sure to resolve it.

Update your DNS and point your domain to your new Google server IP address

Once your Joomla site is running on Google Cloud, you’ll update your domain’s DNS settings to point visitors to the new server’s IP address.

Once your local test is successful, log in to your DNS provider portal and update the DNS A record to point to your new server IP address.

If everything works, you can continue fine-tuning your new server to ensure everything is configured correctly.

And that’s how you migrate your Joomla site to Google Cloud.

Conclusion:

This Joomla migration guide explains how to move a Joomla website to a Google Cloud server. Users can share feedback or report errors using the comment form located below the guide.