第 1 章 Backing up and restoring MicroShift data
You can manually back up and restore the MicroShift database on all supported systems. Greenboot health checks must be completed and you must stop the MicroShift service prior to any backups.
Only MicroShift data is backed up with the following procedures. Application data is not included.
-
On
rpm-ostreesystems, MicroShift automatically creates a backup on every start. These automatic backups are deleted and replaced with the latest backup each time the system restarts. -
If you are using an
rpm-ostreesystem, 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. - On other system types, you must back up and restore data manually.
1.1. Stopping the MicroShift service 复制链接链接已复制到粘贴板!
Use the following procedure to stop the MicroShift service.
Prerequisites
- The MicroShift service is running.
Procedure
Enter the following command to stop the MicroShift service:
$ sudo systemctl stop microshiftWorkloads deployed on MicroShift might continue running even after the MicroShift service has been stopped. Enter the following command to display running workloads:
$ sudo crictl ps -aEnter the following commands to stop the deployed workloads:
$ sudo systemctl stop kubepods.slice