Data Storage (on a virtual platform)

If you run the device as a virtual appliance, you can migrate the Flowmon database storage to a different disk.

To migrate storage:

1. Select the desired disk from the drop-down menu. Click Rescan to update the list of available disks if needed.
2. Click Save to confirm your selection. The system will check the disk to ensure it is suitable for migration. During this check, the first 512kB of the selected disk will be overwritten, destroying any existing partition table.
3. After successful verification, a popup will confirm the disk is ready for migration.

Until the device is restarted, you can cancel the migration at any time by clicking Cancel migration or by reselecting the original storage. If migration is not canceled, the disk will be formatted to the XFS filesystem during the next reboot, and all data will be copied from the original storage. All existing files and directories on the selected disk will be deleted during migration. The reboot may take significantly longer than usual.

If migration completes successfully, the system will use the new disk for Flowmon database storage. If an error occurs, the system will continue using the original storage.

Automatic resizing of data storage (Flowmon 12.5.4 and newer)

Starting from Flowmon 12.5.4, database storage is automatically resized to use the maximum available space on the underlying disk after boot. This applies to database storage located on the same disk as the system (Virtual Probe) in addition to database storage located on a separate disk (Virtual Collector). Automatic resizing does not work on systems without an EFI partition.

To automatically resize the data storage, first power off the Flowmon device. Then, resize the disk in the hypervisor and power on the Flowmon device.

To verify if automatic resizing is supported on your Flowmon device, connect through SSH and run the following command:

blkid -L EFI &>/dev/null && echo "Automatic resizing will work." || echo "Automatic resizing will not work."