Pre-Upgrade (for major version upgrades)

* When using your own NGINX certificate:

• Backup the certificate file located in the /etc/nginx directory before the upgrade
• Copy back after the upgrade has completed

Note - Keep a copy of the previous RPMs on the server, in case of rollback

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

JetPatch all-in-one

If you are running the JetPatch all-in-one (the DB and the application is on the same server) you can take a snapshot of the server or backup the required information as described in the separated architecture instructions below.

Separated Architecture

If you are running the JetPatch application server separate from the DB, you need to:

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 if you have a custom mount location, it will be /<custom mount>/share/intigua/*

Post-Upgrade

***If the upgrade includes a new version of the connector and you have been told that you need to deploy it, then provision the updated connector to the endpoints  with the following steps.  Otherwise, there is no rush to upgrade the connector.  Instead, you can deploy it only on new machines like if there is a new operating system the connector supports:

Note1: In an environment using a custom mount point, you will need to copy the connector files appropriately.  See connector upgrade and custom mount location for more information.

Note2: In an environment using JetProxy, you will need to configure an additional management service that will be used by the endpoints connected to the JetProxy server.

Note3: Modify connector policies on the machines, because they can override the connector upgrade selection (example, if the policy is active for an older connector version, it will then downgrade the connector until the policy is disabled or deleted)

1. Check server state

1. Go through the monitor health article. This option allows the user to monitor different server statistics. If a statistic (Ex: CPU %) is continuing to remain at a high load - this could be an indicator that the server is experiencing issues
2. Go through the patching checklist. Please ensure that the list is followed accordingly as skipping steps may result in issues scene above

2. Update connector (JetPatch agent)

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.

3. Run a test patching cycle

1.  Running a test patching cycle will help ensure that the upgrade was completed successfully before going on to patch your production environment 

Related Section

• General Console and Upgrade Troubleshooting