Skip to content

Restore the Latest Verified Network-Lab Archive

  • Purpose: Rebind verified environment state to fresh execution capacity.
  • Owner: Platform operations
  • Impact: Creates infrastructure and may replace existing lab definitions or referenced base images when explicitly authorised.
  • Rollback strategy: Retain the failed environment for diagnosis or destroy it without replacing the verified source archive.

Pre-checks

Use the same environment and platform blueprint that own the recovery record:

ENV=<environment>
REF=<blueprint-ref>
hyops blueprint validate --env "$ENV" --ref "$REF"
hyops blueprint preflight --env "$ENV" --ref "$REF"

Confirm required secrets and image licences are present. They are not recovered from lab archives.

Execute

Deploy and select the verified archive:

hyops blueprint deploy \
  --env "$ENV" \
  --ref "$REF" \
  --execute \
  --restore-labs

If existing lab definitions must be replaced, add --overwrite-labs. If the verified recovery set must replace existing referenced base images, also add --overwrite-images:

hyops blueprint deploy \
  --env "$ENV" \
  --ref "$REF" \
  --execute \
  --restore-labs \
  --overwrite-labs \
  --overwrite-images

Do not use either overwrite flag without --restore-labs.

Verify

Confirm platform health, then verify the state that matters to the workload:

  • topology or project definitions
  • saved device configuration
  • EVE-NG writable node state where captured
  • Containerlab native lab-directory state where declared
  • device reachability and protocol convergence

Use the continuity-verification runbook for a structured before-and-after test.

Records

The deploy run record identifies the environment, selected recovery generation, and each reconstruction phase. Preserve the prior archive and manifest until acceptance is complete.

Rollback

If the restored state is wrong, keep the environment isolated. Re-run with the correct recovery authority or destroy the new capacity while retaining the verified archive.

References