DOMOS Migration Tool
Overview
The DOMOS Migration Tool is used to migrate an existing DOMOS system to a new installation. It does not matter whether the source system is running on physical hardware or in a virtual environment.
The complete migration process is executed on the target system. Depending on the migration scenario, additional preparation steps may also be required on the source system.
The migration process is based on direct communication between the source and target systems. No additional client or server infrastructure is required.
TL;DR
The following TL;DR section is intended for experienced administrators only. Optional steps, additional explanations, and environment-specific details may be omitted for brevity.
For a complete step-by-step migration guide, including all required details and recommendations, refer to the detailed sections further below in this documentation.
-
Ensure that both systems are reachable via FQDN or IP address and that SSH access is available.
-
Create a configuration file named
domosmigration.cfgcontaining the required connection information (FQDN/IP address, username, password, etc.). -
Optional: Create a backup job on the source system if application data should also be migrated.
-
Copy the configuration file to the target system:
scp domosmigration.cfg admin@NEW-SYSTEM-IP:/tmp
- Start the migration on the target system:
ssh admin@NEW-SYSTEM-IP run_migration
- Wait until the migration process has completed and the target system reboots automatically.
Preparation of the Source System
In most cases, no special preparation is required on the source system.
The DOMOS WebUI must be reachable from the target system and login using username and password authentication must be possible.
The migration tool does not support TLS client certificate authentication. If TLS client certificates are enforced on the source system, they must be disabled before starting the migration.
If application data should also be migrated, a Backup Client job for the Backup Client must be created on the source system. The name of this job must later be specified in the migration configuration file.
Additional Requirements
Network
The source system must be reachable from the target system.
A standard configuration migration communicates with the DOMOS WebUI on port 10000. A migration from DOMOS7 to DOMOS7 uses port 11000.
If a data migration is performed, the Backup Client service port must additionally be reachable. The default Backup Client service port is 9877.
Migration Configuration File
The migration process is controlled through a configuration file.
The configuration file must be named domosmigration.cfg.
Example configuration:
[Remote]
# optional: default is admin
username = admin
# optional: default is admin
password = admin (add custom password)
fqdn = 172.16.0.222 (add FQDN/IP of source system)
# optional: default is 10000
# Attention: For a DOMOS7 to DOMOS7 Migration, use Port `11000` instead.
port = 10000
# optional: default is 5
domosversion = 6 (set domosversion of source system)
# optional: data migration
[DataMigration]
bakres=MyBakResJob
[License]
# optional: DOMOS license
filename = D202317000003.lic
The individual sections are described below.
Section: Remote
This section is mandatory and defines the connection settings for the source system.
| Parameter | Description |
|---|---|
username | Optional. Username used for login. Default: admin |
password | Optional. Password used for login. Default: admin |
fqdn | FQDN or IP address of the source system |
port | Optional. DOMOS WebUI port. Default: 10000. Attention: For a DOMOS7 to DOMOS7 Migration, use Port 11000 instead. |
domosversion | Optional. Source DOMOS version. Available number: 5, 6, 7. Add the Version of the source system. |
Section: DataMigration
This section is optional and only required when application data should also be migrated.
The migration tool downloads the BackupClient from the source system and uses it to create and restore the application backup.
| Parameter | Description |
|---|---|
bakres | Name of the BackupClient job used for the application data migration |
Section: License
This optional section allows installation of a new DOMOS license during the migration process.
The standard configuration backup already contains the existing DOMOS license. This section is therefore only required if a replacement license must be installed.
| Parameter | Description |
|---|---|
filename | Name of the license file |
Perform the Migration
The migration process consists of two steps.
Step 1: Copy Required Files
The migration configuration file and, if required, the new license file must be copied to the /tmp directory on the target system.
The recommended method is Secure Copy (scp).
The configuration file must be named domosmigration.cfg.
scp domosmigration.cfg admin@NEW-SYSTEM-IP:/tmp
scp DOMOSLIC.lic admin@NEW-SYSTEM-IP:/tmp
The /tmp directory is cleared automatically during reboot. The copied files will therefore be removed automatically after the migration process has completed.
Step 2: Start the Migration
The migration is started via SSH.
The migration command only works through the admin user as long as the root password on the target system has not been changed.
If the root password was already modified, the migration must be started directly from the target system command line as root.
Start the migration using the following command:
ssh admin@NEW-SYSTEM-IP run_migration
The migration output is displayed directly in the terminal. No interactive input is required during the migration process.
Example output:
$ ssh admin@172.16.0.23 run_migration
admin@172.16.0.23's password:
2023-04-26 11:04:39 [INFO] Login into remote system ...
2023-04-26 11:04:39 [INFO] Login ok
2023-04-26 11:04:39 [INFO] Downloading configuration backup ...
2023-04-26 11:04:41 [INFO] Download ok
2023-04-26 11:04:41 [INFO] Login into remote system ...
2023-04-26 11:04:41 [INFO] Login ok
2023-04-26 11:04:41 [INFO] Shutting down remote system ...
2023-04-26 11:04:41 [INFO] Restoring old configuration ...
2023-04-26 11:05:28 [INFO] Notice: Restoring sensor successful.
2023-04-26 11:05:28 [INFO] Notice: The database has been successfully restored.
2023-04-26 11:05:28 [INFO] Notice: Restoring management successful.
2023-04-26 11:05:28 [INFO] Error from localhost.localdomain: The node names are not configured correctly.
2023-04-26 11:05:28 [INFO] Notice: Restoring cluster successful.
2023-04-26 11:05:28 [INFO] Patching configuration ...
2023-04-26 11:05:28 [INFO] Add key system.keymap with value de
2023-04-26 11:05:28 [INFO] Add key sssd.section.ssh.ssh_use_certificate_keys.value with value True
2023-04-26 11:05:28 [INFO] Installing new license ...
2023-04-26 11:05:28 [INFO] System reboot
After the target system has rebooted successfully, the migration is complete.
During the migration, the target system adopts the network configuration of the source system.
To avoid IP address conflicts, ensure that the source system is shut down before the migrated target system becomes active on the network.