InfiniMetrics 5.0 contains an update to the operating system (to Ubuntu 18.04) and other infrastructure related updates. Thus, there is no direct upgrade process. Users need to deploy a new instance of InfiniMetrics 5.0 and migrate the data from the older running instance.
This guide specifies the migration process from InfiniMetrics 4.x to InfiniMetrics 5.0 while preserving data that was collected by the existing InfiniMetrics VM.
- A vCenter login with the appropriate permissions to deploy a new virtual machine.
- An instance of InfiniMetrics 4.x which will be migrated to the new InfiniMetrics 5.0 instance. If you are running an older InfiniMetrics release, upgrade to the latest 4.x release (currently 4.3.1) before migrating.
- A new VM with InfiniMetrics 5.0 installed.
- SSH access to the InfiniMetrics 5.0 instance.
- SSH access from the new InfiniMetrics 5.0 to the InfiniMetrics 4.x instance.
- The disk space allocated to the 5.0 instance shall be at least of the same size as allocated to the currently running InfiniMetrics 4.x databases.
The new VM should have at least the same storage capacity, RAM, and CPU allocations as the instance running InfiniMetrics 4.x.
- After the InfiniMetrics 5.0 OVF is deployed and the new application is running, power the virtual machine on.
- If necessary, configure your firewall to allow HTTP/HTTPS connections from the new VM to your InfiniBoxes.
- If necessary, configure your firewall/networking to allow SSH connections from the new VM to your old VM.
Log into the new InfiniMetrics 5.0 instance via SSH as root with password 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 is done, press: CTRL+b, x (Ctrl and b button simultaneously, and then the x key).
If for some reason the SSH connection is closed, re-execution of the `infinimetrics migrate_data` command will connect to the current running tmux session with the last command.
- As the script runs, the new InfiniMetrics main system list view will be populated with systems as they are added.
Once a system is displayed. you can access it via the new VM's URL using your browser. Verify that the new systems are working properly and collecting new data.
Once the script is done and the systems are all displayed (indicating successful migration), you can power off the old VM.
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 verifying 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.
If the disk size of the new VM is smaller than the existing one, a warning will be displayed by the migration procedure.
You may choose to ignore the warning and continue the migration, or abort it and increase the disk size via vCenter.
If you choose to increase the disk size then you must run the following command in the terminal once the VM is powered on again:
Restart the migration process by continuing from step 4 above.
1. Unsupported InfiniMetrics version
The migration procedure will abort if you try to upgrade from an InfiniMetrics version prior to 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 will validate that the new instance has enough disk space to move the databases from the old instance to the new one.
However the script might cause a warning to be displayed if it was launched again after it was stopped, telling you that you might not have enough space in the new instance (this is due to the process calculating the size of all systems located remotely and not reducing the size of systems already migrated).
If you are positive you had enough space when you first launched it, 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 mentioned 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, using the CTRL+C or 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 (as specified in step 5). The migration process will continue from the last system it was working on.
4. Corrupted data
If after migration and inspection of the data you found it to be corrupted or missing historical data, you can delete the specific system and migrate it again using this command:
The command will delete all data relating to that specific system from the new VM only. That includes all data collected since the migration itself and that data 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 will need to roll back to a InfiniMetrics 4.x VM:
- Power off the new InfiniMetrics 5.0 VM.
- Power on the old InfiniMetrics 4.x VM.
- Log into the new InfiniMetrics 5.0 instance via SSH as root with password nfinidat1
6. Migrating the PEM certificate
The migration process does not migrate the PEM certificate from the old InfiniMetrics instance.
After the installation of InfiniMetrics and at any point in time, one can install his PEM certificate file by