Additional Upgrade Steps for Releases Earlier Than 26.1.0

The procedures in this section apply only to Standard deployments upgrading from a release earlier than 26.1. Skip this entire section for upgrades from 26.1 or later and for Hybrid deployments.

Migrate Custom Actions

Migrate custom actions to the updated path during a Virtual Appliance upgrade.

The custom actions path has changed from the previous release. Create and run the following script to migrate custom actions during the upgrade.

  1. Create a migration script for custom actions (custom-actions-migrate.sh) in /var/appd/config .
  2. Edit custom-actions.migrate.sh.
    CODE 
    vi /var/appd/config/custom-actions-migrate.sh
    JSON 
    #!/usr/bin/env bash

set -euo pipefail

# Configuration
OLD=/var/appd/data/custom-actions
NEW=/var/appd/config/custom-actions
ARCHIVE=${2:-custom-actions.tgz}

case "${1:-}" in
    backup)
        test -d "$OLD/actions" || { echo "No custom actions found at $OLD/actions"; exit 1; }
        
        sudo tar -C "$OLD" -czf "$ARCHIVE" actions
        echo "Backup created: $ARCHIVE"
        ;;

    restore)
        test -f "$ARCHIVE" || { echo "Backup file not found: $ARCHIVE"; exit 1; }
        
        sudo mkdir -p "$NEW"
        sudo tar -C "$NEW" -xzf "$ARCHIVE"
        
        # Set permissions
        sudo chown -R appduser:appduser "$NEW/actions"
        sudo find "$NEW/actions" -type d -exec chmod 755 {} \;
        sudo find "$NEW/actions" -type f -exec chmod 755 {} \;
        
        echo "Restored custom actions to $NEW/actions"
        ;;

    *)
        echo "Usage: $0 backup [custom-actions.tgz] | restore <custom-actions.tgz>"
        exit 1
        ;;
esac
  3. Change permissions of the migration script.
    CODE 
    chmod +x /var/appd/config/custom-actions-migrate.sh
  4. Sync custom actions to the running controller.
    CODE 
    appdcli controller actions-sync
  5. Create a custom action archive.
    CODE 
    ./custom-actions-migrate.sh backup custom-actions.tgz
Generate a Backup File

Migrate EUM and Synthetic Services Data to MinIO

Migrate existing EUM and Synthetic services data to MinIO for the Virtual Appliance.

Note: This procedure applies only if you are upgrading Virtual Appliance from 25.10.0 or older. Else, you can skip this procedure.
If you are running EUM and Synthetic services, you must migrate the existing data in these services to MinIO. To migrate data, you must run the migration script. Complete the following steps to enable data migration:
  1. Log in to the Virtual Appliance node and edit the globals.yaml.gotmpl file.
    CODE 
    cd /var/appd/config
vi globals.yaml.gotmpl
  2. Enable data migration for Minio, set the minio.migration.enable parameter to true.
    CODE 
    minio:
  migration:
    enable: true
  3. Sync the changes across all the cluster nodes.
    CODE 
    appdcli sync appd <profile>