Introduction
This document provides the steps on how to move the JetPatch application from one server to another server.
This article contains the following topics:
- Pre-requisites
- Pre-migration tasks
- Set up a new JetPatch Application and database Server.
- Restore backups in the new server
- Re-configure the old JetPatch connector
Pre-Requisites
1. Disable IPv6 on the newly provisioned servers by following the instructions
2. Use the same version of JetPatch application on the destination server.
3. Use the same version or a higher version of PostgreSQL on the destination server. The supported versions are 13.x/14.x/15.x
Pre-migration tasks
Database server:
Backup existing database by logging into the server
Switch the user the postgres and execute the command
su – postgres
pg_dump <database-name> > dbbackup.sql
JetPatch application server:
Log in to the existing JetPatch application server
Backup the following directories (note: please be aware of any custom mounts):
- /usr/share/tomcat/default/conf/*
- /usr/share/intigua/*
Navigate to the JetPatch configuration directory and zip the files
cd /usr/share/tomcat/default/conf/
tar -czvf /root/tomcat_backup.tar.gz *
Navigate to the Intigua directory and take the backup by zipping the files
cd /usr/share/intigua/
tar -czvf /root/intigua_backup.tar.gz *
Copy the backup files to the new server using the preferred method
Setup new JetPatch application and Database server
- Install the JetPatch application following our KC document.
Please note:
- After installing the JetPatch application RPM files and PostgreSQL, do not login to Application.
- Existing users and plans will be migrated to the new server when restoring the database backup and configuration backup.
Restore the backups to the new servers
Database server:
Note: Since the newly provisioned JetPatch will be under an evaluation version, please coordinate with JetPatch support to apply the full license key before restoring the database.
Copy the .sql file new database server
Change the ownership of the backup file to the Postgres user using the command below
chown postgres:postgres /<path-of-dump>/dbbackup.sql
Switch to Postgres user
Command to switch to postgres user and run restore command
su – postgres
psql -d intiguadb -f dbbackup.sql
Grant Schema Level permissions to intiguadb for intigua user
psql -U postgres -d intiguadb
GRANT USAGE ON SCHEMA public TO intigua;
GRANT CREATE ON SCHEMA public TO intigua;
GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO intigua;
GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public TO intigua;
GRANT ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA public TO intigua;
Restart the PostgreSQL service
systemctl restart postgresql-<version>.service
JetPatch application server:
In the new JetPatch application server copy all the files from current server, and perform the below
Restore The Configuration Files. Navigate to the JetPatch configuration directory and restore the files
cd /usr/share/tomcat/default/conf/
tar -xzvf /<path>/tomcat_backup.tar.gz
Restore The Intigua folders & Files. Navigate to the intigua directory and restore the files
cd /usr/share/intigua/
tar -xzvf /<path>/intigua_backup.tar.gz
Restart the Tomcat service
systemctl restart tomcat.service
Re-configure the old JetPatch connectors
To communicate with the new JetPatch Application server you will need to re-configure all servers to communicate with the new A.S. To do so please follow the next steps:
1.Create a new Connector management service in the old JetPatch A.S and Save.
2.Add a secondary URL and enter the address of the new JetPatch A.S
3.Apply the management service to ALL servers (if different configurations are needed, create multiple management services but make sure the secondary URL is pointing to the new JetPatch server.
4.Make sure all servers are re-configured to use the new JetPatch connector.
5.Shut down the old JetPatch application server
6.Launch the new JetPatch application server.
All servers, which were re-configured to use the new connector, should now appear on the new JetPatch server as 'physical' machines.
Also, all the data that was present on the old server should now be successfully migrated to the new server.
Please note:
- If you no longer have access to the old JetPatch, then please follow this article.
- If you are also shifting your DB server, make sure to use the correct properties in intigua.properties file
Comments
0 comments
Please sign in to leave a comment.