Restore DocCare2 from Server Failure

Standby DocCare2 server

If the DocCare2 server broken down, the following deployment allows you continue to use DocCare2 in seconds.

Figure: Deploy a standby DocCare2 server for fast recovery.

In the above deployment, if the working DocCare2 server broke down, you can start the standby DocCare2 server. All users can still use DocCare2 without any impact.

Restore Backup Archive

If your file repository is damaged, for example, the hard disk is damaged, you can restore DocCare2 data from your backup archives.
First, shutdown DocCare2 server if it is already started.
Second, you need to setup a ‘clean’ DocCare2 for the recovery.
The ‘clean’ means:

• Empty database. You should drop all existing tables or create a new database for DocCare2. The recovery will restore all tables with backup data. If you create a new database, you should also re-configure database connection in ${BURGEON_HOME}/conf/database.properties.
• Empty file repository. You should delete or move all contents away from the file repository which is defined in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml, attribute RESOURCE_REPOSITORY. DocCare2 will restore all folders and documents into the file repository.
• Empty user log directory. You should delete or move all contents away from the user log directory which is defined in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml, attribute USER_LOG_DIR. DocCare2 will restore all user action logs into this directory.
• Empty ${BURGEON_HOME}/data. DocCare2 will rebuild indexes while restoring the data.
• You should also rename ${BURGEON_HOME}/install directory. The recovery will create this directory automatically and restore database schema, installation info and license info in it.

Finally, you can execute the following command.
In Windows System, simply run:
${BURGEONSOFT_HOME}\bin\restore.bat absolute_path_of_backup_archive
For example:
C:\DocCare2>restore.bat D:\backups\BAK20071127101852.zip

In Unix/Linux System, execute the script:
${BURGEONSOFT_HOME}/bin/doccare.sh restore absolute_path_of_backup_archive
For example:
[burgeonsoft][~]$ bin/doccare.sh restore /opt/backups/BAK20071127101852.zip

DocCare2 will also rebuild the search indexes during the restoration.
If the backup archive has a large size, the restoration may take a long time. DocCare2 won’t send out a signal to indicate if the restoration is completed. We’ll improve this in future release. Currently, you can check the console output log. If you see the console log print out ‘Closed Resource Index’, that means the restoration completed. You can press Ctrl+c to exit the restoration process.

After restoration, you can just restart DocCare2 and have fun with it as usual.