mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
40 lines
2.2 KiB
Plaintext
40 lines
2.2 KiB
Plaintext
|
|
// Module included in the following assemblies:
|
|
//
|
|
// * microshift_troubleshooting/microshift-troubleshoot-backup-restore.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="microshift-restore-data-failed_{context}"]
|
|
= Data restoration failure
|
|
|
|
[role="_abstract"]
|
|
The restoration of data can fail for many reasons, including storage and permission issues. Mismatched data versions can cause failures when {microshift-short} restarts.
|
|
|
|
[id="microshift-image-based-systems-data-restore-failed_{context}"]
|
|
== Image-based systems data restore failed
|
|
|
|
Data restorations are automatic on `rpm-ostree` systems, but can fail, for example:
|
|
|
|
* The only backups that are restored on `rpm-ostree` systems are backups from the current deployment or a rollback deployment. Backups are not taken on an unhealthy system.
|
|
|
|
** Only the latest backups that have corresponding deployments are retained. Outdated backups that do not have a matching deployment are automatically removed.
|
|
|
|
** Data is usually not restored from a newer version of {microshift-short}.
|
|
|
|
** Ensure that the data you are restoring follows same versioning pattern as the update path. For example, if the destination version of {microshift-short} is an older version than the version of the {microshift-short} data you are currently using, the restoration can fail.
|
|
|
|
[id="microshift-rpm-manual-restore-data-failed_{context}"]
|
|
== RPM-based manual data restore failed
|
|
|
|
If you are using an RPM system that is not `rpm-ostree` and tried to restore a manual backup, the following reasons can cause the restoration to fail:
|
|
|
|
* If {microshift-short} stopped running because of an error, you cannot restore data.
|
|
** Make sure the system is healthy.
|
|
** Start it in a healthy state before attempting to restore data.
|
|
|
|
* If you do not have enough storage space allocated for the incoming data, the restoration fails.
|
|
** Make sure that your current system storage is configured to accept the restored data.
|
|
|
|
* You are attempting to restore data from a newer version of {microshift-short}.
|
|
** Ensure that the data you are restoring follows same versioning pattern as the update path. For example, if the destination version of {microshift-short} is an older version than the version of the {microshift-short} data you are attempting to use, the restoration can fail.
|