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#
| Item | Requirement |
|---|---|
| CPU | 4 Core |
| RAM | 16 GB |
| Storage | At least 50 GB of free space |
| Architecture | x86_64 (AMD64) |
Recommended Specifications#
| Item | Requirement |
|---|---|
| CPU | 8 Core |
| RAM | 32 GB |
| Storage | At least 100 GB of free space |
| Architecture | x86_64 (AMD64) |
ℹ️ 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.
| Operating System | Minimum Supported Version |
|---|---|
| RHEL | 9 or later |
| Rocky Linux | 9 or later |
| CentOS | 9 or later |
| Debian | 12 or later |
| Fedora | 41 or later |
| Ubuntu | 22.04 or later |
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.
| Component | Requirement |
|---|---|
| Operating System | RHEL-based Linux / Debian-based Linux |
| Node.js | 22.x |
| Container Runtime | Docker Engine |
| Container Management | Docker Compose Plugin |
Docker Requirements#
INNORIX runs in Docker Containers and requires the following Docker environment.
| Component | Requirement |
|---|---|
| Docker Engine | 24.0 or later |
| Docker Compose | v2 |
| Architecture | x86_64 (AMD64) |
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 curlAdd 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 curlAdd 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 nodejsDebian-based Linux#
sudo apt install -y nodejsRemove 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-engineDebian-based Linux#
sudo apt remove -y docker docker-engine docker.io containerd runcConfigure 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-coreAdd the official Docker Repository.
sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repoDebian-based Linux#
Create the key storage path for Docker Repository authentication.
sudo mkdir -p /etc/apt/keyringsAdd the Docker GPG Key.
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpgAdd 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/nullUpdate System Packages#
Update system packages to the latest versions before installing Docker.
RHEL-based Linux#
sudo dnf updateDebian-based Linux#
sudo apt updateInstall 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-pluginDebian-based Linux#
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-compose-pluginStart and Enable the Docker Service#
Start the Docker service and configure it to start automatically after system reboot.
sudo systemctl enable --now dockerVerify the Docker Installation#
Verify that Docker was installed successfully.
Check the Docker version.
docker --versionCheck the Docker Compose version.
docker compose versionIf 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.gzAfter the download is complete, verify that the file was saved correctly.
ls -lh INNORIX-ONPREM-PACKAGE.tar.gzExtract the Installation Package#
Extract the downloaded On-premise package.
Extract the package.
tar -xzf INNORIX-ONPREM-PACKAGE.tar.gzAfter 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 -laMain configuration files:
| File | Description |
|---|---|
| docker-compose.yml | INNORIX Container runtime configuration file |
| install.sh | INNORIX installation script |
| start.sh | INNORIX service startup script |
| Other configuration files | Service operating environment 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.ymlConfiguration items:
| Item | Description |
|---|---|
| Server IP Address | IP address of the server where the INNORIX service runs |
| Container Configuration | INNORIX service runtime environment |
| Network Configuration | Container communication environment |
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.shThe 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.shAfter 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 startStop the Agent#
/opt/INNORIX/INNORIX_Exacoola stopAfter 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:
| Item | What to Check |
|---|---|
| Deployment | Whether the Stack services are running normally |
| INNORIX Service | Service running status |
| Hyperlink Agent | Agent running status |
| Network | Whether the server is accessible |
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_ADDRESSor
http://localhostThe access address is based on the server IP address configured in the docker-compose.yml file.
Server Access Checklist#
| Item | Description |
|---|---|
| Server IP | IP address of the server where the INNORIX service runs |
| Access URL | Web Console access address |
| Network Access | Whether the server is accessible from the user environment |
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:
| Item | Configuration Value |
|---|---|
| Domain | INNORIX.example.com |
| IP Address | INNORIX installation server IP |
After domain configuration is complete, users can access the service as follows.
https://domainIf 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:
| Item | Description |
|---|---|
| Service Port | INNORIX service access port |
| Container Port | Internal Docker Container service port |
| Firewall Port | Port allowed for external access |
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:
| Item | Description |
|---|---|
| Server Information | Service host server information |
| Network Configuration | Container communication environment |
| Storage Configuration | Data storage location |
| Service Configuration | Service runtime options |
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.ymlThe Docker Compose configuration includes the following items.
| Configuration Item | Description |
|---|---|
| Container Configuration | INNORIX service runtime environment |
| Network Configuration | Communication between Containers |
| Volume Configuration | Connection to the data storage area |
| Port Configuration | Service access ports |
| Environment Configuration | Service environment variables |
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#
| Item | Description |
|---|---|
| Server IP | IP address of the server where INNORIX is installed |
| Network Interface | Network interface used by the service |
| DNS | Server address mapping when using a domain |
| Routing | Communication path to file transfer target systems |
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#
| Item | Description |
|---|---|
| Inbound Rule | Policy for external access to the INNORIX server |
| Outbound Rule | Policy for communication from the INNORIX server to external systems |
| Service Port | Web Console and file transfer service Port |
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#
| Item | Description |
|---|---|
| Storage Capacity | Ensure sufficient storage space for system operation data |
| Disk Performance | Ensure reliable read/write performance for operation data and logs |
| Access Permission | Configure permissions so the INNORIX service can access the storage |
| Backup | Apply a backup policy to protect system configuration and operation data |
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#
| Item | Description |
|---|---|
| Service Configuration | INNORIX service configuration data |
| System Data | System operation data |
| Log Data | Service log data |
| File Data | Transferred file storage area |
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#
| Item | Description |
|---|---|
| Domain | Service domain for HTTPS access |
| SSL Certificate | Certificate for server authentication |
| Private Key | Private key for the SSL certificate |
| HTTPS Port | Encrypted communication Port |
HTTPS Setup Procedure#
- Prepare a domain appropriate for the production environment.
- Obtain an SSL certificate.
- Apply the certificate files to the server environment.
- Restart the INNORIX service.
- 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#
| Item | Description |
|---|---|
| Certificate File | Public certificate file |
| Private Key File | Private key file |
| Certificate Chain | Certificate authority chain information |
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#
| Item | Description |
|---|---|
| Administrator Account | System administrator account management |
| User Permission | Permission settings by user |
| Access Control | Service access restrictions |
| Authentication | User authentication management |
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#
| Item | Description |
|---|---|
| Account Policy | Account management policy |
| Password Policy | Password policy |
| Network Policy | Network access policy |
| Log Management | System log management |
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_ADDRESSor
http://localhostIf access is successful, the INNORIX initial screen is displayed.
If you cannot connect, check the following items.
| Check Item | Description |
|---|---|
| Server Status | Whether the INNORIX service is running |
| Service Deployment Status | Whether the stack services are operating normally |
| Network | Whether the server is accessible |
| Port | Whether the service Port is open |
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#
| Item | Description |
|---|---|
| Service Status | INNORIX service running status |
| Server Status | Whether the server is operating normally |
| Connection Status | Network connection status |
| System Status | System readiness status |
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:
| Item | Value |
|---|---|
| ID | Admin |
| Password | Innorix2026! |
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#
- Log in with the administrator account.
- Go to the Workspace creation menu.
- Enter the Workspace information.
- Complete Workspace creation.
Workspace Configuration Items#
| Item | Description |
|---|---|
| Workspace Name | Workspace name |
| Description | Workspace description |
| Administrator | Administrator account information |
| Storage | File storage environment |
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#
- Complete Workspace creation
- Generate an authentication key
- Copy the generated Authentication Key
- 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:
| Item | Description |
|---|---|
| Workspace | Workspace management |
| Administrator | Administrator account management |
| Service Setting | Service operation settings |
| User Setting | User management settings |
Verify Initial Setup Completion#
| Check Item | Status |
|---|---|
| Web Console access complete | ✓ |
| Server status check complete | ✓ |
| Administrator login complete | ✓ |
| Workspace creation complete | ✓ |
| Authentication key generation complete | ✓ |
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#
| Item | Description |
|---|---|
| Deployment Status | Whether new services and Containers were deployed successfully |
| Service Status | Whether major services are operating normally |
| Process Status | Whether service processes are running |
| Agent Status | Hyperlink Agent running status |
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#
| Item | Description |
|---|---|
| CPU Usage | System CPU usage |
| Memory Usage | Memory usage |
| Storage Usage | Disk usage |
| System Resource | Server resource status |
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#
| Item | Description |
|---|---|
| Server Access | Whether the Web Console is accessible |
| Network Connection | Whether connected target systems can communicate |
| Port Access | Whether the service Port is accessible |
| DNS Resolution | Domain resolution status |
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#
- Access the Web Console with the administrator account
- Prepare a test file
- Create a file transfer task
- Connect the target system
- Run the file transfer
- Check the transfer result
File Transfer Check Items#
| Item | Description |
|---|---|
| Transfer Status | Transfer task status |
| File Count | Number of transferred files |
| File Size | Size of transferred files |
| Transfer Time | Time required for transfer |
| Result | Success or failure result |
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#
| Category | Target | Description |
|---|---|---|
| System Configuration | Docker Swarm Configuration | Service runtime environment and service configuration information |
| System Configuration | Environment Configuration Files | Service operating environment configuration information |
| System Configuration | License Information | Product authentication and license-related information |
| Data | Workspace Information | Workspace configuration information |
| Data | User Information | Account and permission information |
| Data | Operation Data | Data generated during service operation |
| Logs | Log Data | System operation records and failure analysis information |
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#
| Item | Description |
|---|---|
| Docker Compose Configuration | Container runtime environment information |
| Environment Variable Configuration | Service environment configuration information |
| Service Configuration | INNORIX operation configuration information |
| Network Configuration | Service connection environment information |
System Configuration Backup Procedure#
- Check the INNORIX installation directory
- Back up Docker Compose and environment configuration files
- Move the backup files to the backup storage location
- 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#
| Item | Description |
|---|---|
| Workspace Data | Workspace-related information |
| User Data | User and permission information |
| Service Data | Service operation data |
| Log Data | System and task records |
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.
| Item | Description |
|---|---|
| Backup File | Verify a valid backup file |
| System Version | Check the backup environment and current environment |
| Storage Space | Ensure sufficient restore space |
| Service Status | Check whether the service is stopped |
Restore Procedure#
- Check the INNORIX service status
- Stop the service if necessary
- Restore system configuration files
- Restore data
- Restart the service
- Verify normal operation
Verify the Restore#
After restoration is complete, verify that the system and services operate normally.
Restore Check Items#
| Item | What to Check |
|---|---|
| Service Status | Whether the INNORIX service is running normally |
| Configuration | Whether configuration information is applied correctly |
| Workspace | Whether the existing Workspace is preserved |
| User Account | Verify user accounts |
| File Transfer | Whether file transfer functions operate normally |
| Log | Whether system logs are generated normally |
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#
| Check Item | Status |
|---|---|
| Backup targets verified | ✓ |
| System configuration backup complete | ✓ |
| Data backup complete | ✓ |
| Restore procedure verified | ✓ |
| Restore validation complete | ✓ |
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#
| Item | What to Check |
|---|---|
| Current Version | Check the currently installed INNORIX version |
| System Status | Verify that the service is operating normally |
| Storage | Ensure sufficient workspace for the upgrade |
| Network | Verify that the Container Image can be downloaded |
| Backup | Verify that system configuration and data have been backed up |
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#
- Check the Docker environment status
- Load the latest INNORIX Container Image
- Check the existing Image and the new Image
- Apply the Image to be updated
Items to Check#
| Item | Description |
|---|---|
| Image Version | New Container Image version |
| Storage Usage | Image storage space |
| Compatibility | Compatibility between the current environment and version |
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 exacoolaVerify 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 exacoolaStep 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.tarAfter loading is complete, verify that the new Image was stored successfully.
docker imagesStep 3. Upgrade the Service (Redeploy)
Redeploy the service using the latest loaded Container Image.
sudo docker stack deploy -c docker-compose.yml exacoolaDocker 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 exacoolaIf 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 exacoolaStep 5. Check Service Logs
Check the logs to verify that no errors occurred during the upgrade.
docker service logs exacoola_node-appTo view real-time logs and only the most recent logs, use the following command.
docker service logs -f --tail=100 exacoola_node-appLogs for other services can be checked in the same way.
docker service logs exacoola_mysqldocker service logs exacoola_redisDocker 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#
| Item | Description |
|---|---|
| Configuration | Existing service configuration is preserved |
| Environment | Environment variable configuration is preserved |
| Network | Overlay Network configuration is preserved |
| Volume | Persistent Storage and operation data are preserved |
| Workspace | Workspace configuration information is preserved |
| License | Applied License information is preserved |
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#
| Item | What to Check |
|---|---|
| Deployment Status | Whether new services and Containers were deployed successfully |
| Service Status | Whether the INNORIX service operates normally |
| Web Console | Whether the administrator screen is accessible |
| Configuration | Whether existing settings are preserved |
| File Transfer | Whether file transfer functions operate normally |
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 exacoolaTo check individual Containers (tasks), use the following command.
docker stack ps exacoolaStep 2. Check the Current Logs
Check for errors that occurred during the upgrade.
docker service logs exacoola_node-appTo view real-time logs, use the following command.
docker service logs -f --tail=100 exacoola_node-appStep 3. Check the Previous Version Image
Check the previous version Images and Tags stored locally.
docker imagesVerify 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.tarStep 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.0After saving the configuration, redeploy the service using the changed Image.
sudo docker stack deploy -c docker-compose.yml exacoolaDocker 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 exacoolaIf 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-initservice 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-appTo check only a specific service, use the following command.
docker service logs exacoola_mysqldocker service logs exacoola_redisVerify Rollback Completion#
| Check Item | Status |
|---|---|
| Service status check complete | ✓ |
| Previous version Image check complete | ✓ |
| Previous version service redeployment complete | ✓ |
| Service operation check complete | ✓ |
| Log check complete | ✓ |
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#
| Symptom | Cause | Resolution |
|---|---|---|
| Docker installation fails | Existing Docker-related package conflict | Remove existing Docker packages and reinstall |
| Repository addition fails | Repository configuration error | Check the Repository for the operating system environment |
| Docker command cannot run | Docker not installed or service stopped | Check Docker installation and service status |
| Docker permission error | Insufficient user permissions | Run with administrator privileges |
Check Docker Status#
Check the Docker service status.
systemctl status dockerCheck the Docker version.
docker --versionCheck the Docker Compose version.
docker compose versionCorrective 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#
| Symptom | Cause | Resolution |
|---|---|---|
| Container creation fails | Docker Compose configuration error | Check docker-compose.yml configuration |
| Image download fails | Network or authentication issue | Check Docker Repository access |
| Container exits immediately | Environment configuration error | Check Container logs |
| Storage connection fails | Volume configuration error | Check Storage path and permissions |
Check Container Status#
Check the status of deployed services.
docker stack services exacoolaVerify that the REPLICAS value for each service is displayed correctly.
Check the status of individual Containers (tasks).
docker stack ps exacoolaVerify 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.ymlconfiguration 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#
| Symptom | Cause | Resolution |
|---|---|---|
| Cannot access Web Console | Service not running | Check Container and service status |
| Service initialization fails | Environment configuration error | Check configuration files |
| Agent execution error | Hyperlink Agent issue | Check Agent status |
| Function operation error | Internal service error | Check logs |
Service Check Items#
| Item | What to Check |
|---|---|
| Deployment Status | Whether new services and Containers were deployed successfully |
| Service Status | INNORIX service status |
| Agent Status | Hyperlink Agent running status |
| Configuration | Whether service configuration is applied correctly |
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 startStop:
/opt/INNORIX/INNORIX_Exacoola stopNetwork Connectivity Issues#
INNORIX requires normal network connectivity for Web Console access and file transfers between systems.
Major Symptoms and Causes#
| Symptom | Cause | Resolution |
|---|---|---|
| Cannot access Web Console | Port blocked | Check Firewall settings |
| Cannot access server | IP or DNS error | Check network configuration |
| File transfer fails | Target system connection issue | Check communication status |
| External connection fails | Blocked by security policy | Check network policy |
Network Check Items#
| Item | What to Check |
|---|---|
| Server IP | Whether the server IP is configured correctly |
| DNS | Domain connection status |
| Firewall | Whether the Port is allowed |
| Network Route | Whether the communication path is normal |
Corrective Actions#
If a network issue occurs, check the following in order.
- Check the server network connection
- Check IP and DNS settings
- Check Firewall policies
- Check service Port access
- Check the target system connection status
License Activation Issues#
A valid license activation is required to use all INNORIX features.
Major Symptoms and Causes#
| Symptom | Cause | Resolution |
|---|---|---|
| License registration fails | License Key error | Check the issued Key |
| Authentication fails | Authentication Key error | Recheck the authentication key |
| Feature restrictions occur | License not applied | Check License activation status |
| Server activation fails | Environment information mismatch | Check server information |
License Check Items#
| Item | Description |
|---|---|
| Workspace | Whether a Workspace has been created |
| Authentication Key | Whether the authentication key was generated correctly |
| License Key | Issued license information |
| Server Information | Installation server information |
Corrective Procedure#
- Check Workspace creation status
- Check the Authentication Key
- Re-enter the License Key
- 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#
| Log Type | Description |
|---|---|
| Docker Log | Container operation and error information |
| Service Log | INNORIX service operation records |
| System Log | Server operating environment information |
| Network Log | Connection and communication information |
Check Docker Logs#
Check the service logs.
docker service logs exacoola_[service_name]Issue Analysis Procedure#
- Check when the issue occurred
- Check service status
- Check Container status
- Check related logs
- Analyze the cause and take corrective action
- Verify that the service operates normally
Verify Troubleshooting Completion#
| Check Item | Status |
|---|---|
| Docker installation issue resolved | ✓ |
| Container deployment issue resolved | ✓ |
| Service operation issue resolved | ✓ |
| Network connectivity issue resolved | ✓ |
| License activation issue resolved | ✓ |
| Log review and issue analysis complete | ✓ |