Skip to Content
Browse documentation

Restore Converted Migration Backups

Transfer converted archives to Eenos, review restore conflicts and options, and verify the account after a destination restore.

Standalone converters produce backups for a separate destination restore. WAP import workflows already coordinate their own restore stages; monitor those through Transfer Progress instead of restoring the same account again.

Before restoring

  1. Review converter logs and inspect the intended output. Confirm account identity, included components and any skip options.
  2. Securely transfer the archive to private destination storage. Compare source and destination checksums to detect transfer changes; a checksum alone does not prove a backup is complete or trustworthy.
  3. Check destination compatibility, free space, runtime/database services, domains, usernames and reseller ownership. Current DNSv2 converter output requires Eenos 5.0.1 or later.
  4. Back up any existing destination account that could be affected. Resolve conflicts before choosing overwrite or rename options.

Restore an account

As root on the destination, first inspect the installed restore command:

/usr/local/eenos/scripts/restoreacct --help

For a reviewed Eenos-format archive, use its full path:

/usr/local/eenos/scripts/restoreacct /backup/eenosbkp-exampleuser.tar.gz

Replace the example with the actual converter output. A full account restore is the default scope. This command changes destination account data; run it only after the checks above and inspect its logs and results.

Options that need particular care

OptionReview before using
--forceCan replace existing account data. It is not a routine conflict-resolution shortcut.
--newname USERRenames account-related data; applications can retain old paths or database references.
--disk_mount PATHDestination storage layout and capacity.
--ipv4 ADDRESSDestination address assignment and dedicated/shared IP requirements.
--skipmysql, --skippgsql, --skipmongodbDatabases that will need a separate restore.
--skiphome, --skipemail, --skipresellerMissing files, mail or reseller configuration that must be handled separately.
--skipletsCertificate provisioning must be handled separately.

The restore tool also has component-specific scopes. Read the installed help rather than combining full-account and component restore options by assumption. Converter flags and restore flags are separate interfaces; for example, the converter's --skiphomedir is not the restore command's --skiphome.

See the complete restoreacct command reference for all scopes and options.

Packages and ownership

The converters can emit a separate EenosHostingPackages directory. An account restore is not evidence that all package definitions have been installed. Review converted package names, limits and reseller ownership against WAP Packages before assigning plans. Do not blindly overwrite existing package files with source values.

After restore

Review warnings and skipped components, confirm ownership and limits, and complete verification and cutover. Keep the original and converted backups until the migration has been accepted. Re-running a restore is not a rollback strategy.