1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00

Merge pull request #23015 from openshift-cherrypick-robot/cherry-pick-22807-to-enterprise-4.5

[enterprise-4.5] Bug 1847769: backup_and_restore: clarify backup process
This commit is contained in:
Andrea Hoffer
2020-06-18 11:18:45 -04:00
committed by GitHub
2 changed files with 11 additions and 4 deletions

View File

@@ -15,11 +15,15 @@ installation, otherwise the backup will contain expired certificates. It is also
recommended to take etcd backups during non-peak usage hours, as it is a
blocking action.
Once you have an etcd backup, you can xref:../backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[restore to a previous cluster state].
[IMPORTANT]
====
You back up your cluster's etcd data by performing a single invocation of the backup script on a master host. Do not take a backup for each master host.
====
After you have an etcd backup, you can xref:../backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[restore to a previous cluster state].
You can perform the xref:../backup_and_restore/backing-up-etcd.adoc#backing-up-etcd-data_backup-etcd[etcd data backup process]
on any master host that has connectivity to the etcd cluster, where the proper
certificates are provided.
on any master host that has a running etcd instance.
// Backing up etcd data
include::modules/backup-etcd.adoc[leveloffset=+1]

View File

@@ -7,7 +7,10 @@
Follow these steps to back up etcd data by creating an etcd snapshot and backing up the resources for the static Pods. This backup can be saved and used at a later time if you need to restore etcd.
You should only save a backup from a single master host. You do not need a backup from each master host in the cluster.
[IMPORTANT]
====
Only save a backup from a single master host. Do not take a backup from each master host in the cluster.
====
.Prerequisites