LogoLogo
T4O-6.x
T4O-6.x
  • About Trilio for Openstack
    • Welcome to Trilio for OpenStack
    • T4O Architecture
    • Release Notes
    • Features
    • Compatibility Matrix
    • Resources
      • 6.1.0
      • 6.0.0
  • Getting Started
    • Requirements
      • Network Considerations
      • Installation Strategy and Preparation
    • Getting started with Trilio on Red-Hat OpenStack Platform (RHOSP)
      • Trilio Installation on RHOCP (with RHOSP17.1)
      • Post Installation Health-Check
      • Trilio Installation on RHOSO18.0
      • Add new backup target on RHOSO18.0
    • Getting started with Trilio on Canonical OpenStack
    • Licensing
    • Installing WorkloadManager CLI client
    • Uninstall Trilio
      • Uninstalling from RHOSP
  • Upgrading to T4O-6.x from older supported versions
    • Supported Trilio Upgrade Path
    • Upgrading on RHOSP
    • Upgrading on RHOSO18.0
  • 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
    • Serial Upload per Instance during Snapshot
  • User Guide
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notifications
  • Admin Guide
    • Backups-Admin Area
    • Backup Targets
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import & Migration
    • Disaster Recovery
      • Example runbook for Disaster Recovery using NFS
    • Migrating encrypted Workloads
    • Rebasing existing workloads
  • Troubleshooting
    • Frequently Asked Questions
    • General Troubleshooting Tips
    • Important log files
  • API GUIDE
    • Backup Targets
    • 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] Restart wlm-cron resource
  • 4] Fetch backup target details
  • 5] Import workloads
  • 6] Update backing file path

Was this helpful?

Export as PDF
  1. Upgrading to T4O-6.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

  • Disable the wlm services on all controller nodes

sudo systemctl stop tripleo_triliovault_wlm_api.service
sudo systemctl disable tripleo_triliovault_wlm_api.service
sudo systemctl stop tripleo_triliovault_wlm_scheduler.service
sudo systemctl disable tripleo_triliovault_wlm_scheduler.service
sudo systemctl stop tripleo_triliovault_wlm_workloads.service
sudo systemctl disable tripleo_triliovault_wlm_workloads.service
  • Disable the datamover service on all compute nodes

sudo systemctl stop tripleo_triliovault_datamover.service
sudo systemctl disable tripleo_triliovault_datamover.service
sudo umount /var/lib/nova/triliovault-mounts

2] Install latest Trilio release

Take a backup of existing triliovault-cfg-scripts directory

cd /home/stack
mv triliovault-cfg-scripts/ triliovault-cfg-scripts-5.x

Clone triliovault-cfg-scripts github repository of latest release.

git clone -b {{ trilio_branch }} https://github.com/trilioData/triliovault-cfg-scripts.git

Copy the passwords and triliovault wlm ids files from old cfg-scripts directory.

cp /home/stack/triliovault-cfg-scripts-5.x/redhat-director-scripts/rhosp17/environments/passwords.yaml /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp17/environments/trilio_passwords.yaml
cp /home/stack/triliovault-cfg-scripts-5.x/redhat-director-scripts/rhosp17/puppet/trilio/files/triliovault_wlm_ids.conf /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp17/puppet/trilio/files/

While providing the backup target details in section 4.1, please ensure to provide the existing backup target (of 5.x release) as default.

3] Restart wlm-cron resource

From any one of the controller nodes, run the below command.

sudo pcs resource restart triliovault-wlm-cron-podman-0

4] Fetch backup target details

From any one of the controller nodes, login to wlm api container and run the below commands to fetch the backup target details.

sudo podman exec -it triliovault_wlm_api bash
source /etc/triliovault-wlm/cloud_admin_rc

workloadmgr backup-target-type-list

This command will return the backup_target_id and backup_target_type_id.

5] Import workloads

From any one of the controller ndoes, login to wlm api container and run the below commands.

sudo podman exec -it triliovault_wlm_api bash
source /etc/triliovault-wlm/cloud_admin_rc

workloadmgr abandon-resource --all-workloads --all-policies --cloud-wide
workloadmgr workload-get-importworkloads-list --source-bt {{ backup_target_id }}
workloadmgr workload-importworkloads --source-btt {{ backup_target_type_id }}

6] Update backing file path

This step would be needed only when your old backup target is S3.

PreviousSupported Trilio Upgrade PathNextUpgrading on RHOSO18.0

Last updated 3 months ago

Was this helpful?

Please follow from section 1.4 to section 10. Please note that sections 5 and 6 needs to be skipped during this process.

Please follow to update the backing file path of existing snapshots.

this documentation
this documentation