mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
23 lines
1.2 KiB
Plaintext
23 lines
1.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * updating/preparing_for_updates/updating-cluster-prepare.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="update-etcd-backup_{context}"]
|
|
= etcd backups before cluster updates
|
|
|
|
etcd backups record the state of your cluster and all of its resource objects.
|
|
You can use backups to attempt restoring the state of a cluster in disaster scenarios where you cannot recover a cluster in its currently dysfunctional state.
|
|
|
|
In the context of updates, you can attempt an etcd restoration of the cluster if an update introduced catastrophic conditions that cannot be fixed without reverting to the previous cluster version.
|
|
etcd restorations might be destructive and destabilizing to a running cluster, use them only as a last resort.
|
|
|
|
[WARNING]
|
|
====
|
|
Due to their high consequences, etcd restorations are not intended to be used as a rollback solution.
|
|
Rolling your cluster back to a previous version is not supported.
|
|
If your update is failing to complete, contact Red{nbsp}Hat support.
|
|
====
|
|
|
|
There are several factors that affect the viability of an etcd restoration.
|
|
For more information, see "Backing up etcd data" and "Restoring to a previous cluster state". |