Migrating the Operavix Server from Windows to Linux

To maintain Operavix functionality when transitioning to Linux in Docker, correctly migrate data and configure the environment. This guide describes the migration process with preserving all settings and data, including connections to external systems (ClickHouse, Active Directory, etc.).

Configuring Active Directory Authentication (Kerberos)

If your system used Standard Windows Authentication, complete these steps before migration:

1. In the Operavix web interface navigate to the Authentication section.
2. Remove or disable the Standard Windows Authentication method.
3. Configure Kerberos Authentication instead. This is the only supported Active Directory integration method on Linux.

Preparing for Migration

1. Ensure the Operavix version installed on the Windows server (Server #1) matches the version planned for the Linux server (Server #2), including all components and patches.
2. On Server #1, create a full backup of the directory: C:\ProgramData\Operavix\.
3. Stop the Operavix service using the Services console from Windows.
4. Change the service startup type to Disabled to prevent accidental startup after migration.

Installing and Preparing the Linux Server

1. On Server #2, perform the initial Operavix application launch following the installation instructions. This initializes directory structures and Docker volumes.
2. After the initial launch, stop the Operavix service.
   sudo docker service rm operavix-app
   

3. Clear the application data Docker volume.
   sudo rm -rf /var/lib/docker/volumes/operavix-app-data/_data/*
   

Migrating Data

1. From the Server #1 backup, extract the databases and secret_key directories.
2. Create an archive (e.g., Operavix.tar) containing these directories.
   tar -cvf Operavix.tar databases secret_key
   

3. Transfer the archive to Server #2 using scp.
   scp "Operavix.tar" user@linux-server:/tmp/
   

4. Extract the archive into the target Docker volume.
   sudo tar -xvf /tmp/Operavix.tar -C /var/lib/docker/volumes/operavix-app-data/_data/
   

5. Verify correct volume structure. The directory must contain databases/ and secret_key/.
   ls -la /var/lib/docker/volumes/operavix-app-data/_data/
   

6. The application inside the container runs under a user with UID 1001. Assign the correct owner.
   sudo chown -R 1001:1001 /var/lib/docker/volumes/operavix-app-data/_data/
   sudo chown -R 1001:1001 /var/lib/docker/volumes/operavix-app-log/_data/
   

Completing the Migration

1. Launch the application on Linux by performing a standard Operavix startup per the installation instructions.
2. Confirm the application is running. The application container must show Running status.
   docker-compose ps
   

3. Verify data access, settings, and ClickHouse connectivity.
4. Confirm users can authenticate (including via AD if configured).
5. After confirming stable Linux operation, remove the application from Server #1 and ensure the service cannot start.