Clone a Datacenter
Recreate a complete STRATUM datacenter topology, then supply the exact Arsenal VM images and ISO content that its systems need.
Topology is not the VM disk
A STRATUM datacenter export preserves the datacenter definition: VM and network objects, topology, connectivity, and their relationships. It does not embed the Arsenal VM template images or ISO files required to boot those systems.
It also does not include guest disk changes made after a VM was originally deployed from its base image. To reproduce a configured system, first Promote that stopped VM into a new versioned Arsenal image. Export that promoted image along with the topology.
If you import only a datacenter package, the VM objects and their wiring can be restored, but their required VM images and ISO content must already be available. A VM attached to its original base image will boot from that baseline, without later guest changes.
Clone a configured datacenter
Identify the content to preserve
List the VM template families, exact image versions, and ISO files referenced by the datacenter. Decide which VMs require their post-installation or post-configuration disk changes in the clone.
Promote configured VMs
Stop each VM whose local disk changes need to be preserved. In Arsenal Forge → VM, Promote it into an Arsenal template image/version. Record the promoted template name and version for that VM.
Export the VM images and ISO files
Export the promoted VM images, any original/base VM templates still required, and the ISO files used by the datacenter. Keep each image's template identity and version available for import.
Export the datacenter
Use the datacenter Export action in STRATUM to save the VM and network topology as a separate datacenter package.
Import the Arsenal content
On the destination STRATUM system, import the VM templates and exact image versions first, followed by the required ISOs. Confirm that these resources appear in Arsenal.
Import and reconnect the datacenter
Import the datacenter package. Then edit each VM and select the correct promoted template + version from the VM's Payload list. Use the original base template/version for VMs that do not need their later disk changes.
Verify the clone
Review VM payloads, storage-bin availability, local-network mappings, any required ISO attachments, and worker placement before starting the imported datacenter. Boot and test the VMs to confirm the intended guest configurations.
When promotion is not needed
Base-image clone: If all the VMs should start from their original Arsenal templates and you do not need changes made after their first deployment, export and import those base template versions, the required ISOs, and the datacenter package. You do not need to Promote the deployed VMs.
Configured-state clone: If you installed software, applied settings, or added data inside a deployed VM, Promote that stopped VM first and export the promoted image version. After import, point the VM's Payload to that promoted version.
This workflow reproduces the datacenter topology and the captured guest disk contents. It does not transfer running memory state, live execution sessions, externally managed data, or site-specific physical networking automatically.