WSO2 Open Banking does not persist data in the file systems or retain or generate artifacts. By default, we only store log files in the file system and data and artifacts in the databases and the repository.
...
- Database backups:
- Back up of all the databases defined in
<WSO2_OB_KM_HOME>/repository/conf/datasources/master-datasources.xmland<WSO2_OB_APIM_HOME>/repository/conf/datasources/master-datasources.xml. - Back up any other databases configured in any files in the
<WSO2_OB_KM_HOME>/repository/conf/datasourcesdirectory and<WSO2_OB_APIM_HOME>/repository/conf/datasources.
- Back up of all the databases defined in
- Artifact backups:
This includes hot-deployment artifacts, web applications, synapse files, tenant directories, etc. Back up of the<WSO2_OB_KM_HOME>/repository and<WSO2_OB_APIM_HOME>/repositorydirectories periodically. The frequency of the backups depends on your usage. For example, if you are creating or updating APIs daily, take this backup daily. - WSO2 product Open Banking instance backups:
A one-time-only backup that you take of the entire server directory. This includes all the configuration files, logs, server extensions, and deployment artifacts for both tenants and super tenants. This back up is ideally done when the server is ready to be deployed in a production environment.
...
We recommend that you use a proper artifact management system such as Puppet to back up and manage your artifacts before deploying them in the WSO2 Carbon runtime. Also, use the WSO2 Update Manager (WUM) tool, which is a command-line utility that allows you to get the latest updates (bug fixes and security fixes) of a particular product release.
Diagram: managing your artifacts using a configuration management system
...
- Recover the hot-deployment artifacts by replacing the
<WSO2_OB_KM_HOME>/repository and<WSO2_OB_APIM_HOME>/repositorydirectories with the backed up copy. - Recover the entire WSO2 Open Banking solution by directly replacing the existing WSO2 server directory in the production setup with the backup server directory. This will ensure that all the files, logs, and configurations made to the solution do not need to be redone.
- To recover the databases, follow the recovery strategy recommended by the databases you are using. For information on supported and tested databases, see Prerequisites for WSO2 Open Banking.