Database & Backups
This page describes common deployment issues in connection to the database settings of Fineract 1.x
Flyway Upgrades Related:
Apache Fineract will not support the Enterprise license version of flyway with MariaDB as such; this is a conflict of interest (the project PMC had to drop the GPL-based Pentaho reporting engine.)
Relevant Documentation:
DB Names have changed after the flyway upgrade in the upstream code base.
Maintaining Backups
How to Maintain Regular Backups:
Backups
MySQL periodic backups have to be preserved using a cronjob or a service internally, which can simply store and take a snapshot every week or based on the requirement.
In the database connection issues, it is recommended to maintain regular backups.
Mysql dump files can be generated to save or backup data from a database at any time. This can later be recovered when need be. This comes in handy to:
Create a DB script containing specific baseline configurations relevant to a generic use case such that each time deployment fails; the script revives the db values of these configurations setup.
Save the state of the database and recover it whenever necessary.
Backup and Restore a MySQL database from a running docker mysql container To Backup:
where fineract_default is the source database, and baseline_config.sql will contain the backup data.
To Restore:
where fineract_default is the destination database, and baseline_config.sql is the source from which the data is to be restored.
Relevant Documentation:
https://mifosforge.jira.com/wiki/spaces/docs/pages/98107409/Mifos+X+Database+Backup+and+Restore
Last updated
