This guide describe the steps required to update LibraCyber Email Archiver from v24.1 to v26.5. For a detail description of v26.5 please refer to this page. This page describes only the migration process.
Please note that starting version 24.9 and up, the archiver does not support Kerberos.
Overview
Migrating from v24.1 to v26.5 requires deploying a new VM. The migration process will automatically transfer all data from v24.1 Archiver to v26.5 Archiver.
The expected downtime occurs only during step 6 (up to 30 minutes, depending on network speed).
Please note that:
- deferred emails queue will not be migrated. Please check for deferred emails before migrating
- after the migration the Archiver will have a different IP address (as the VM is changed). You can update the DNS or the v26.5 Archiver IP address as needed
- after the migration the connectors' cache will be reset. The first connector synchronization cycle will take longer than usual, depending on the number of archived mailboxes. Journaling emails ingestion will not be affected
- before starting the procedure, a snapshot of the v24.1 Archiver is required
Migration procedure
The migration procedure consists of 6 steps, and each step can be run at a different time.
If something goes wrong during the migration and the v26.5 Archiver is not yet operational, you can go to the v24.1 Archiver console and use option 97 to restore the functionality of the v24.1 Archiver.
Step 1: update v24.1 indexing engine
On the v24.1 Archiver, update the indexing engine to the latest version by connecting to the hypervisor console and selecting option 98. During this step, the archiving process and searches will be temporarily suspended. The maximum expected duration is 15 minutes.
Step 2: prepare v24.1 Archiver
On the v24.1 Archiver, select option 99 from the hypervisor console. This procedure will check if your Archiver can be migrated to v26.5 and provide information about the required resources for the new VM (CPU and RAM). It will also display the disks size, if different from the Archiver template. Use this information in the next step to deploy the v26.5 Archiver.
Step 3: deploy v26.5 Archiver
Deploy the v26.5 Archiver based on the resources obtained in Step 2. Run the v26.5 Archiver Wizard to configure the network and upload your license. The IP address of the v26.5 Archiver must be different from the IP address of the v24.1 Archiver.
The default password for the admin user on the v26.5 Archiver is admin, but you can change it as needed. Please note that after migration, the credentials will be the same as those from the v24.1 Archiver.
After deploying the v26.5 Archiver, take a snapshot of this VM as well.
Step 4: test connectivity
Ensure that the v24.1 Archiver is reachable from the v26.5 Archiver (e.g., on the same local network). On the v24.1 Archiver, open the firewall (how to open Archiver firewall) to allow SSH connections from the v26.5 Archiver.
Use option 100 from the v26.5 Archiver hypervisor console to test connectivity to the v24.1 Archiver. You can now decide to proceed with Step 5 or pause the procedure.
Step 5: pre-sync
Use option 100 from the v26.5 Archiver hypervisor console to run the pre-sync process. This step will transfer (copy) all data from the v24.1 Archiver to the v26.5 Archiver, leaving the v26.5 Archiver in a frozen and non-operational state.
During this step, the v24.1 Archiver remains fully operational with no downtime. You can now choose to proceed with Step 6 or pause the procedure.
Step 6: migration
Use option 100 from the v26.5 Archiver hypervisor console to execute the final step of the migration. During this step, archiving process, searches, and journaling email ingestion will be suspended.
At the end of this step, the v26.5 Archiver will become fully operational, and the v24.1 Archiver VM will be automatically powered off.
About firewall
After migration, firewall settings must be manually applied on v26.5 Archiver VM.
About local volumes
The migration of Archiver from version 24.1 to v26.5 does not support the presence of local disks.
To proceed with the upgrade, any local volumes must be removed.
Currently, the migration can be performed by following these steps:
- Create new non-local volumes (e.g., S3, Wasabi, FTP, etc.).
- Disable local volumes
- Copy or move the contents of the local volume to the remote volume.
- Remove the local volume from Archiver.
- Perform the migration from version 24.1 to v26.5.
After the migration, it will be possible (but not mandatory) to connect a local disk to the new Archiver, create a local volume, and restore data from the remote volume.