This guide describes the migration process from InfiniMetrics 4.x to InfiniMetrics 5.0 or above while preserving the data that was collected by the existing InfiniMetrics VM.
InfiniMetrics versions 5.0 and above contain an update to the operating system (Ubuntu 18.04) and other infrastructure related updates. There is no direct upgrade process from versions earlier than 5.0. To upgrade, follow the instructions in this guide to deploy a new instance of InfiniMetrics 5.0 and then migrate the data from the older running instance. Then you can upgrade from version 5.0 to a later version.
- A vCenter login with the appropriate permissions to deploy a new virtual machine.
- An instance of InfiniMetrics 4.x to be migrated to the InfiniMetrics instance of the newer version. If you are running an InfiniMetrics release earlier than 4.0, upgrade to the latest 4.x release (currently 4.3.1) before migrating.
Disk space allocated to the 5.0 instance that is at least the same size as that allocated to the currently running InfiniMetrics 4.x databases.
If the disk size of the new VM is smaller than the existing one, a warning message is displayed during the migration procedure described below.
You can abort the migration, and increase the disk size via vCenter.
After you increase the disk size, run the following command in the terminal after the VM is powered on again:
Then rerun the migration procedure starting from step 5.
Follow the installation instructions to deploy a new InfiniMetrics 5.0 VM.
The new VM must have at least the same storage capacity, RAM, and CPU allocations as the instance running InfiniMetrics 4.x.
- Ensure that your firewall is configured to allow HTTP/HTTPS connections from the new VM to your InfiniBoxes.
- Ensure that your firewall/networking is configured to allow SSH connections from the new InfiniMetrics 5.0 VM to your old InfiniMetrics 4.x VM.
Log in to the new InfiniMetrics 5.0 instance via SSH. Use the following credentials:
- For the User, enter root
- For the Password, enter the value set for your InfiniMetrics password. If a value has not been set, enter nfinidat1
Run the following commands:
The migrate_data command will instantiate inside a new tmux session. tmux is used to keep the command running regardless of SSH/TTY connection.
When the command terminates for any reason, the tmux session will remain active in order to allow the audit and review of the log and action information.
To terminate the tmux session after it completes, press: CTRL+b, x (Ctrl and b button simultaneously, and then the x key).
If for some reason the SSH connection is closed, re-execute the `infinimetrics migrate_data` command to connect to the current running tmux session with the last command.
As the script runs, the new InfiniMetrics main system list view is populated with systems as they are added.
Once a system is added, you can display it in your browser via the new VM's URL. Verify that the new systems are working properly and collecting new data.
If you see any irregularity with the new InfiniMetrics, restart InfiniMetrics 4.x and shut down the new version. Contact Infinidat support.
- Configure InfiniMetrics Call Home on the new instance. If needed, configure the PROXY and/or firewall rules.
- After the script is done, the systems are all displayed (indicating successful migration), and you have verified that the new InfiniMetrics runs properly, power off the InfiniMetrics 4.x VM. It is recommended to keep the VM for some time before deleting it.
- After the migration to InfiniMetrics 5.0 is complete, you can upgrade to a later version.
1. Unsupported InfiniMetrics version
The migration procedure aborts if you try to upgrade from an InfiniMetrics version earlier than v4.x.
You must first upgrade your existing InfiniMetrics instance to v4.x (latest is v4.3.1), and then migrate it to v5.0 as described above.
2. Not enough space on new VM
The migration process validates that the new instance has enough disk space to move the databases from the old instance to the new one.
However, if the script was launched again after some systems were already migrated, a warning message might tell you that the new instance does not have enough space. This is due to the calculation of the size of all systems located remotely without reducing the size of systems already migrated.
If you are sure enough space was allocated when you launched the migration process, you can ignore the warning and continue with the migration. Otherwise, consider increasing the VM disk size and running the
infinimetrics expand-disk command, as described in the Prerequisites section above.
3. Migration procedure killed before it finished
If the migration is killed for some reason, it is possible to run it again (on the same VM or on a new one). This will not cause any data loss or data duplication.
You can stop the migration anytime by pressing CTRL+C or by sending it a SIGINT/SIGKILL signal. This will stop the migration and delete the system it was working on from the new VM.
You can run the migration again anytime starting from step 5. The migration process will continue from the last system it was working on.
4. Corrupted data
If, after migration and inspection of a system's data, you found it to be corrupted or missing historical data, you can delete the specific system and migrate it again using this command:
This command deletes all data from the new VM relating to that specific system, including the data collected after the migration that might not be available from the old VM if the old VM was stopped after the migration.
5. Rolling back to the old VM
In the unlikely event that you need to roll back to a InfiniMetrics 4.x VM:
- Power off the new InfiniMetrics 5.0 (or above) VM.
- Power on the old InfiniMetrics 4.x VM.
6. Migrating the PEM certificate
The migration process does not migrate the PEM certificate from the old InfiniMetrics instance.
At any time after the installation of InfiniMetrics, you can install your PEM certificate file by