Reconstruct Management

× Magnified Image

Rebuild Management when its host, persistent state, or administrator access is lost while the installed appliance survives. This procedure reconnects to the surviving appliance and restores its published GitOps history.

Screenshots show the Management frontend with simulated example data. Versions, hostnames, timestamps and status observations do not describe a deployed appliance.

Before you begin

  • Have the appliance’s retained artifact bundle and Management media compatible with its release.

  • Provide a fresh Management ISO VM and state disk, or a container host with a fresh Management data volume, according to the requirements. Preserve failed state for diagnosis.

  • Keep the previous Management instance inactive so that two instances do not publish competing configurations.

  • Check that the new Management network can reach the surviving appliance.

The ISO does not restore a Management disk image or reset a forgotten Management administrator password. A fresh Management installation creates new Management state. Recreate the local accounts and registry connections you need, and download or upload the required bundles again.

Reconstruct and Reconnect

  1. Deploy fresh Management through Docker, Compose or Podman with a new data volume, or deploy and initialize the ISO VM.

  2. Sign in to the new Management instance.

  3. Follow Reconnect the appliance and supply the existing appliance’s artifact bundle. Do not start a fresh appliance installation.

  4. When the dashboard offers Git history recovery, choose Restore from cluster. The configured destination repository must be accessible and empty. If it is inaccessible, correct the Gitea connection and use Check Git repository again.

  5. Wait for restoration to finish. If you choose Not now, the recovery choice remains available on the dashboard.

  6. Recreate registry connections and retrieve or upload locally needed release and recovery bundles through Settings.

Management recovers the appliance’s selected published configuration from a surviving appliance registry. The initial GitOps files inside an old artifact bundle are not a substitute for that current configuration. This procedure cannot recover changes that were never published from the lost Management repository.

Verify

Confirm the expected appliance identity and release. Open Gitea and check that the recovered configuration and Git history belong to that appliance. Then check health and application access. Services can still have failures after a successful reconnection.

If the appliance cannot supply its selected configuration, preserve the error and contact support. If the appliance itself was lost, use full appliance recovery instead.