Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • TIBCO LogLogic® H4/H4R1/H4R2 Appliance Migration Options


    Manoj Chaurasia

    Table of Contents


    TIBCO LogLogic® provides the industry's first enterprise-class, end-to-end log management solution. Using LogLogic® log management solutions, IT organizations can analyze and archive log and machine data for the purpose of compliance and legal protection, decision support for security remediation, and increased system performance and improved availability of overall infrastructure.


    Introduction

    TIBCO has announced the retirement of the H4, H4R1, and H4R2 generation of its TIBCO LogLogic® Log Management Intelligence (LMI) hardware appliance. 

    Purpose of the Article

    TIBCO recommends the following options for migration from the H4/H4R1/H4R2. This article explains these options to help customers choose the option that is right for their organization:

    • Migrate to the Enterprise Virtual Appliance hosted on a VMWare server
    • Migrate to the Enterprise Virtual Appliance hosted in the AWS cloud

    The following information will explain these options in more detail.

    Option 1. Migration to the TIBCO LogLogic® Enterprise Virtual Appliance (EVA) hosted on a VMWare server.

    This option puts the customer in control of the hardware environment, with the ability to grow their system as needs and requirements evolve, from adding RAM to adding CPU and disk capacity. The EVA offers all of the features and functionality of a hardware appliance.

    This option does not offer an automated migration path. TIBCO Professional Services Group can assist with design and implementation for successful migration of the configuration and data from the old to new systems. For the specific upgrade path for each H4 family model to the EVA see the TIBCO LogLogic physical appliances - Upgrade path matrix at the end of this article.

    Option 2. Migration to the TIBCO LogLogic® Enterprise Virtual Appliance (EVA) hosted on Amazon Web Services (AWS).

    This option offers the same benefits and flexibility of EVA, hosted on the AWS cloud. No need for local hardware. HA clustering is not currently available for cloud deployments.

    This option does not offer an automated migration path. TIBCO Professional Services Group can assist with design and implementation for successful migration of the configuration and data from the old to new systems. For the specific upgrade path for each H4 family model to the EVA see the TIBCO LogLogic physical appliances - Upgrade path matrix below.

    TIBCO LogLogic H4 Appliances - Upgrade path

    H4 Appliance

    EVA replacement

    Capacity Expansion Options

    LX825

    EVA Mid (500 Sources, 2.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s)

    LX1025

    EVA Mid (500 Sources, 2.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s)

    LX4025

    EVA Global (5K Sources, 8.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s), Additional 2TB, 6TB Retention

    ST1025

    EVA Mid (500 Sources, 2.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s)

    ST2025-SAN

    EVA Large (2.5K Sources, 4.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s)

    ST4025

    EVA Global (5K Sources, 8.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s), Additional 2TB, 6TB Retention

    MX3025

    EVA Large (2.5K Sources, 4.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s)

    MX4025

    EVA Global (5K Sources, 8.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s), Additional 2TB, 6TB Retention

    * Upgrade involves manual data migration.

    TIBCO LogLogic H4R1 and H4R2 Appliances - Upgrade path

    H4R1/R2 Appliance

    EVA replacement

    Capacity Expansion Options

    LX1025R1

    EVA Medium (500 Sources, 2.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s)

    LX4025R1

    EVA Large (2,500 Sources, 4.5TB storage)*

    Additional 500, 2,500 or 5,000 Devices License(s)

    LX1025R2EVA Medium (500 Sources, 2.5TB storage)*Additional 500, 2,500 or 5,000 Devices License(s)
    LX4025R2EVA Large (2,500 Sources, 4.5TB storage)*Additional 500, 2,500 or 5,000 Devices License(s)
    ST2025-SANR1EVA Large (2,500 Sources, 4.5TB storage)*Additional 500, 2,500 or 5,000 Devices License(s)
    ST4025R1EVA Large/Global (2,500 Sources, 4.5TB storage)*Additional 500, 2,500 or 5,000 Devices License(s)
    ST2025-SANR2EVA Large (2,500 Sources, 4.5TB storage)*Additional 500, 2,500 or 5,000 Devices License(s)
    ST4025R2EVA Large/Global (2,500 Sources, 4.5TB storage)*Additional 500, 2,500 or 5,000 Devices License(s)

    Manual Process of Data Migration

    Due to the nature of the data migration function, there is no officially supported path to migrate data and configuration between a physical LogLogic Server and a Virtual Server for LMI. TIBCO LogLogic LMI being a Linux os based system supports the manual copying of data using commands such as Rsync. Data has to be synced manually, then several changes on the target system will need to be made to account for the data that was synced. The overall steps for this process will be outlined in this article, but due to the fact that several application-level changes have to be made, we recommend users to contact TIBCO Support in order to use this process effectively. The overall steps are as follows:

    1. Upgrade the H4/H4R1 appliance to 6.3.0 version of LMI and LSP 34 in order to minimize the manual steps needed. In the case of H4R2 the starting LMI version for these appliances is LMI 6.1.1 + LSP 32.1 which makes the upgrade steps shorter path compared to H4 and H4R1 appliances.
    2. Rsync the data between the H4 server and EVA server. As LogLogic LMI stores data in File System as files, this can be synced between physical servers and EVA appliances.
    3. Once the Rsync of the data is finished, the database needs to be updated with entries and pointers to this data.
    4. Permissions on the files depending on how the Rsync is executed may change and hence those have to be fixed recursively to support application searches.
    5. Configuration from the physical (H4/H4R1/H4R2) appliances needs to be manually exported and imported into EVA appliances.

    Note: Not all configurations can be exported manually as the application does not support it. Some configurations such as Alerts, Saved Searches, etc might be missing if the manual process of data migration is used.

    Note 1: The above-mentioned method assumes that the target server is an empty or a newly deployed server. If the target server already contains data and has been in usage, the data migration steps may overwrite the data.

    Note 2: Data Migration does not guarantee the syncing of data in real-time. There may be a certain amount of data loss during any of the above processes. Application restarts are necessary during the data migration setup which can cause downtime of the application and loss of data as well


    User Feedback

    Recommended Comments

    There are no comments to display.


×
×
  • Create New...