With the official General Availability release of Logmanager 4.0 comes a major modernization of the entire platform. However, for our existing customers running version 3.x, it is important to distinguish between the availability of this version for new deployments and its readiness for migrating existing production environments.

A Critical Prerequisite: Feature Parity

The core principle of our migration strategy is operational continuity. Version 4.0 was initially released with a feature set optimized for smaller organizations and newly built infrastructures.

For more complex 3.x installations, certain functional limitations currently prevent migration.

Key Limitation for Clustered Environments

Logmanager 4.0 does not yet support cluster or High Availability (HA) configurations. As a result, it is neither technically feasible nor recommended to begin migration for customers operating clustered environments until this functionality is fully available in the 4.x series.

In addition to cluster support, the following components are currently under development in version 4.0:

  • Logmanager Forwarders – Data collection from distributed networks
  • Granular RBAC – Advanced role-based access control with fine-grained permissions
  • Backup & Restore – Native configuration and data backup management directly within the interface

Our top priority for this year is to complete these features and achieve full functional parity with version 3.x.

  1. Development phase (next 6 months)
    No mass migrations will take place during this period. Our focus is on completing the missing core modules in LM4.
  2. Individual pilot projects
    Once feature parity is achieved, we will initiate controlled migrations with selected customers operating less complex topologies to validate migration scripts and ensure stability.
  3. General availability for migration
    Mass migration will only be released once LM4 fully supports all specific configurations, including clustered deployments and distributed data collection.

Migration Process: SMB Bridge Approach

Due to the transition to an entirely new database architecture, migration will be performed via export and import using external SMB storage.

  • Export: Data from Logmanager 3.x will be exported to external SMB storage.
  • Upgrade: Version 4.0 will then be installed on the existing hardware or virtual machine.
  • Re-indexing: Data will be imported from SMB storage into LM4. Please note that this process requires re-indexing into the new database structure, which is both time-intensive and I/O demanding.

To maintain maximum system performance after migration, we recommend the following approach:

  • Retain the complete historical archive on external SMB storage (to meet compliance and audit requirements).
  • Import only operationally critical data into the active Logmanager 4.0 database (e.g., the most recent 14 days).
  • If forensic analysis of older records is required, specific time ranges can be imported from SMB storage on an ad hoc basis.

Summary

Customers currently running version 3.x continue to have a stable, fully supported system. No immediate action is required.

We will inform you through standard communication channels once the features necessary for your specific architecture, particularly cluster support, are available.

For technical details about the current release, please refer to the Logmanager 4 Release Notes.