Migration Prerequisites¶
Before you begin the migration process, complete the following steps to ensure a smooth and secure transition:
- Administrative access
Confirm that you have administrative access to both source (MSR 2.9 and MSR 3.1) and target (MSR 4.x) environments to read all source data and configure the destination from your migration workstation.
- Backup
Perform a full backup of existing data to prevent any data loss in case of a misstep:
- MSR 4 installation
Complete the following tasks to prepare the target environment for migration:
Verify that the system meets all prerequisites. See Prerequisites.
Install MSR 4 using the steps in the Install MSR with High Availability.
Configure authentication as described in the Authentication Configuration.
- Storage
Ensure that the target system has sufficient storage capacity to accommodate all migrated artifact. The storage must be separate from MSR 2.9 or MSR 3.1.
The PostgreSQL database must have enough space for the following:
Current Enzi RethinkDB
Current MSR RethinkDB
Plus 25% overhead
The BLOB storage must have enough space for the following:
Current used storage
Extra space for new images, based on your requirements
Plus at least 5% overhead for working space
- Migration workstation
Set up a dedicated migration workstation to manage the migration process. This workstation must have:
Linux operating system.
Installed the following tools:
A container runtime, either:
RethinkDB — Install the version that matches your source MSR. To determine the correct RethinkDB version, refer to the release notes:
Access to the following databases:
PostgreSQL — configured as part of the MSR 4 deployment.
Enzi — included in MSR 2.9 (through MKE) or directly in MSR 3.1.
RethinkDB — used in both MSR 2.9 and MSR 3.1 deployments.