Cross-host migration & cloning
Moving BOA sites and accounts: the in-host Ægir Clone and Migrate tasks, the root-side xoct, xcopy and xmass cross-host toolchain, migratefs, and site import and export.
Moving sites and accounts around a BOA fleet splits into two problem classes, and BOA solves each with a different toolchain.
Within one host — duplicating a site, or moving a site between platforms during a
Drupal-version upgrade — is the front-end's job: the Ægir Clone and Migrate
tasks, accelerated (and made cheaper to mass-run) by BOA's FastTrack/MyQuick
control files. No data leaves the box; the work is a Provision backup/restore plus a
Hostmaster node rewrite.
Across hosts — relocating a whole Octopus account, duplicating an account onto a
second box, or evacuating an entire server — is the root-side xoct / xcopy /
xmass toolchain. These:
- wrap
mydumper/myloader(per-account) or xtrabackup + GTID replication (whole-server); - freeze the source with a PHP-level
http-off503; - rename the moved account in place with
renameaegirhost; - convert the old box into a real-IP-recovering reverse proxy until DNS is repointed.
The toolchain is storage-aware — each store lands on the target's attached /mnt mount
or its root, per the target's disk reality — and its transfer steps are DRY-by-default,
running live only with an explicit --live.
A related root-side tool, migratefs, relocates account file stores onto attached
storage before — or independent of — any move.
A third axis runs through both: TLS is never carried across a machine-name change.
Clone, a name-changing Migrate, and every cross-host move auto-disable Encryption on
the new node, because the old certificate and ssl_key are bound to the old
machine-name. You re-issue deliberately for the new hostname.
The pages below open with the cross-host toolchain — an overview of which tool
to reach for and the storage gate, write freeze and migration proxy they share,
then the per-account xoct/xcopy move-and-copy runbook and the whole-server
xmass runbook — and go on to in-host cloning and migration, aliases and
redirects, storage relocation with migratefs, importing and exporting sites,
the Percona version matrix with the before/after verification checklist, the
vanilla-Ægir adoption runbook, the PX0 proxy role and xtrim shrink, and a
scenario-first failover and recovery runbook for the proxy/active/mirror
topology the toolchain leaves behind.
See the Reference appendix for the consolidated
configuration-variable, command, and control-file tables, and
Discontinued features for the retired xboa tool and
the legacy manual remote_import flow.
Cross-host migration — xoct, xcopy, xmass
Overview of the root-side xoct, xcopy and xmass cross-host tools: which to reach for when, and the machinery all three share - the DRY/--live storage gate, the http-off write freeze, and the migration proxy.
xoct & xcopy — single-account move and copy
The full xoct single-account cross-host move runbook - dispatch verbs, the export dump, on-target import and renameaegirhost, DNS proxy conversion - plus xcopy, the non-destructive duplicate that leaves the source live.
xmass — whole-server move
The full xmass whole-server move runbook: xtrabackup snapshot plus MySQL GTID replication, incremental sync, the storage-planned cutover sequence, per-account proxy modes, and the state machine and recovery paths.
Site cloning & in-host migration
The in-host Ægir Clone and Migrate tasks: the Provision backend, the FastTrack and MyQuick accelerators and their defaults, the Restore trade-off, and Encryption auto-disable.
Aliases & redirects
The hosting_alias data model, pure-alias versus 301-redirect mode, the separate redirection vhost BOA emits per alias, SAN cert coverage, and rebuilding aliases after a rename.
Relocating stores to attached storage — migratefs
The operator-only migratefs tool that relocates account file stores and the shared arch archive onto the single attached mount and symlinks them back, with a DRY plan by default.
Importing & exporting sites
Adopting a Drupal site BOA did not create with provision-import and platform auto-import, and taking a managed site back out to standalone via its backup tarball.
Percona versions & verifying a migration
How xoct and xmass behave across Percona 5.7/8.0/8.4, why the MySQL watchdog is paused during a move, and the before/after checklist that proves a migration actually succeeded.
Adopting vanilla Ægir into BOA — aegir2boa
The operator runbook for adopting a vanilla Ægir 3.x estate into a BOA Octopus account on a separate box - the read-only preflight, the in-place Apache-to-Nginx flip, and remote per-site or whole-panel adoption behind a proxy-revert window.
PX0 proxies & shrinking a migrated source — xtrim
What a migrated source box becomes when it is kept as a permanent web proxy, how its certificates stay alive, and how xtrim removes the payload it no longer serves — the reversible quiesce step, the one-way data stage, the box-wide finalize, and everything the tool refuses to touch.
Failover & recovery scenarios
Scenario-first runbook for the migration and HA topology: what to do when the proxy box or the active server goes down, how to switch to a mirror behind your own proxy or a CDN-only front, what downtime to expect, and how to bring the original server back as master.
Migration source wiring
The migrate_source task: what it grants, the proof of possession that bounds which database may be named and the checks around it, its automatic enablement on every Octopus install and upgrade, and the reconciliation sweep.