Pre-Upgrade

Snapshots Recommended:

• General: We strongly recommend taking snapshots.
• Use Cases:
  • Single VM: Use the same VM if you need to leverage snapshots.
  • New VM: Consider a new VM if snapshots aren’t necessary.

JetPatch All-in-One (DB and Application on Same Server):

• Options:
  • Take a server snapshot
  • Backup critical information as detailed in the separated architecture section below

Separated Architecture (Application and DB on Different VMs):

• Take snapshot of application and DB
• When Snapshots Aren’t Feasible:
  1. Database Backup: Follow the Backup the database instructions.
  2. Application Backup: Backup the following directories:
     • /usr/share/tomcat/default/conf/*
     • /usr/share/intigua/*
       • Note: For custom mount locations, the path will be /<custom mount>/share/intigua/*.

Additional Pre-Upgrade Steps:

• NGINX Certificate:
  • Backup the certificate file in /etc/nginx
  • Restore it after the upgrade
• RPM Copies:
  • Keep copies of previous RPMs on the server for rollback if needed

In general, we recommend snapshots.  If you need leverage the snapshots, you can try the same VM, otherwise use a new VM.

Post-Upgrade

How to Update Connector

1. Log into the Console as an Administrator, and go to the Servers tab.
2. To avoid errors, filter the list by the Status column to view only endpoints with active connections. Remember that you'll need to update the others later.
3. Click the uppermost checkbox to select all endpoints:

   

4. If there are multiple pages, click to select all:

   

5. Provision the new JetPatch connector management service to the endpoints.
   1. In the Servers tab, select the endpoints, and click Server Actions > Manage Intigua on Server:

      

   2. Select Manage Intigua On Server, and under Configuration Service, select a management service:

      

   3. Click Apply.

Note: It may take some time for the action to be performed.

Related Section

• General Console and Upgrade Troubleshooting