Check System Requirements

Hardware Requirements

Operating System Requirements

Network Requirements

Software Requirements

Docker Requirements

Storage Requirements

Install Docker

Configure the NodeSource Repository

Install Node.js

Remove Existing Docker-related Libraries

Configure the Docker Repository

Update System Packages

Install Docker Engine and Components

Start and Enable the Docker Service

Verify the Docker Installation

Get the INNORIX Container

Download the On-premise Package

Extract the Installation Package

Verify the Installation Directory

Deploy INNORIX

Configure the Docker Swarm Environment

Run the Server Installation

Start the INNORIX Service

Run the Hyperlink Agent

Verify the Deployment Status

Configure Your Environment

Configure Server Access

Configure the Domain

Configure Ports

Configure Environment Variables

Configure the Service

Configure Network & Storage

Configure the Network

Configure the Firewall

Configure File Storage

Configure Persistent Storage

Configure Security

Configure HTTPS

Configure the SSL Certificate

Configure Access Control

Configure Security Policies

Complete Initial Setup

Access the Web Console

Verify the Server Status

Create a Workspace

Generate an Authentication Key

Complete the Initial System Configuration

Verify Initial Configuration Completion

Verify Your Installation

Verify the Service Status

Verify the System Status

Verify Network Connectivity

Perform a File Transfer Test

Back Up & Restore

Verify Backup Targets

Back Up the System Configuration

Back Up Operational Data

Restore Procedure

Verify the Restore

Verify Backup and Restore Completion

Upgrade INNORIX

Prepare for the Upgrade

Update the Container Images

Upgrade the Services

Verify the Upgrade

Rollback Procedure

Verify Rollback Completion

Troubleshooting

Docker Installation Issues

Container Deployment Issues

Service Execution Issues

Network Connectivity Issues

License Activation Issues

Verify Logs and Analyze Issues

Verify Troubleshooting Completion

Upgrade INNORIX

INNORIX operates as a Docker container-based platform and is upgraded by applying new Container Images.

Before performing an upgrade, back up the existing operating environment, assess the service impact, and proceed with the upgrade safely.

This section describes how to prepare for an INNORIX version upgrade, update the Container Images, apply the upgraded services, and verify the upgrade.

Prepare for the Upgrade

Before starting the upgrade, verify the current operating environment and system status.

Pre-upgrade Verification

Item	Verification
Current Version	Verify the currently installed INNORIX version
System Status	Verify that the services are operating normally
Storage	Ensure sufficient space for the upgrade
Network	Verify that the Container Images can be downloaded
Backup	Verify that the system configuration and operational data have been backed up

Pre-upgrade Checklist

Perform the following tasks before the upgrade.

Back up the current INNORIX configuration.
Back up operational data.
Verify the Docker environment status.
Confirm the administrator maintenance schedule.
Review whether service interruption is required.

For stable operation, performing the upgrade during a scheduled maintenance window is recommended.

Update the Container Images

The INNORIX upgrade is performed by loading and applying the latest Container Images.

Container Image Update Procedure

Verify the Docker environment status.
Load the latest INNORIX Container Images.
Verify both the existing and new Images.
Apply the updated Images.

Verification Items

Item	Description
Image Version	Version of the new Container Image
Storage Usage	Storage used by the Images
Compatibility	Compatibility with the current environment

Notes

Do not remove the existing Images before the upgrade.
Keep the previous Images to support rollback if necessary.

Upgrade the Services

After applying the latest Container Images, replace the existing services with the new version.

During the upgrade, the existing configuration, network, and persistent storage are preserved, and only the Containers are replaced with the new version.

It is strongly recommended to back up the system configuration and operational data before performing the upgrade.

Service Upgrade Procedure

Step 1. Verify the Current Service Status

Verify the currently deployed services and their status.

bash

docker stack services exacoola

Verify that the REPLICAS value for each service (for example, node-app 3/3) is normal.

To verify individual Containers (tasks), run the following command.

bash

docker stack ps exacoola

Step 2. Load the Latest Container Images

INNORIX services are distributed as offline image packages (.tar).

Load the latest image package provided.

bash

docker load -i ./exacoola-images.tar

After loading is complete, verify that the new Images have been loaded successfully.

bash

docker images

Step 3. Upgrade the Services (Redeploy)

Redeploy the services using the newly loaded Container Images.

bash

sudo docker stack deploy -c docker-compose.yml exacoola

Docker Swarm detects the updated Images and replaces the node-app service one instance at a time using a rolling update.

The existing Volumes and operational data are preserved while only the Containers are replaced.

Step 4. Verify Service Execution

Verify that the Containers have been redeployed successfully.

bash

docker stack services exacoola

If the REPLICAS value for node-app is 3/3, the deployment is successful.

To verify the status of individual tasks and their redeployment time, run the following command.

bash

docker stack ps exacoola

Step 5. Verify the Service Logs

Verify that no errors occurred during the upgrade.

bash

docker service logs exacoola_node-app

To monitor real-time logs or display only the most recent logs, run the following command.

bash

docker service logs -f --tail=100 exacoola_node-app

You can verify the logs of other services in the same way.

bash

docker service logs exacoola_mysql

bash

docker service logs exacoola_redis

Docker Swarm-based Upgrade

INNORIX manages all services using Docker Swarm (single-node).

During the upgrade, docker stack deploy preserves the existing configuration and recreates only the Containers with the updated Images.

Preserved Components

Item	Description
Configuration	Existing service configuration is preserved
Environment	Environment variable configuration is preserved
Network	Overlay Network configuration is preserved
Volume	Persistent storage and operational data are preserved
Workspace	Workspace configuration is preserved
License	Applied license information is preserved

Post-upgrade Verification

After the upgrade is complete, verify the following.

Verify that all services have the expected REPLICAS value (for example, node-app 3/3).
Verify that the Web Console is accessible.
Verify administrator sign-in.
Verify that the Workspace is displayed correctly.
Verify that the License is applied correctly.
Verify that the Hyperlink Agent is operating normally.
Verify that file Transfer tasks can be created and executed.

Recommendations

The following practices are recommended for production environments.

Back up the system configuration and operational data before the upgrade.
Keep the previous Container Images.
Perform the upgrade during a scheduled maintenance window.
Verify the service logs after the upgrade.
Perform an actual file Transfer test to verify normal operation.

Verify the Upgrade

After the upgrade is complete, verify that the services are operating correctly.

Service Verification Items

Item	Verification
Deployment Status	Verify that the new services and Containers have been deployed successfully
Service Status	Verify that the INNORIX services are operating normally
Web Console	Verify administrator access
Configuration	Verify that the existing configuration has been preserved
File Transfer	Verify that the file Transfer functionality operates correctly

Functional Testing

After the upgrade, verify the following functions.

Administrator sign-in
Workspace information retention
User information retention
Ability to create file Transfer tasks
Successful completion of file Transfer tasks

Rollback Procedure

If issues occur after the upgrade, restore the previous version of the services using the earlier Container Images.

Before performing a rollback, verify the current service status and logs, and confirm that the previous Images are available on the server.

Rollback Procedure

Step 1. Verify the Current Service Status

Verify the currently deployed services and their status.

bash

docker stack services exacoola

To verify individual Containers (tasks), run the following command.

bash

docker stack ps exacoola

Step 2. Verify the Current Logs

Check for errors that occurred during the upgrade.

bash

docker service logs exacoola_node-app

To monitor the logs in real time, run the following command.

bash

docker service logs -f --tail=100 exacoola_node-app

Step 3. Verify the Previous Images

Verify the previous Images and Tags stored locally.

bash

docker images

Verify that the rollback target version (for example, exacoola-node:v3.1.0) is available.

Example:

text

exacoola-node    v3.2.0    (Current Version)
exacoola-node    v3.1.0    (Rollback Target)

If the previous Image is not available, load the archived image package first.

bash

docker load -i ./exacoola-images-v3.1.0.tar

Step 4. Apply the Previous Version

Update the Image Tag in docker-compose.yml for the services to be rolled back.

Since node-app and node-init use the same Image, update both services.

Example:

yaml

image: exacoola-node:v3.1.0

After saving the configuration, redeploy the services using the previous Image.

bash

sudo docker stack deploy -c docker-compose.yml exacoola

Docker Swarm detects the updated Image Tag and redeploys the services using the previous version.

The existing Volumes and operational data are preserved.

Step 5. Verify Service Execution

Verify that the Containers have been redeployed successfully with the previous version.

bash

docker stack services exacoola

If the IMAGE column displays the rollback target version (exacoola-node:v3.1.0) and the REPLICAS value for node-app is 3/3, the rollback is successful.

To verify the status of individual tasks and their redeployment time, run the following command.

bash

docker stack ps exacoola

Note
The node-init service is an initialization-only service, so a Shutdown or Complete status is expected.

Step 6. Verify the Service Logs

After the rollback, verify that the services have started without errors.

bash

docker service logs exacoola_node-app

To verify specific services, run the following commands.

bash

docker service logs exacoola_mysql

bash

docker service logs exacoola_redis

Verify Rollback Completion

Verification Item	Status
Service status verified	✓
Previous Images verified	✓
Previous version redeployed	✓
Service execution verified	✓
Log verification completed	✓