You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can manually back up and restore the {microshift-short} database on all supported systems. Greenboot health checks must be completed and you must stop the {microshift-short} service prior to any backups.
9
+
You can manually back up and restore the {microshift-short} database on all supported systems. For application data, you must create custom procedures.
10
10
11
-
[NOTE]
12
-
====
13
-
Only {microshift-short} data is backed up with the following procedures. Application data is not included.
14
-
====
15
-
16
-
* On `rpm-ostree` systems, {microshift-short} automatically creates a backup on every start. These automatic backups are deleted and replaced with the latest backup each time the system restarts.
17
-
* If you are using an `rpm-ostree` system, the data is automatically restored after Greenboot rolls the system back. This data restoration ensures that the database matches the software running on the host after the rollback is completed.
18
-
* On other system types, you must back up and restore data manually.
= About backing up and restoring {microshift-short} data
8
+
9
+
Before you can create a manual backup, greenboot health checks must finish running and you must stop the {microshift-short} service.
10
+
11
+
* On `rpm-ostree` systems, {microshift-short} automatically creates a backup on every start. These automatic backups are deleted and replaced with the latest backup each time the system restarts.
12
+
* Data is also automatically restored on an `rpm-ostree` system after a greenboot system rollback. This data restoration ensures that the database matches the software running on the host after the rollback is completed.
13
+
* On other system types, you must back up and restore data manually.
14
+
15
+
Automated backups are in the `/var/lib/microshift-backups` directory by default. You can use this directory for manually backing up and restoring data by specifying it in each command. When you restore a backup, you must use the entire file path.
16
+
17
+
[NOTE]
18
+
====
19
+
The following procedures only backup and restore {microshift-short} data. Application data is not included.
= Using automatic recovery in image mode for {op-system-base} systems
8
8
9
-
:FeatureName: Image mode for {op-system-base}
10
-
11
-
include::snippets/technology-preview.adoc[]
12
-
13
9
As a use case, consider the following example situation in which you want to automate the `auto-recovery` process for image mode for {op-system-base-full} systems that use the systemd service.
You can back up {microshift-short} data manually at any time. Back up your data before system updates to preserve it for use if an update fails or for other system trouble. Automated backups are created in the `/var/lib/microshift-backups` directory. You can use this directory for manually backing up and restoring data by specifying it in each command. When you create a backup, you must use the entire file path for the output file.
10
+
You can back up {microshift-short} data manually at any time. Back up your data before system updates to preserve it for use if an update fails or for other system trouble. You can use the `/var/lib/microshift-backups` for manually backing up and restoring data by specifying it in each command. When you create a backup, you must use the entire file path for the output file.
10
11
11
12
.Prerequisites
12
13
@@ -15,16 +16,15 @@ You can back up {microshift-short} data manually at any time. Back up your data
15
16
16
17
.Procedure
17
18
18
-
. Manually create a backup by using the parent directory and specifying a name, such as `/var/lib/microshift-backups/<my_manual_backup>`, by running the following command:
19
+
. Manually create a backup by using the parent directory and specifying a name, such as `/var/lib/microshift-backups/_<manual_backup>_`, by running the following command:
Replace `<other_backups_location>` with the directory you want to use and `<my_manual_backup>` with the backup name you want to use.
42
+
Replace `_<other_backups_location>_` with the directory you want to use and `_<my_manual_backup>_` with the backup name you want to use.
43
43
44
44
.Verification
45
-
* You can verify that the backup exists by viewing the data in the directory you chose. For example, `/var/lib/microshift-backups/<my_manual_backup>/` or `/mnt/<other_backups_location>/<another_manual_backup>`.
45
+
* You can verify that the backup exists by viewing the data in the directory you chose. For example, `/var/lib/microshift-backups/_<manual_backup>_/` or `/mnt/_<other_backups_location>_/_<another_manual_backup>_`.
= Restoring {microshift-short} data backups manually
8
9
9
-
You can restore {microshift-short} data from a backup manually. Backups can be restored after updates, or after other system events that remove or damage required data. Automated backups are in the `/var/lib/microshift-backups` directory by default. You can use this directory for manually backing up and restoring data by specifying it in each command. When you restore a backup, you must use the entire file path.
10
+
You can restore {microshift-short} data from a backup manually. Backups can be restored after updates, or after other system events that remove or damage required data. When you restore a backup, you must use the entire file path.
10
11
11
12
[NOTE]
12
13
====
13
-
On an `rpm-ostree` system, {microshift-short} backs up and restores data automatically.
14
+
On an `rpm-ostree` system, {microshift-short} backs up and restores data automatically. Automated backups are in the `/var/lib/microshift-backups` directory by default.
14
15
====
15
16
16
17
.Prerequisites
17
18
18
19
* Root access to the host.
19
-
* Full path of the data backup file.
20
+
* You have the full path of the data backup file.
20
21
* The {microshift-short} service is stopped.
21
22
22
23
.Procedure
23
24
24
25
. Manually restore {microshift-short} data by using the full file path of the backup you want to restore by running the following command:
Replace `<my_manual_backup>` with the backup name that you used. Optional: You can also restore automatic `ostree` backups using the full file path.
31
+
<1> Replace `_<manual_backup>_` with the backup name that you used. Optional: You can also restore automatic `ostree` backups using the full file path.
31
32
+
32
33
.Example output
33
-
+
34
34
[source,terminal]
35
35
----
36
36
??? I1017 07:39:52.055165 6007 data_manager.go:131] "Copying backup to data directory" storage="/var/lib/microshift-backups" name="test" data="/var/lib/microshift"
@@ -43,13 +43,18 @@ Replace `<my_manual_backup>` with the backup name that you used. Optional: You c
43
43
44
44
. Optional. Manually restore data from a customized directory by using the full file path of the backup. Run the following command:
Replace `<other_backups_location>` with the directory you used and `<my_manual_backup>` with the backup name you used when creating the backup you are restoring.
50
+
<1> Replace `_<other_backups_location>_` with the directory you used and `_<my_manual_backup>_` with the backup name you used when creating the backup you are restoring.
51
51
52
52
. Restart the host. Restarting the host enables all workloads and pods to restart.
53
53
54
54
.Verification
55
-
* Use the `oc get pods -A` command to verify that the cluster is running, then check the restored data.
55
+
56
+
* Use the `oc get pods -A` command to verify that the cluster is running, then check the restored data.
0 commit comments