Updated: March 30th, 2026
Interlock DataForge Classic deployment instructions
Interlock's DataForge Classic is our legacy compliance migration solution. The DataForge Classic 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 Classic OVA installation process.
Installation Overview
The Interlock DataForge Classic server software is deployed by the client as 2 OVA images (Windows migration environment) and (Debian 11 "bullseye" back end) on a VMware ESXi virtual machine. The Windows environment is where our migration software will be run, using the Linux server as our MariaDB database for migration and object metadata storage.
Software Installation Prerequisites
The Interlock DataForge Classic Server requires access to the following infrastructure and permissions prior to installation.
Static IP Address
Required for DataForge Classic Server and DataForge Application Server (Linux)
Network Ports
Communication between DataForge Classic Server is required for:
- MySQL port 3306 and SSH port 22 from the DataForge Linux Server
- Source and target storage (ports dependent on storage types)
- RDP port 3389 open on the Windows VM accessible from migration engineers provisioned VM(s)
- Please provide for both UDP and TCP
Whitelist Site
The DataForge Classic Windows VM:
- https://fileshare.interlock-tech.com used to download software patches and updates, upload log files, and troubleshoot issues.
- https://support.interlock-tech.com used to generate and provide software activation licenses for migrations.
DataForge Classic OVA Deployment
The DataForge Classic OVA is a Windows Server environment that is preconfigured to use with our software. The software and tools needed for migration engineer are pre-installed and configured for use.
- Download and extract the DataForge-Classic-Migrator-(current version).7z file using the link that an Interlock employee has provided for you.
- In VMWare / ESXi: You will Create / Register VM normally using the OVA extracted from the download.
- Assign the appropriate VM network that will be used for the migration. This VM will need firewall access to both the source and target storage, and the Linux backend
The OVA will create a 512GB C: drive and a 256GB E: drive.
DataForge / Linux Backend OVA Deployment
For the Linux database back end, we use the same image and setup instructions for our latest compliance migration software, DataForge. Please follow these instructions, skipping all of the Migration Node Installation prerequisites and sections.
