Upgrading in an AWS Environment

In an AWS environment, you can upgrade LogLogic EVA from version 6.2.1 or 6.3.0 to version 6.3.1 by running a cross-version migration script.

Prerequisites

Before you start the upgrade procedure, you must meet the following requirements:
  1. Deploy a new instance of LogLogic EVA 6.3.1 in AWS. LogLogic LSP 35.0.0 is automatically installed with it.

    For instructions, see the "Deploying LogLogic EVA in AWS" section in TIBCO LogLogic® Enterprise Virtual Appliance Quick Start.

  2. The status of Advanced Features options (enabled or disabled) must be identical on the source instance and the new 6.3.1 instance.
    Source version Applicable Features
    6.2.1 Advanced Features
    6.3.0 Advanced Features, Advanced Aggregation, and Monitoring Console
  3. The version of LogLogic LSP on both LogLogic EVA instances must be identical. Therefore, on your existing LogLogic EVA instance, you must upgrade the LogLogic LSP to version 35.0.0, because LogLogic EVA 6.3.1 is compatible with LogLogic LSP 35.0.0.

    For instructions about upgrading LogLogic LSP, see TIBCO LogLogic® Log Source Packages Installation and Upgrade Guide.

Perform the following procedure on the source LogLogic EVA instance (version 6.2.1 or 6.3.0) and the destination LogLogic EVA (6.3.1) instance - as indicated.

Procedure

  1. On the destination instance:
    1. Log in to the destination instance as the toor user.
    2. Copy the SSH public key from the file /root/.ssh/id_dsa.pub.
  2. On the source instance:
    1. Log in to the source instance as the toor user.
    2. Ensure that the file /root/.ssh/authorized_keys exists. If not, create the file by running the following commands: 
      $ touch /root/.ssh/authorized_keys
$ chmod 600 /root/.ssh/authorized_keys
    3. Paste the SSH public key from step 1b into the /root/.ssh/authorized_keys file by running the following command: 
      $ echo '[SSH_public_key]' >> /root/.ssh/authorized_keys
  3. On the destination instance:
    1. Log in to the destination instance as the toor user.
    2. Run the following script: 
      $ /loglogic/scripts/crossversion_migration/migrate.sh -v <source_version> -s <IP_address_source_instance>
      where:
      • <source_version> can be either v621 or v630.
      • <IP_address_source_instance> must be the IP address of the source instance.
      For example: 
      $ /loglogic/scripts/crossversion_migration/migrate.sh -v v621 -s 192.0.2.4

Result

All data and configuration settings from your existing instance are migrated to the LogLogic EVA 6.3.1 instance.

The password of the 6.3.1 appliance GUI is set identical to the password of the source appliance. However, the password of the toor user remains unchanged after migration.

What to do next

If LogLogic LSP 35.0.0 is installed on your LogLogic EVA 6.3.1 instance, you must reimport the required Advanced Application Packs (AAP) that you had imported on the source appliance. For instructions about importing the AAPs, see TIBCO LogLogic® Log Source Packages Installation and Upgrade Guide.
Next topic: Running the Postupgrade Script
Previous topic: Upgrading in a High Availability Environment