A Backup Does Not Restore

Diagnosis

Scenario

An administrator attempts to restore a Backup through the supported workflow.

Observed Behavior

The restore reports one of these messages, or it does not complete:

Error restoring Backup.
Error uploading Backup.
Failed to restore Database from the backup, Database was rolled back to previous state. Please refresh the page to see all changes! The previous configuration was kept.
Failed to restore Database from the backup. Please refresh the page to see all changes! The database was not rolled back. Stop configuration changes and contact Riedel Customer Success.

Possible Causes

The displayed restore message is required to distinguish the cases. A Backup that cannot be uploaded, a restore that the system rolled back, and a restore that was not rolled back each need a different response.

Warning

If a cluster fault accompanies the restore failure, contact Riedel Customer Success before retrying or intervening in the infrastructure. Database integrity and stored data may be at risk. A Backup restore is not a substitute for support-led infrastructure recovery.

Prerequisites

Restore actions require Backup admin. Check version compatibility and licensing as described in Manage Backups before a restore.
Retain the original Backup file, source and target versions, and complete restore result.
If a cluster fault is present, stop recovery actions and contact Riedel Customer Success before retrying.

Resolution

Administrator: Stop further restore attempts and preserve the original Backup file. Record the source and target hi versions and the complete restore message.
If the result is Failed to restore Database from the backup. Please refresh the page to see all changes!, stop configuration changes and contact Riedel Customer Success before any further restore.
If a cluster fault accompanies the failure, contact Riedel Customer Success through Customer Support before retrying. Follow A Multi-Server Installation Reports a Server or Service Fault.
If there is no cluster fault, compare the Backup's Software Version with the installed hi version and check licensing as described in Manage Backups. If compatibility is not established, contact Riedel Customer Success before another restore attempt.
Do not modify or unpack the Backup file to make it pass validation. If the file is incomplete or altered, retain it and ask Riedel Customer Success how to proceed.

Caution

Restoring replaces all Nodes, wiring, and configuration on the running system. Before another attempt, create a Backup of the current system and get operational approval for the interruption.

If the documented compatibility and starting conditions are met, follow Back Up and Restore a System. If it still fails, retain the new result and contact Riedel Customer Success.

Verify the Result

Confirm that hi reports Database was restored from a backup. Please refresh the page to see all changes! and that the Backup shows the Last restored status, then follow the verification steps in Back Up and Restore a System. Check the affected configuration and critical operator workflows. If cluster or database integrity was in question, obtain Riedel Customer Success guidance before returning the installation to service; a completed restore alone does not establish infrastructure recovery.

See Backups for consequences and supported actions.