Introducing DR in a Box — Automated Windows Server Migration to Proxmox
Introducing DR in a Box — Automated Windows Server Migration to Proxmox
DR in a Box is an automated, wizard-driven tool designed to simplify Windows Server migration and disaster recovery workflows by provisioning and failing over Physical, Virtual, or Cloud Windows Server workloads into Proxmox virtual machines. It leverages a web-based UI and a combination of JavaScript, APIs and PowerShell to discover sources, provision targets, synchronize data using the OpenText Migrate replication engine, and perform controlled failovers.
Demo video can be found here
How DR in a Box works
DR in a Box orchestrates the end-to-end migration and failover process using four coordinated stages:
- Discover — Agentless and agent-assisted discovery routines enumerate Windows Server sources (physical hosts, VMs, or cloud instances) and collect configuration and disk layout information.
- Provision — The wizard provisions Proxmox VM targets automatically (disk, CPU, memory, network), using templates or custom sizing defined during the wizard flow.
- Sync — DR in a Box integrates with the OpenText Migrate replication engine to replicate volumes and keep source and target in sync until failover is required.
- Failover — The tool automates the failover process into the newly provisioned Proxmox VMs, including final sync, NIC configuration, and boot orchestration.
Key features
- Wizard‑driven, web-based user interface for guided migration workflows.
- Support for Physical → Proxmox, Virtual → Proxmox and Cloud → Proxmox Windows Server migrations.
- Uses JavaScript, REST APIs and PowerShell scripts to perform discovery, provisioning and post‑provision configuration.
- Integrates with OpenText Migrate replication engine for continuous data synchronization.
- Automates target VM provisioning in Proxmox (disks, CPU, memory, network, cloud-init/user-data where applicable).
- Failover automation to reduce manual steps and time-to-recovery during an outage.
Benefits
- Reduces manual provisioning complexity when recovering Windows Servers to Proxmox.
- Speeds failover and recovery time by automating repetitive tasks.
- Provides consistent, repeatable migration flows that reduce human error.
- Works with existing OpenText Migrate licenses to reuse proven replication capabilities.
Prerequisites & compatibility
- OpenText Migrate must be licensed and configured for replication between source and target environments.
- Proxmox VE cluster reachable from the DR in a Box orchestration host with API access and sufficient privileges to create VMs and storage allocations.
- Windows Server sources must be reachable for discovery (WinRM or other configured management channel) and allow PowerShell-based operations where required.
- Browser access to the DR in a Box web UI; recommended modern browsers (Chrome, Edge, Firefox).
- Network and firewall rules permitting replication, management API calls, and post-failover connectivity.
Limitations & considerations
- Does not provide built-in OpenText support — customers should treat this as an add‑on automation layer and retain existing OpenText support arrangements for Migrate.
- Not all source configurations or specialized hardware mappings can be automatically translated; custom post‑provision tasks may be required for advanced scenarios.
- Guest OS drivers, licensing activation and application‑specific configuration may still require manual validation after failover.
- Carefully validate network, DNS and Active Directory dependencies during test failovers to avoid split‑brain or name resolution issues.
Security and hardening
DR in a Box uses APIs and PowerShell to perform management actions. Follow standard security best practices:
- Run the orchestration service under a least‑privilege service account and rotate credentials regularly.
- Use encrypted channels (HTTPS/TLS) for the web UI and API calls to Proxmox and OpenText endpoints.
- Store secrets (API keys, service passwords) in a vetted secrets manager — avoid plain text configuration files.
- Audit and log all discovery, provisioning, and failover operations for compliance and troubleshooting.
Recommended workflow for adoption
- Perform discovery runs and review the inventory output for accuracy.
- Run non‑disruptive test replications to Proxmox targets and validate boots in an isolated network or lab.
- Document any post‑migration manual steps required for applications or licensing activation.
- Schedule formal DR tests (planned failovers) and update runbooks with DR in a Box steps and verification checks.
- Establish rollback procedures and ensure backups are available before production failover.
Troubleshooting & escalation
Common checks when issues occur:
- Verify Proxmox API access and check task/queue for failed VM creations.
- Confirm OpenText Migrate replication state and that the latest delta is applied to the target storage.
- Review PowerShell and orchestration logs in the DR in a Box UI for script errors or permission failures.
- Validate network connectivity (ports, DNS, routes) between source, orchestration host and Proxmox cluster.
If issues persist, collect logs (web UI, orchestration host, Proxmox task logs, Migrate replication logs) and reach out to the tool maintainer or your internal platform team with those artifacts for escalation.
DR in a Box offers a practical automation layer for teams that need to accelerate Windows Server recovery to Proxmox while leveraging OpenText Migrate for replication. When used intentionally — with proper testing, security controls and runbooks — it can reduce manual steps, shorten recovery time objectives, and improve repeatability for DR operations.
