When to Migrate Data
The primary purpose of the data migration solution is to migrate log data and configuration settings from one LogLogic LMI appliance or LogLogic EVA to another.
It is particularly useful when upgrading from earlier LogLogic appliance models
to newer models.
When migrating data, the following network connection configurations are supported:
- eth0 to eth0
- bond0 to bond0
- split mode (eth0 continues to collect data during migration from eth1 to eth1)
Important: Do not perform backup or restore operations when data migration is in progress.
Important considerations
- Before performing data migration from LogLogic MX Appliance models to an LX4025R1 appliance, you must increase the global data retention on LX4025R1 to match that of the source LogLogic MX Appliance.
- When data migration is in progress, do not run any commands to enable or disable HA.
- With data migration enabled on the source and destination appliances, after data migration is complete, you cannot:
- Use Advanced Features on the destination appliance.
- Change the Advanced Features setting (enable or disable) on the source and destination appliances.
- After migrating data from a source appliance that does not support Advanced Features, an error might be displayed when using Advanced Features on the destination appliance. In such a scenario, you must reinstall LogLogic LSP on the destination appliance.
Supported Data Migration Paths
In case of LogLogic EVA, migration can be performed only from one LogLogic EVA to another. The following table lists the supported migration paths for LogLogic LMI appliances:
| From: H4R1 or H4R2 appliances | To: H5 appliances |
|---|---|
| LX1025R1 or LX1025R2 | LX1035 |
| LX4025R1 or LX4025R2 | LX4035 |
| ST4025R1 or ST4025R2 | ST4035 |
| ST2025-SANR1 or ST2025-SANR2 | ST2035-SAN |
Data Migration on High Availability Appliances
Data migration is automatically performed whenever you configure failover on an appliance. This migration is necessary to ensure both appliances’ data is in sync. For more information and procedures for failover, see Failover.
Note: Running Data Retention during data migration might slow down migration processing. Turning off Data Retention during data migration, might reduce the total migration time.