Version upgrades

Version upgrades#

Version upgrades may include additional functionality, performance enhancements, and/or other improvements over previous versions. Fixes for certain types of issues will also be included in these updates.

Upgrading to v20.0.2#

The Replicator 20.0.2 upgrade requires the target server to be running v19.1.1 (must be provisioned with at least 2 CPU cores and 8 GB of RAM) or higher. For older versions, follow this guide to upgrade to v19.1.1.

Important

Profile data is automatically migrated when a Replicator 19.1.1 appliance is upgraded to v20.0.2. Refer to this guide to migrate data from a v19.1.1 appliance to a different v20.0.2 standalone or headless instance.

For v19.1.1 hardware appliance upgrades, see this section first.

Note

The upgrade will take about one hour to complete.
Due to an increase in minimum specs, older VMs with 2 GB of RAM should be provisioned with 8 GB RAM before the upgrade.
The upgrade requires a minimum of 16 GB free space on root (/). There may be older logs (sudo rm /var/log/messages-*) that can be deleted to free up space.
The primary appliance in a high-availability pair must be upgraded before the secondary/backup. See this section for instructions.

Contact Plixer Technical Support for assistance or clarifications.

Pre-upgrade preparation#

[Upgrades from 19.1.1] Create a backup of the v19.1.1 profile configuration data by downloading and running this utility (hardware appliances) or taking a VM snapshot (virtual appliances).
Confirm the current password for the replicator SSH user (run passwd replicator).

Verify that root login is disabled by running:

sudo sed -i 's/^#PermitRootLogin.*/PermitRootLogin no/g' /etc/ssh/sshd_config

Confirm that the Replicator server has access to https://files.plixer.com. This check can be performed by downloading the upgrade checksum file using the following command:
```
curl -O https://files.plixer.com/plixer-repo/scrutinizer/19.7.2/replicator-install.run.sha256
```
For Replicator servers that do not have internet access, download the file from the REPO_HOST_IP for the offline yum/dnf repository instead.

Upgrading the server#

Once all preparation steps have been completed, follow these steps to upgrade the appliance:

Offline upgrades#

To upgrade a Replicator 19.1.1 server that is unable to access the default yum/dnf repository on https://files.plixer.com/plixer-repo/scrutinizer/19.7.2, an offline repository will need to be set up on the local network. This repository can be hosted on a Scrutinizer server or another host on the network.

To set up the offline repository on a Scrutinizer server (with IP address REPO_HOST_IP), follow these steps:

High-availability pairs#

To upgrade a Replicator 19.1.1 high-availability (HA) pair to v20.0.2, follow these steps:

Note

To set up a new v20.0.0+ HA pair, follow this guide.

View instructions

[Virtual IP pairs only] On the primary instance, check /etc/keepalived/keepalived.conf and note the virtual IP address (VIP) being used (can also be obtained using ip addr show commands).

Stop and disable the keepalived service.

sudo systemctl stop keepalived
sudo systemctl disable keepalived

Verify that the VIP was released by the primary and has been taken over by the secondary instance (run on both):
```
ip a
```
Upgrade the primary instance following this guide.
After the upgrade, log into the web interface and verify that profiles were successfully migrated to the upgraded primary instance.
Apply a new license (must support at least two Replicator instances).
Register a new instance under Admin > Resources > Replicators and note the API authentication token.
Reboot the primary instance, and then upgrade the secondary instance following the same steps as before.

After the upgrade, stop and disable Scrutinizer services on the secondary instance.

sudo systemctl stop scrutinizer plixer_db plixer_collector plixer_webapp
sudo systemctl disable scrutinizer plixer_db plixer_collector plixer_webapp

Run the setup script:

sudo /usr/share/replicator/util/setup.sh

Enter the following details when prompted:
- Configuration host (primary instance) IP address
- API authentication token created when the new instance was created (step 6)
- Name assigned to the new instance
Restart the secondary instance, and then return to Admin > Resources > Replicators in the web interface to verify that the secondary instance has successfully registered itself with the primary (IP address should be displayed).
On the same page, click on the primary instance name (usually ‘Local’), and configure high availability using the primary and secondary instances (enter the previous VIP if necessary).
Click the Save button, and then wait two minutes.

Verify that /etc/keepalived/keepalived_replicator.conf contains the following (on both devices):

# this file is automatically generated do not edit
global_defs {
        script_user plixer
        enable_script_security
}
vrrp_instance VI_1 {
        state BACKUP
        interface eth0
        virtual_router_id 51
        priority 90
        advert_int 1
        preempt_delay 5
        notify  /usr/share/replicator/bin/notify.sh
        authentication {
                auth_type PASS
                auth_pass zhO2brnVF2byl4+zL/ssTaCPmHFr5IMQJEIVDkJiFCCvBIttqjBptwm8c8PWbjqqN4BVieKunkVqPWIRp4fG0Q==
        }
        virtual_ipaddress {
                10.42.150.17
        }
}

Modify /etc/keepalived/keepalived.conf on both instances:

sudo bash -c 'echo "include /etc/keepalived/keepalived_replicator.conf" > /etc/keepalived/keepalived.conf' 

Restart the keepalived service on both instances:
```
sudo systemctl restart keepalived
```

Both Replicator instances should now be running v20.0.2 and set up as a high-availability pair using the same (pre-upgrade) configuration.

Hardware appliances#

V19.1.1 hardware appliances that are upgraded to v20.0.2 default to the standalone role and can be used as the configuration host for headless Replicator instances.

If another appliance (standalone Replicator 20.0.2 or Plixer One/Scrutinizer 19.7.2) is going to be used as the configuration host, the hardware appliance can be converted to a headless instance instead.

Important

Profile configuration data must be backed up before a Replicator 19.1.1 hardware appliance is upgraded, so it can be restored after the conversion.

Upgrading and converting a v19.1.1 hardware appliance#

Follow these steps to upgrade a v19.1.1 hardware appliance and convert it to a headless instance with all configuration data retained:

Upgrading to v19.1.1#

Upgrading the server#

Once all preparation steps have been completed, follow these steps to upgrade the appliance:

Offline upgrades to v19.1.1#

The following instructions for setting up an offline repo are intended for upgrading to Replicator v19.1.1 only:

Version upgrades

Contents

Version upgrades#

Upgrading to v20.0.2#

Pre-upgrade preparation#

Upgrading the server#

Offline upgrades#

High-availability pairs#

Hardware appliances#

Upgrading and converting a v19.1.1 hardware appliance#

Upgrading to v19.1.1#

Upgrading the server#

Offline upgrades to v19.1.1#

Upgrading to v19.0.1#

Upgrading to v18.14#