Skip to content

RDAF Rollback Procedure Using VMware Snapshots

Important

For reference, 8.2.3 is considered the Latest Version, and 8.2.2 is considered the Previous Version. The terms Latest Version and Previous Version are used throughout this document for reference. Update the version references accordingly when using this procedure.

This document describes the procedure for rolling back an RDAF environment from Latest Version to Previous Version using VMware snapshots after completing the validation of Latest Version.

Follow the steps in the specified order to ensure that all RDAF services are stopped and restarted properly and that the environment is restored to its pre-upgrade state.

1. Pre-Upgrade and Validation Steps

Before starting the upgrade, perform the following preparatory steps:

1. Log in to VMware vCenter.

2. Take snapshots of all RDAF VMs before starting the upgrade to Latest Version.

3. Verify that snapshots of all VMs have been created successfully.

4. Upgrade the RDAF environment from Previous Version to Latest Version by following the standard RDAF Upgrade Documentation.

5. Complete the validation of all features and functionalities in Latest Version.

2. Revert VMware Snapshots

Once the validation of Latest Version is completed, perform the following steps to restore the environment to its pre-upgrade state.

1. Log in to VMware vCenter.

2. Locate all the RDAF VMs for which snapshots were created before the upgrade.

3. Revert all VM snapshots to restore the VMs to their pre-upgrade state.

4. Verify that all VMs have been successfully reverted to their respective snapshots.

Note

Ensure that snapshots are reverted consistently across all RDAF VMs to avoid version or data inconsistencies between components.

3. Stop All RDAF Services

After reverting the VMware snapshots, establish an SSH connection to the CLI VM and stop all RDAF services in the specified order to ensure a controlled shutdown of the environment.

Step 1. Stop the RDAF application service.

Execute the following command to gracefully stop the RDAF application service.

rdaf app stop

Step 2. Stop the RDAF worker service.

Execute the following command to stop the RDAF worker service

rdaf worker stop

Step 3. Stop the RDAF event gateway service.

Use the following command to stop the RDAF event gateway service.

rdaf event_gateway stop

Step 4. Stop the RDAF platform service.

Execute the following command to stop the RDAF platform services.

rdaf platform stop

Step 5. Stop the RDAF infrastructure services.

Use the following command to shut down all RDAF infrastructure services.

rdaf infra stop

Step 6. Stop external OpenSearch (if configured).

If external OpenSearch is configured and running, execute the following command to stop the external OpenSearch service.

rdaf opensearch_external stop

Step 7. Stop the bulk statistics service (if configured and running).

If the bulk statistics service is running, execute the following command to stop the service.

rdaf bulk_stats stop

Step 8. Verify the status of all RDAF services.

Once all the above services have been stopped, execute the following command to verify the status of all RDAF services.

rdaf status

Note

Verify that all RDAF services are in the Exited state before proceeding to the next step.

4. Start Infrastructure Services

Once all RDAF services have been stopped successfully, initialize the infrastructure services first. Ensure that all infrastructure components are operational before proceeding to the platform and application services.

Step 1. Start the RDAF infrastructure services.

Execute the following command to initialize all RDAF infrastructure services.

rdaf infra start

Step 2. Verify the infrastructure service status.

After initiating the infrastructure services, verify that all infrastructure components have started successfully.

Step 3. Perform the infrastructure health check.

To validate the operational status of the infrastructure components, execute the following health check command.

rdaf infra healthcheck

Note

Verify that the status of all infrastructure components is OK before proceeding.

Step 4. Perform MariaDB recovery (if required).

If the MariaDB cluster does not start successfully, perform the MariaDB recovery procedure described here.

Step 5. Start external OpenSearch (if configured).

If external OpenSearch is configured, execute the following command to start the external OpenSearch service.

rdaf opensearch_external start

Verify that external OpenSearch has started successfully before proceeding to the next step.

5. Start RDAF Platform and Application Services

After confirming that all infrastructure components are healthy, execute the following commands in the specified order to bring up the RDAF platform and application services.

Step 1. Start the RDAF platform service.

Execute the following command to initialize the RDAF platform services.

rdaf platform start

Step 2. Start the RDAF worker service.

Once the platform services have been initiated, execute the following command to start the RDAF worker service.

rdaf worker start

Step 3. Start the RDAF event gateway service.

Execute the following command to initialize the RDAF event gateway service.

rdaf event_gateway start

Step 4. Start the RDAF application service.

Once the dependent services are running, execute the following command to start the RDAF application service.

rdaf app start

Step 5. Start the bulk statistics service (if configured).

If the bulk statistics service is configured in the environment, execute the following command to start the service.

rdaf bulk_stats start

Allow sufficient time for all services to initialize before proceeding with the final validation.

6. Final Validation

Once all RDAF services have been started, execute the following commands to verify the service status, deployed component versions, and overall health of the RDAF environment.

Step 1: Verify the status of all RDAF services.

Execute the following command to confirm that all RDAF services are up and running successfully.

rdaf status

Note

Verify that all required RDAF services are running successfully.

Step 2. Verify the deployed RDAF component versions.

To confirm that the rollback has restored the expected RDAF version, execute the following command.

rdac pods --version

Note

Verify that the deployed RDAF components reflect the expected Previous Version.

Step 3. Perform the RDAF health check.

Execute the following command to perform the final health check of the RDAF environment.

rdac healthcheck

Note

Confirm that the health check completes successfully without any critical errors.

Step 4. Perform application-level validation.

After completing the service and health checks, perform the following validation activities.

1. Verify that all RDAF services are up and running successfully.

2. Confirm that the application and platform components are accessible.

3. Verify that the expected features and functionalities are working as expected.

4. Confirm that the environment has been successfully restored to the pre-upgrade state (Previous Version).