Skip to main content

Migrate to v3

Migrate from OIBus v1 and v2 into the new OIBus v3 version with our migration tool and a few manuel steps.

Download specific version​

OIBus version

The migration tool writes directly into the database of OIBus v3.9.6. It refuses to run on a data folder initialized by another OIBus version: install OIBus v3.9.6 from one of the links below. You can update OIBus to a later version once the migration is done.

Migration steps​

  1. Stop the OIBus service.

    tip

    You can zip the data folder, or at least the configuration file oibus.json and its keys as a backup.

  2. Install OIBus v3.9.6. Be careful to specify the same data folder. Check that OIBus v3 run properly by login on http://localhost:2223 with admin / pass. If everything works, go on with the next step.

  3. Stop OIBus v3.

  4. Copy the migration tool in the OIBus binary folder.

  5. Run the OIBus migration tool. Be sure to specify the appropriate data folder.

Windows command

oibus-upgrade.exe --config D:\OIBusData

Linux / macOS command

./oibus-upgrade --config /usr/oibus/OIBusData
  1. Start OIBus v3.
tip

The file upgrade-journal.log contains the logs of the migration.

What is migrated
  • Engine settings, IP filters and the admin user (it replaces the default admin user of OIBus v3).
  • Scan modes used by the South connectors.
  • South connectors and their points. Points of OPC UA, OPC HDA, Modbus and ADS connectors are gathered into groups, one per scan mode. The overlap of history connectors becomes a negative start time offset.
  • The last completed instant of history South connectors, and the files already handled by folder scanners preserving their files.
  • North connectors, their subscriptions, and the data waiting in their cache, error and archive folders.