1.3. Restoring MicroShift data backups manually
You can restore MicroShift data from a backup manually. You can restore backups 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.
On an rpm-ostree system, MicroShift backs up and restores data automatically.
Prerequisites
- Root access to the host.
- Full path of the data backup file.
- The MicroShift service is stopped.
Procedure
Manually restore MicroShift data by using the full file path of the backup you want to restore by running the following command:
$ sudo microshift restore /var/lib/microshift-backups/<my_manual_backup>Replace
<my_manual_backup>with the backup name that you used. Optional: You can also restore automaticostreebackups using the full file path.Example output
??? 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" ??? I1017 07:39:52.055243 6007 data_manager.go:154] "Renaming existing data dir" data="/var/lib/microshift" renamedTo="/var/lib/microshift.saved" ??? I1017 07:39:52.055326 6007 data_manager.go:227] "Starting copy" cmd="/bin/cp --verbose --recursive --preserve --reflink=auto /var/lib/microshift-backups/test /var/lib/microshift" ??? I1017 07:39:52.061363 6007 data_manager.go:241] "Finished copy" cmd="/bin/cp --verbose --recursive --preserve --reflink=auto /var/lib/microshift-backups/test /var/lib/microshift" ??? I1017 07:39:52.061404 6007 data_manager.go:175] "Removing temporary data directory" path="/var/lib/microshift.saved" ??? I1017 07:39:52.063745 6007 data_manager.go:180] "Copied backup to data directory" name="test" data="/var/lib/microshift"Optional. Manually restore data from a customized directory by using the full file path of the backup. Run the following command:
$ sudo microshift restore /<mnt>/<other_backups_location>/<another_manual_backup>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.- Restart the host. Restarting the host enables all workloads and pods to restart.
Verification
Use the
oc get pods -Acommand to verify that the node is running, then check the restored data.$ oc get pods -AExample output
NAMESPACE NAME READY STATUS RESTARTS AGE default i-06166fbb376f14a8bus-west-2computeinternal-debug-qtwcr 1/1 Running 0 46m kube-system csi-snapshot-controller-5c6586d546-lprv4 1/1 Running 0 51m openshift-dns dns-default-45jl7 2/2 Running 0 50m openshift-dns node-resolver-7wmzf 1/1 Running 0 51m openshift-ingress router-default-78b86fbf9d-qvj9s 1/1 Running 0 51m openshift-ovn-kubernetes ovnkube-master-5rfhh 4/4 Running 0 51m openshift-ovn-kubernetes ovnkube-node-gcnt6 1/1 Running 0 51m openshift-service-ca service-ca-bf5b7c9f8-pn6rk 1/1 Running 0 51m openshift-storage topolvm-controller-549f7fbdd5-7vrmv 5/5 Running 0 51m openshift-storage topolvm-node-rht2m 3/3 Running 0 50m注意This example output shows a basic MicroShift installation. If you installed optional RPMs, the status of pods running those services is also expected in your output.