LogoLogo
T4O-5.x
T4O-5.x
  • About Trilio for OpenStack
    • Welcome to Trilio for OpenStack
    • T4O Architecture
    • Release Notes
    • Compatibility Matrix
    • Resources
      • 5.2.4
      • 5.2.3
      • 5.2.2
      • 5.2.1
      • 5.2.0
      • 5.1.0
      • 5.0.0
  • Getting Started
    • Requirements
      • Network Considerations
      • Installation Strategy and Preparation
    • Getting started with Trilio on Red-Hat OpenStack Platform (RHOSP)
      • Post Installation Health-Check
    • Getting started with Trilio on Kolla-Ansible OpenStack
    • Getting started with Trilio on Canonical OpenStack
    • Software Driven Migration: VMware to OpenStack
      • Trilio's Approach
      • Supported Environments
      • Preparations
      • Deployment & Configuration
      • VM Migration Tool
      • Limitations
    • Licensing
    • Installing WorkloadManager CLI client
    • Uninstall Trilio
      • Uninstalling from RHOSP
  • Upgrading to T4O-5.x from older supported versions
    • Supported Trilio Upgrade Path
    • Upgrading on RHOSP
    • Upgrading on Kolla
    • Enabling T4O 4.1 or older backups when using NFS backup target
  • Advanced Configuration
    • Switching NFS Backing file
    • Multi-IP NFS Backup target mapping file configuration
    • Advanced Ceph configurations
      • Additions for multiple CEPH configurations
    • Multi-Region Deployments
  • User Guide
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notifications
    • VMware migration
      • Migration Plans
        • How-to Guide: Creating a Migration Plan
      • Migrations
        • How-to Guide: Initiating a Migration
  • Admin Guide
    • Backups-Admin Area
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import & Migration
    • Disaster Recovery
      • Example runbook for Disaster Recovery using NFS
      • Example runbook for Disaster Recovery using S3
    • Migrating encrypted Workloads
    • Rebasing existing workloads
  • Troubleshooting
    • Frequently Asked Questions
    • General Troubleshooting Tips
    • Important log files
  • API GUIDE
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notification Settings
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import and Migration
Powered by GitBook
On this page
  • 1] Prerequisites
  • 2] Install latest Trilio release
  • 3] Enable mount-bind for NFS
  • 4] Enable Global Job Scheduler
  • 4.1] Through UI
  • 4.2] Through CLI
  • 5] Import old workloads existing on the Backup Target

Was this helpful?

Export as PDF
  1. Upgrading to T4O-5.x from older supported versions

Upgrading on RHOSP

1] Prerequisites

Please ensure the following requirements are met before starting the upgrade process:

  • No Snapshot or Restore is running

  • Global job scheduler is disabled

  • wlm-cron is disabled on the Trilio Appliance

Deactivating the wlm-cron service

The following sets of commands will disable the wlm-cron service and verify that it is has been completely shutdown.

[root@TVM2 ~]# pcs resource disable wlm-cron
[root@TVM2 ~]# systemctl status wlm-cron
● wlm-cron.service - workload's scheduler cron service
   Loaded: loaded (/etc/systemd/system/wlm-cron.service; disabled; vendor preset                                                                                                                                                                                                                                                                                                                                                           : disabled)
   Active: inactive (dead)

Jun 11 08:27:06 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:06 - INFO - 1...t
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 140686268624368 Child 11389 ki...5
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - 1...5
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: Shutting down thread pool
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - S...l
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: Stopping the threads
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - S...s
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: All threads are stopped succes...y
Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - A...y
Jun 11 08:27:09 TVM2 systemd[1]: Stopped workload's scheduler cron service.
Hint: Some lines were ellipsized, use -l to show in full.
[root@TVM2 ~]# pcs resource show wlm-cron
 Resource: wlm-cron (class=systemd type=wlm-cron)
  Meta Attrs: target-role=Stopped
  Operations: monitor interval=30s on-fail=restart timeout=300s (wlm-cron-monito                                                                                                                                                                                                                                                                                                                                                           r-interval-30s)
              start interval=0s on-fail=restart timeout=300s (wlm-cron-start-int                                                                                                                                                                                                                                                                                                                                                           erval-0s)
              stop interval=0s timeout=300s (wlm-cron-stop-interval-0s)
[root@TVM2 ~]# ps -ef | grep -i workloadmgr-cron
root     15379 14383  0 08:27 pts/0    00:00:00 grep --color=auto -i workloadmgr                                                                                                                                                                                                                                                                                                                                                           -cron

2] Install latest Trilio release

3] Enable mount-bind for NFS

This step would be needed only when your backup target is NFS and if you are upgrading from T4O 4.1 or older releases.

T4O has changed the calculation of the mount point from 4.2 release onwards. It is necessary to set up the mount-bind to make T4O 4.1 or older backups available for T4O 4.2

4] Enable Global Job Scheduler

After the upgrade, global job scheduler would be disabled. You can enable that either through UI or CLI.

4.1] Through UI

Login to the Dashboard and go to Admin -> Backups-Admin -> Settings tab and check the 'Job Scheduler Enabled' checkbox. By clicking the 'Change' button you can enable the Global Job Scheduler.

4.2] Through CLI

Login to the any WLM container, create and source the admin rc file. Execute the enable the global job scheduler cli.

$ podman exec -itu root triliovault_wlm_api /bin/bash
$ source admin.rc
$ workloadmgr enable-global-job-scheduler
Global job scheduler is successfully enabled

5] Import old workloads existing on the Backup Target

Workload import allows importing Workloads existing on the Backup Target into the Trilio database.

PreviousSupported Trilio Upgrade PathNextUpgrading on Kolla

Last updated 1 year ago

Was this helpful?

Please follow to install the latest Trilio release.

Please follow to set up the mount bind for RHOSP.

Please follow to import the Workloads.

this documentation
this documentation
this documentation