Updated: February 6th, 2026
Interlock DataForge Application Server and Node Software
Interlock's DataForge is an always-on compliance migration solution. The DataForge software OVA is deployed on a VMware ESXi virtual machine image created in a customer's environment. This manual guides the user through the DataForge OVA installation process.
Installation Overview
The Interlock DataForge Application Server software is deployed by the client as an OVA image (Debian 11 "bullseye" back end) on a VMware ESXi virtual machine. Once the OVA is deployed, a 1 TB disk must be allocated to the Application Server and an IP address must be assigned. The client must also install the Migration Node software Windows (2016 or higher) VMware ESXi virtual machine, which will link to the Application server.
Multiple Migration Nodes can be created to support scalability requirements. If multiple Migration Nodes are installed, each Node requires its own virtual machine. The Nodes are installed manually after the DataForge Application Server software deployment is complete.
Software Installation Prerequisites
The Interlock DataForge Application Server and Node software requires access to the following infrastructure and permissions prior to installation.
Static IP Address
Required for DataForge Application Server and Node(s)
Network Ports
Communication between Application Server and Node(s) is required
Windows VM
Each Node requires its own Windows VM instance and software
Runtime Environment
DataForge Node software uses ASP.NET Core Runtime 8 and .NET Runtime 8, which must be installed into each migration node
Whitelist Site
The client support site requires access to https://fileshare.interlock-tech.com to download software patches and updates, upload log files, and troubleshoot issues
DataForge Infrastructure Requirements
Our DataForge migration software has a minimum of 2 elements to perform a successful migration: The DataForge Server and the DataForge Migration Node.
DataForge Application Server Requirements
Our current version of the DataForge Migration Server is built on top of Debian 11 “bullseye”
Virtual Processor
8 Virtual Cores (minimum)
Virtual Memory
64GB (minimum)
Virtual Disk #1 - OS Storage
120GB boot disk configured as part of the DataForge Server OVA
Virtual Disk #2 - MariaDB data store
A 1TB (minimum) disk must be added as secondary storage prior to initial boot. This disk will be automatically configured as the data directory for MariaDB
DataForge records the object information for each iteration (initial, changed. deleted) of every migration item (object or file) as an individual record in the database. For large scale migrations being performed by a single DataForge server instance, consider making Disk #2 larger to accommodate large object counts + deltas if using the synchronize feature
Virtual Networking
VMXNET3 NIC configured as part of the DataForge Server OVA.
DataForge Migration Node Requirements
Our DataForge Migration Node software is supplied as an MSI installer package and is expected to be installed in a Windows Environment.
Virtual Processor
- 4 Virtual Cores (1Gbps NIC) (minimum)
- 8+ cores (10Gbps NIC) (recommended)
Virtual Memory
- 16GB (minimum)
- 32GB+ (recommended)
Virtual Disk
- 150 GB free space after OS install (minimum)
Environment
Network Connectivity Requirements
DataForge Server
- The DataForge interface is web based and is required to have port 80 inbound available to access the web GUI from your migration engineer's desired workstation.
- The DataForge Server only talks bidirectionally to the migration node(s), listening on MariaDB server (port 3306) and RabbitMQ listener ports (35672-35682)
- SSH access inbound to DataForge server to apply any additional configuration or software updates.
DataForge Migration Node
The migration node(s) will perform all of the copying from source storage to target storage as well as communicating with the DataForge Server. Depending on your migration requirements, you will need allow access from each migration node to read object data from source and read/write to target.
Optional
If DataForge compliance reports are required, the DataForge Application server can connect to an SMB share as a save point.
DataForge Deployment Sizing
The deployment sizing (total disk space needed and number of nodes created) can be scaled up or scaled out based on the volume of data to be migrated. Guidelines based on data deployment are as follows.
| Source Storage Network Speed | Minimum Node CPU | Minimum Node RAM |
|---|---|---|
| 1GB | 4 | 16 |
| 10GB | 8 | 32 |
| Source Storage Node Count | DataForge Nodes |
|---|---|
| 1GB / 4 Nodes | 2 |
| 1GB / 8 Nodes | 4 |
| 1GB / 16+ Nodes | 8 |
| 10GB / 4 Nodes | 1 |
| 10GB / 8 Nodes | 3 |
| 10GB / 16+ Nodes | 6 |
DataForge Application Server Image Deployment
The Interlock DataForge Application Server package is self-contained in the OVA file, provided in a password protected zip file. Note that the administrative rights to make system changes are contained in the 'interlock' local account. Contact Interlock or your reseller for this information.
The VMware administrator deploys and boots the image (without any special configuration work) by following these steps.
- Logon to the VMware ESXi server administrative console.
- Download the image provided in the DataForge zip file.
- Extract the .ova file template.
- Select the .ova file template and deploy to the ESXi to create the virtual machine.
- Select DataForge, Add Disk and attach the 1TB (see requirements) disk in the console.
- Press power on to start the DataForge Application Server.
- Configure the required static IP address using the Debian nmtui command.
The DataForge Application Server installation is complete. Continue to the Node installation instructions.
Migration Node Installation
Once the DataForge Application Server is deployed, the project scope determines the number and scale of Nodes to be installed. The VMware administrator installs the software for the required Node(s) by following these steps.
- Deploy Windows virtual machine to your environment.
- Download the Node installer (see zip file downloaded with the Application server).
- Extract the Migration Node installer software.
- Install the .NET 8 runtime packages (see requirements).
- Configure the Node software (use the Application Server IP address).
- Ensure that each migration node system date and time is in sync with the date and time on the DataForge server (the NTP server may need to be set manually).
- The Node automatically starts.
The Node software installation is now complete. You should now be able to log into your DataForge instance via web browser and the IP address you configured for the server
