Background:
During the daily use of the RPM, the RPM database is abnormal. However, the
cause is unknown. In some cases, the `rpm --rebuilddb` cannot ensure the
complete recovery of the database. For recoverability and locatability, I think
database backup functionality can be added for the following reasons:
1. If the database is abnormal after a command is executed, we can use the
backup database directory to construct the onsite scenario to facilitate fault
locating.
2. We can replace the abnormal directory with the normal database that is
backed up before.
I have a preliminary solution idea:
1. A configuration switch is added to control whether to enable this feature.
2. Add the configuration to determine the location of the backup database
directory and the number of database directories to run the backup.
3. Back up the database directory after the installation/uninstallation/upgrade
transaction is complete, and the backup database is controlled by .rpm.lock.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2828
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
