Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
2500_config_apps:3400_backup_restore [2026/08/13 00:55] – removed - external edit (Unknown date) 127.0.0.12500_config_apps:3400_backup_restore [2026/08/13 07:33] (current) – Imported by DokuWiki Advanced Plugin aware_support3
Line 1: Line 1:
 +[<10>]
 +====== Backing up and Restoring Operational Data ======
 +
 +The operational data stored by a system is its most valuable asset. All precautions must be taken to preserve its integrity. It is highly recommended to perform regular database backups and certainly it is a very good idea to perform a backup before [[2500_config_apps:0200_work_bsv:0700_publishing_bsv|publishing]] a new business space version. 
 +
 +As backup and restore processes are quite sensitive it is also recommended to perform them when no one is using the system in the Operation Mode.
 +
 +//**AwareIM**// uses two databases with the default names ''BASDB'' and ''BASDBTEST''. These two databases need to be backed up on a regular basis. Generally, it is recommended that the database backup be performed using the tools provided by the specific database used with //**AwareIM**//. In certain cases, it is possible to perform a simple directory backup. For example, if the default Derby/Cloudscape database is used it is possible to backup the DATA directory located underneath the root directory of the //**AwareIM**// installation. To restore the data after the backup all you need to do is overwrite the ''DATA'' directory with the files from the backup.
 +
 +<alert type="danger" icon="fa times-circle">
 +**warning**
 +
 +If you are just doing development and do not care about current data, then all you need is a BSV, so make sure you always have the current BSV file whenever you do something make sure that you save your work. If something goes wrong during publishing the version the easiest solution is recreate a business space and re-import the BSV. This should always work fine as the BSV includes everything. 
 +
 +\\ If you do have production data already that you care about then any publishing of a new BSV that involves changes to the database structure (business objects and attributes) should be considered a __MAJOR EVENT__. If anything goes wrong during the publishing operation you may lose your data. This is especially the case when you rename your objects/attributes and/or change the types of existing attributes.\\ \\ So you need to prepare properly for this. Before you publish you need to export the current BSV (and the new one) and perform a __FULL BACKUP__ of the current database.\\ \\ If __ANYTHING GOES WRONG__ during publishing the first thing you need to do is __RESTORE THE DATABASE FROM THE FULL BACKUP. NEVER DO ANY FURTHER WORK ON THE DATABASE THAT YOU ENDED UP WITH AFTER PUBLISHING ERROR__.\\ \\ The full restore should restore everything properly - there should be no report or any other errors. This is because the full snapshot of the database should include __EVERYTHING THAT THE SYSTEM NEEDS__ to work properly.</alert>
 +
 +An alternative to performing backup/restore of the database is to use the the Data Migration feature (see [[2500_config_apps:3450_bulk_data_export]]). Using this feature, you can perform export of the entire operational data of a business space to create a backup file and then import the file to restore the operational data.