INNORIX On-premise Deployment and Management

Check System Requirements

Before installing INNORIX On-premise, verify that the server environment meets the requirements.

This section describes the operating system, Docker, network, and storage requirements needed to install and operate INNORIX.

Hardware Requirements

The following hardware environment is recommended for operating INNORIX On-premise.

Minimum Specifications

Recommended Specifications

ℹ️ Actual system resource requirements may vary depending on file transfer volume, number of concurrent users, file processing scale, and the operating environment.

Operating System Requirements

INNORIX On-premise supports the following Linux operating system environments.

Network Requirements

The INNORIX server must be able to communicate reliably with clients and connected target systems.

Check the following items before installation.

Server IP Address

• Verify the IP address of the server where the INNORIX service will run
• Apply that IP address when configuring Docker Swarm.

Network Connection

• Configure the access path according to the internal or external network environment.
• The environment must allow communication with file transfer target systems.

Firewall Configuration

• Ports required for INNORIX service operation (80, 443, 8077) must be allowed by the firewall policy.

Software Requirements

The following software environment is required to install INNORIX On-premise.

Docker Requirements

INNORIX runs in Docker Containers and requires the following Docker environment.

Before installing Docker, verify that existing Docker-related packages or Container Runtime environments will not cause conflicts.

Storage Requirements

For INNORIX operation, it is recommended to separate the system area from the file storage area.

System Area

Purpose:

• Docker installation files
• INNORIX Container
• Service configuration files
• Log data

Install Docker

INNORIX runs in Docker Containers.

This section configures the Docker runtime environment for INNORIX deployment.

Before installing Docker, configure the Node.js environment, install Docker-related packages, and then enable the Docker service.

Configure the NodeSource Repository

Configure the NodeSource Repository to install Node.js.

Run the following commands according to the operating system environment.

RHEL-based Linux

Install the curl package before configuring the NodeSource Repository.

sudo dnf install -y curl

Add the NodeSource Repository.

curl -fsSL https://rpm.nodesource.com/setup_22.x | sudo bash -

Debian-based Linux

Install the curl package.

sudo apt install -y curl

Add the NodeSource Repository.

curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -

Install Node.js

After the NodeSource Repository is configured, install Node.js.

The INNORIX installation environment uses Node.js 22.x.

RHEL-based Linux

sudo dnf install -y nodejs

Debian-based Linux

sudo apt install -y nodejs

Remove Existing Docker-related Libraries

If existing Docker or Container Runtime-related packages are installed, remove them before installing Docker to prevent conflicts.

RHEL-based Linux

sudo dnf remove -y podman buildah docker docker-common docker-selinux docker-engine

Debian-based Linux

sudo apt remove -y docker docker-engine docker.io containerd runc

Configure the Docker Repository

Add the official Docker Repository so the latest Docker Engine packages can be installed.

RHEL-based Linux

Install the dnf plugin required to add the Docker Repository.

sudo dnf -y install dnf-plugins-core

Add the official Docker Repository.

sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo

Debian-based Linux

Create the key storage path for Docker Repository authentication.

sudo mkdir -p /etc/apt/keyrings

Add the Docker GPG Key.

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg

Add the Docker Repository.

echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

Update System Packages

Update system packages to the latest versions before installing Docker.

RHEL-based Linux

sudo dnf update

Debian-based Linux

sudo apt update

Install Docker Engine and Components

Install the core components required to run Docker.

Components to install:

• Docker Engine
• Docker CLI
• containerd
• Docker Buildx Plugin
• Docker Compose Plugin

RHEL-based Linux

sudo dnf install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

Debian-based Linux

sudo apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin

Start and Enable the Docker Service

Start the Docker service and configure it to start automatically after system reboot.

sudo systemctl enable --now docker

Verify the Docker Installation

Verify that Docker was installed successfully.

Check the Docker version.

docker --version

Check the Docker Compose version.

docker compose version

If the version information is displayed correctly, the Docker environment setup is complete.

Get the INNORIX Container

After the Docker environment is configured, download the INNORIX On-premise package and prepare the installation environment for deployment.

This section covers downloading the INNORIX installation package, extracting it, and configuring the installation directory.

Download the On-premise Package

Download the INNORIX On-premise installation package.

The downloaded package includes Docker configuration files and installation scripts required to run the INNORIX service.

Package Download URL

wget https://innorix.com/package/INNORIX-ONPREM-PACKAGE.tar.gz

After the download is complete, verify that the file was saved correctly.

ls -lh INNORIX-ONPREM-PACKAGE.tar.gz

Extract the Installation Package

Extract the downloaded On-premise package.

Extract the package.

tar -xzf INNORIX-ONPREM-PACKAGE.tar.gz

After extraction, move to the generated INNORIX installation directory.

cd INNORIX-ONPREM-PACKAGE/

Verify the Installation Directory

After extraction is complete, the files required for INNORIX deployment are created.

Check the installation directory structure.

ls -la

Main configuration files:

Deploy INNORIX

After the Docker environment and INNORIX installation package are ready, deploy the INNORIX service.

This section describes Docker Swarm configuration, running the installation script, starting the INNORIX service, and running the Hyperlink Agent.

Configure the Docker Swarm Environment

Configure the server environment where the INNORIX Container will run.

Move to the installation directory.

cd INNORIX-ONPREM-PACKAGE/

Open the Docker Compose configuration file and change the server IP address to match your environment.

sudo nano docker-compose.yml

Configuration items:

Save the file after completing the configuration changes.

Run the Server Installation

Run the INNORIX installation script to configure the Container and service environment.

Run the following command from the installation directory.

sudo bash ./install.sh

The installation script performs the following tasks.

• Install the INNORIX Container
• Apply the Docker environment configuration
• Prepare the service runtime environment
• Apply the required settings

After installation is complete, start the INNORIX service in the next step.

Start the INNORIX Service

After installation is complete, start the entire INNORIX system.

Run the following command.

sudo bash ./start.sh

After startup is complete, the INNORIX Container runs and the Web Console becomes accessible.

Run the Hyperlink Agent

Run the INNORIX Hyperlink Agent.

The Hyperlink Agent is the Agent program used to operate the INNORIX service.

Start the Agent

/opt/INNORIX/INNORIX_Exacoola start

Stop the Agent

/opt/INNORIX/INNORIX_Exacoola stop

After starting the Agent, verify that it is operating normally.

Verify Deployment Status

After the INNORIX service deployment is complete, verify its running status.

Items to check:

After deployment completes successfully, proceed to the next step, initial server setup.

Configure Your Environment

After INNORIX deployment is complete, configure the access environment and service operation settings to match the installed server environment.

This section describes how to configure the INNORIX server access environment, domain, ports, environment variables, and service settings.

Configure the Server Access Environment

After INNORIX installation is complete, you can access the Web Console through the server IP address specified during Docker Swarm configuration or through localhost.

After installation, access the service using the following address format.

http://IP_ADDRESS

or

http://localhost

The access address is based on the server IP address configured in the docker-compose.yml file.

Server Access Checklist

When server access is successful, the INNORIX initial screen appears, after which you can configure the system using an administrator account.

Domain Configuration

In production environments, using a domain instead of an IP address is recommended for reliable service access and HTTPS.

When configuring a domain, map the domain to the INNORIX server IP address in the DNS environment.

Example:

After domain configuration is complete, users can access the service as follows.

https://domain

If you use a domain, you can apply an SSL certificate later during the security configuration step.

Port Configuration

Port settings appropriate for the network environment are required to operate the INNORIX service.

Port settings are managed according to the Docker Swarm environment and server firewall policies.

Items to check:

When configuring ports, check the following environment settings.

• Server firewall policy
• Network security appliance policy
• Internal access control policy
• External system integration environment

Configure Environment Variables

The INNORIX service manages operating environment information through Docker environment variables.

Environment variables are configured through the Docker Compose configuration file.

Main configuration items:

After changing the configuration file (docker-compose.yml), redeploy with docker stack deploy to apply the changes.

Service Configuration

INNORIX manages service components using Docker Swarm.

Service configuration file:

docker-compose.yml

The Docker Compose configuration includes the following items.

After changing the configuration, restart the INNORIX service to apply the changes.

After completing the service configuration, check the following items.

• Whether the Container is running normally
• Whether the Web Console is accessible
• Whether the service status is normal

Configure Network & Storage

For reliable operation in large-file transfer environments, network connectivity and storage configuration are important for INNORIX.

This section describes the network environment, firewall settings, file storage area, and persistent storage configuration required to operate the INNORIX service.

Network Configuration

INNORIX requires a reliable network environment for file transfers between servers and user access.

Configure an internal or external network environment according to the installation environment.

Network Configuration Items

Network Checklist

Check the following items before installation.

• Whether the INNORIX server can communicate with connected target systems
• Whether the server IP address is configured correctly
• Whether there is network latency or packet loss
• Whether external Repositories and the Docker environment are accessible

For reliable file transfer performance, ensure sufficient network bandwidth for the file transfer environment.

Firewall Configuration

Server and network firewall policies must be configured to operate the INNORIX service.

When configuring the firewall, check the following environment settings.

• Linux OS firewall settings
• Internal network firewall policies
• Security appliance access policies
• Cloud environment security group settings

Firewall Configuration Items

If a required Port is blocked, Web Console access or file transfer functions may not operate correctly.

File Storage Configuration

Because INNORIX uses memory-based file transfer, no separate workspace is required to temporarily store files during transfer.

Storage is used to store configuration information, logs, and service data required for system operation.

Recommended File Storage Configuration

Storage Configuration Considerations

• Ensure storage space for system operation data and logs.
• It is recommended to store operation data in reliable Persistent Storage.
• Back up system configuration information and log data regularly.
• Monitor disk usage in the production environment regularly to maintain reliable service operation.

Persistent Storage Configuration

In a Docker Container environment, Persistent Storage must be configured so data is retained when Containers are deleted or recreated.

Connect a Docker Volume or Bind Mount to retain service data.

Persistent Storage Targets

Configure Security

INNORIX requires security configuration to provide secure file transfer services in enterprise environments.

This section describes how to configure HTTPS, SSL certificates, access control, and security policies required in production environments.

HTTPS Configuration

HTTPS is recommended for the INNORIX Web Console and service access environment.

Applying HTTPS encrypts communication between users and the INNORIX server, enabling secure service operation.

HTTPS Configuration Items

HTTPS Setup Procedure

1. Prepare a domain appropriate for the production environment.
2. Obtain an SSL certificate.
3. Apply the certificate files to the server environment.
4. Restart the INNORIX service.
5. Verify HTTPS access.

SSL Certificate Configuration

SSL certificates are used to verify the trustworthiness of the INNORIX server and protect communication between users and the server.

SSL Certificate Configuration Items

SSL Certificate Checklist

• Check the certificate validity period
• Verify that the service domain matches the certificate domain
• Check certificate file permissions
• Establish a certificate renewal policy

If the SSL certificate expires, HTTPS access errors may occur, so regular management is required.

Access Control Configuration

INNORIX maintains system security by managing administrator and user access.

When configuring access control, manage user permissions and access scope.

Access Control Items

Recommended Security Settings

• Manage administrator accounts separately
• Change the initial password
• Remove unnecessary user accounts
• Apply the principle of least privilege

Security Policy Configuration

Configure security settings for the INNORIX operating environment according to enterprise security policies.

Security Policy Items

Production Environment Recommendations

Server Security

• Apply the latest security patches
• Disable unnecessary services
• Restrict administrator access permissions

Network Security

• Apply firewall policies
• Allow access only from approved networks
• Use HTTPS for external access

Data Security

• Restrict access permissions for important configuration files
• Apply a backup policy for operation data
• Perform log monitoring

Complete Initial Setup

After INNORIX deployment is complete, access the Web Console and perform the initial system setup.

This section describes checking server status after installation, administrator login, Workspace creation, and initial operating environment configuration.

Access the Web Console

After INNORIX installation is complete, perform the initial system setup through the Web Console.

Use the server IP address specified during Docker Swarm configuration or localhost as the access address.

Access URL:

http://IP_ADDRESS

or

http://localhost

If access is successful, the INNORIX initial screen is displayed.

If you cannot connect, check the following items.

Check Server Status

After accessing the Web Console, verify that the system is ready.

Checking server status allows you to verify whether the INNORIX service is running and whether the initial configuration is complete.

Items to Check

If all statuses are normal, proceed to the administrator login step.

Log In to the Administrator Account

After verifying server status, log in with the administrator account.

Initial administrator account information:

Recommended Tasks After Administrator Login

For security, the following actions are recommended after the first login.

• Change the initial administrator password
• Manage administrator account information
• Configure user permission policies
• Register additional operations administrators

Create a Workspace

Create a Workspace to use INNORIX features.

A Workspace is the primary workspace for managing file transfer tasks and system configuration in the INNORIX operating environment.

Workspace Creation Procedure

1. Log in with the administrator account.
2. Go to the Workspace creation menu.
3. Enter the Workspace information.
4. Complete Workspace creation.

Workspace Configuration Items

Generate an Authentication Key

Generate an authentication key in the Workspace to activate the license.

The generated authentication key is used during the license issuance process.

Authentication Key Generation Procedure

1. Complete Workspace creation
2. Generate an authentication key
3. Copy the generated Authentication Key
4. Use it on the license issuance page

Authentication Key Management Precautions

• Manage the authentication key so it is not exposed externally.
• Store it securely after license issuance is complete.
• Follow the reissuance procedure if necessary.

Initial System Configuration

After completing the initial setup, configure the basic system settings to match the operating environment.

Main configuration items:

Verify Initial Setup Completion

Verify Your Installation

After INNORIX installation and initial setup are complete, verify that the system operates normally.

This section verifies installation completion by checking service status, system status, network connectivity, and file transfer tests.

Check Service Status

Verify that the INNORIX service is running normally.

Check the status of each service running in Docker.

Items to Check

Verification Details

Normal status:

• Container is running normally
• No service errors
• Hyperlink Agent is operating normally
• Web Console is accessible

If there is a problem with service status, check the Docker Container logs and system logs.

Check System Status

Verify that the INNORIX operating environment is configured correctly.

System Check Items

Items to Verify

After installation is complete, check the following conditions.

• Whether system resources are insufficient
• Whether sufficient Storage free space is available
• Whether the environment required to run the service is operating normally
• Check for potential operational issues

Especially in large-file transfer environments, Storage usage and available Disk space must be managed continuously.

Verify Network Connectivity

INNORIX requires reliable network connectivity for file transfers between servers and user access.

After installation, verify the network connection status.

Network Check Items

Verification Method

Check the following items.

• Whether the configured IP address or domain is accessible
• Whether firewall policies are applied correctly
• Whether the service Port is accessible
• Whether communication with connected target systems is possible

File Transfer Test

After installation is complete, perform an actual file transfer test to verify that INNORIX functions operate normally.

Test Procedure

1. Access the Web Console with the administrator account
2. Prepare a test file
3. Create a file transfer task
4. Connect the target system
5. Run the file transfer
6. Check the transfer result

File Transfer Check Items

Normal Operation Criteria

When installed correctly:

• File transfer tasks can be created
• Target connection operates normally
• Transfer completion status can be checked
• Transfer results and logs can be checked

Back Up & Restore

The INNORIX operating environment requires a regular backup policy to prepare for system failures, server changes, and operational data loss.

This section describes the procedures for backing up system configuration information and data required for INNORIX operation and restoring them if a failure occurs.

Identify Backup Targets

Before performing a backup, identify the backup targets that must be managed in the INNORIX operating environment.

Backup targets are divided into system configuration information and operation data.

Backup Targets

Pre-backup Checklist

Check the following items before backup.

• Whether sufficient backup storage space is available
• Verify access permissions for files to be backed up
• Check the current INNORIX service status
• Check the backup file storage location

Back Up System Configuration

A system configuration backup stores the configuration information required to restore the INNORIX service to the same environment.

System Configuration Backup Targets

System Configuration Backup Procedure

1. Check the INNORIX installation directory
2. Back up Docker Compose and environment configuration files
3. Move the backup files to the backup storage location
4. Verify that the backup files were created successfully

Recommendations

• Perform a backup before major configuration changes
• Store backups in a location separate from the production server
• Restrict access permissions to backup files
• Manage change history

Data Backup

Data backup protects important data generated during INNORIX operation.

Data Backup Targets

Data Backup Considerations

• Consider backup time based on data volume
• Minimize impact on the production environment
• Apply a regular backup policy
• Verify data integrity after the backup is complete

Restore Procedure

If a failure occurs or system reconfiguration is required, restore the INNORIX environment using backup data.

Preparation Before Restore

Check the following items before performing a restore.

Restore Procedure

1. Check the INNORIX service status
2. Stop the service if necessary
3. Restore system configuration files
4. Restore data
5. Restart the service
6. Verify normal operation

Verify the Restore

After restoration is complete, verify that the system and services operate normally.

Restore Check Items

Restore Completion Criteria

If the restore completes successfully, check the following items.

• Web Console is accessible
• Administrator login works normally
• Existing settings are preserved
• Workspace and user information can be checked
• File transfer functions operate normally

Verify Backup and Restore Completion

Upgrade INNORIX

INNORIX runs in Docker Containers and is upgraded by applying a new version of the Container Image.

Before upgrading, perform a backup to protect the existing production environment, check the service impact, and proceed safely.

This section describes preparation for an INNORIX version upgrade, updating the Container Image, applying it to the service, and validating the upgrade.

Prepare for the Upgrade

Before proceeding with the upgrade, check the current operating environment and system status.

Pre-upgrade Check Items

Pre-upgrade Preparation

Perform the following tasks before upgrading.

• Back up the current INNORIX configuration
• Back up operation data
• Check the Docker environment status
• Check the administrator maintenance schedule
• Review whether service downtime is required

For a reliable upgrade, it is recommended to perform the work during a maintenance window in production environments.

Update the Container Image

INNORIX is upgraded by loading and applying the latest Container Image.

Container Image Update Procedure

1. Check the Docker environment status
2. Load the latest INNORIX Container Image
3. Check the existing Image and the new Image
4. Apply the Image to be updated

Items to Check

Precautions

• Deleting the existing Image before the upgrade is not recommended.
• Keep the previous Image for rollback if a problem occurs.

Upgrade the Service

After applying the latest Container Image, replace the existing service with the new version.

During the upgrade, existing environment settings, network configuration, and Persistent Storage are preserved; only the Container is replaced with the new version.

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

Service Upgrade Procedure

Step 1. Check the Current Service Status

Check the currently deployed services and their running status.

docker stack services exacoola

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

To check individual Containers (tasks), use the following command.

docker stack ps exacoola

Step 2. Apply the Latest Container Image

The INNORIX service is deployed using offline image (.tar) files.

Load the latest image file provided to you.

docker load -i ./exacoola-images.tar

After loading is complete, verify that the new Image was stored successfully.

docker images

Step 3. Upgrade the Service (Redeploy)

Redeploy the service using the latest loaded Container Image.

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

Docker Swarm detects the changed Image and replaces the node-app services one at a time in sequence (rolling update).

Existing Volumes and operation data are preserved while only the Container is replaced.

Step 4. Verify Service Operation

Verify that the Container was redeployed successfully.

docker stack services exacoola

If REPLICAS for node-app is displayed as 3/3, the service is operating normally.

To check the status and redeployment time for each task, use the following command.

docker stack ps exacoola

Step 5. Check Service Logs

Check the logs to verify that no errors occurred during the upgrade.

docker service logs exacoola_node-app

To view real-time logs and only the most recent logs, use the following command.

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

Logs for other services can be checked in the same way.

docker service logs exacoola_mysql

docker service logs exacoola_redis

Docker Swarm-based Upgrade

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

During an upgrade, docker stack deploy recreates Containers by applying only the changed Image while preserving the existing configuration.

Preserved Configuration Items

Post-upgrade Checklist

After the upgrade is complete, check the following items.

• Verify that REPLICAS for all services are normal (node-app 3/3)
• Verify normal Web Console access
• Verify administrator login
• Verify that the Workspace can be retrieved normally
• Verify that the License is applied correctly
• Verify that the Hyperlink Agent operates normally
• Verify that file transfer tasks can be created and run

Recommendations

The following practices are recommended in production environments.

• Back up system configuration and operation data before upgrading
• Keep the existing Container Image
• Perform the upgrade during a maintenance window outside business hours
• Check service logs after the upgrade is complete
• Verify normal operation by performing an actual file transfer test

Verify the Upgrade

After the upgrade is complete, verify that the service operates normally.

Service Check Items

Functional Test

After the upgrade, check the following functions.

• Whether administrator login works normally
• Whether Workspace information is preserved
• Whether user information is preserved
• Whether file transfer tasks can be created
• Verify file transfer completion status

Rollback Procedure

If a problem occurs after an upgrade, you can restore the service to the previous state using the previous version of the Container Image.

Before performing a rollback, check the current service status and logs, and verify that the previous version of the Image exists on the server.

Rollback Procedure

Step 1. Check the Current Service Status

Check the currently deployed services and their running status.

docker stack services exacoola

To check individual Containers (tasks), use the following command.

docker stack ps exacoola

Step 2. Check the Current Logs

Check for errors that occurred during the upgrade.

docker service logs exacoola_node-app

To view real-time logs, use the following command.

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

Step 3. Check the Previous Version Image

Check the previous version Images and Tags stored locally.

docker images

Verify that the rollback target version (for example, exacoola-node:v3.1.0) exists in the list.

Example)

exacoola-node    v3.2.0    (current version)
exacoola-node    v3.1.0    (rollback target)

If the previous version Image is not in the list, first load the saved image tar file.

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

Step 4. Apply the Previous Version

In docker-compose.yml, change the Image Tag for the service to be reverted to the previous version.

Because node-app and node-init use the same Image, change both services.

Example)

image: exacoola-node:v3.1.0

After saving the configuration, redeploy the service using the changed Image.

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

Docker Swarm detects the changed Image Tag and redeploys the service to the previous version.

Existing Volumes and operation data are preserved.

Step 5. Verify Service Operation

Verify that the Container was successfully redeployed to the previous version.

docker stack services exacoola

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

To check the status and redeployment time for each task, use the following command.

docker stack ps exacoola

ℹ️ The node-init service is used only for initialization, so it is normal for it to appear with a Shutdown or Complete status.

Step 6. Check Service Logs

After rollback, verify that the service starts without errors.

docker service logs exacoola_node-app

To check only a specific service, use the following command.

docker service logs exacoola_mysql

docker service logs exacoola_redis

Verify Rollback Completion

Troubleshooting

To quickly identify and resolve issues that may occur during INNORIX installation and operation, this section provides troubleshooting methods for major issue types.

This section describes methods for troubleshooting Docker installation, Container deployment, service operation, network connectivity, license activation, and log analysis.

Docker Installation Issues

During Docker installation, package conflicts, Repository configuration errors, or Docker service startup issues may prevent installation from completing successfully.

Major Symptoms and Causes

Check Docker Status

Check the Docker service status.

systemctl status docker

Check the Docker version.

docker --version

Check the Docker Compose version.

docker compose version

Corrective Actions

If the problem persists, check the following items.

• Check the supported operating system version
• Check the required Docker Engine version
• Check for conflicts with an existing Container Runtime
• Check the server internet connection status

Container Deployment Issues

During INNORIX Container deployment, Docker Compose configuration errors or Image download issues may prevent Containers from being created successfully.

Major Symptoms and Causes

Check Container Status

Check the status of deployed services.

docker stack services exacoola

Verify that the REPLICAS value for each service is displayed correctly.

Check the status of individual Containers (tasks).

docker stack ps exacoola

Verify that the CURRENT STATE of each task is Running.

Items to Check

If a Container deployment issue occurs, check the following items.

• Whether the Docker service is running
• docker-compose.yml configuration values
• Whether the Server IP is configured
• Storage Mount status
• Whether the Container Image was downloaded successfully

Service Operation Issues

Even if the Container is running normally, problems may occur with INNORIX service access or functionality.

Major Symptoms and Causes

Service Check Items

Check the Hyperlink Agent

If you need to check Agent status, use the following commands to verify its running state.

Start:

/opt/INNORIX/INNORIX_Exacoola start

Stop:

/opt/INNORIX/INNORIX_Exacoola stop

Network Connectivity Issues

INNORIX requires normal network connectivity for Web Console access and file transfers between systems.

Major Symptoms and Causes

Network Check Items

Corrective Actions

If a network issue occurs, check the following in order.

1. Check the server network connection
2. Check IP and DNS settings
3. Check Firewall policies
4. Check service Port access
5. Check the target system connection status

License Activation Issues

A valid license activation is required to use all INNORIX features.

Major Symptoms and Causes

License Check Items

Corrective Procedure

1. Check Workspace creation status
2. Check the Authentication Key
3. Re-enter the License Key
4. Check the server activation status

Check Logs and Analyze Issues

When a problem occurs, use logs to analyze the exact cause.

Log analysis is used to identify the causes of service errors, Container issues, and network failures.

Logs to Check

Check Docker Logs

Check the service logs.

docker service logs exacoola_[service_name]

Issue Analysis Procedure

1. Check when the issue occurred
2. Check service status
3. Check Container status
4. Check related logs
5. Analyze the cause and take corrective action
6. Verify that the service operates normally

Verify Troubleshooting Completion