Help Center

Burgeonsoft | Contact Us | Chinese

Restore Backup Archive

 

If your document storage unfortunately is damaged, for example, hard disk error, or you need to migrate the data to another DocCare instance, you may need to backup the data and restore the backup archive.

First, shut down DocCare if it is running.
Second, install a 'clean' DocCare instance for restoring the data.
The 'clean' means:

  • An empty database schema. You can delete all the tables and view in the existed schema or drop then create a new schema. The tables and view will be created automatically when restoring.
  • Check the JDBC configuration. The configuration file is ${BURGEON_HOME}/conf/database.properties. Detail to seeConfigure JDBC Connection
  • Empty the document repository. You can delete the whole document repository or move it to anywhere. The path of document repository is defined in RESOURCE_REPOSITORY parameter in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml.
    DocCare will re-build the document repository while restoring.
  • Emptly user action logs. You can delete the them or move them to anywhere. The path of user action logs is defined in USER_LOG_DIR parameter in ${BURGEON_HOME}/deploy/resourcemanager.sar/services.xml.
    DocCare will restore the user action logs from the backup archive.
  • Empty ${BURGEON_HOME}/data except directory 'template'. DocCare will re-build the document index while restoring.
  • Delete or rename ${BURGEON_HOME}/install directory. DocCare will restore the installation info and user license file.

Or, you can just create a new DocCare instance and copy the modified configuration files from old DocCare instance to the new one.
Thus, you can quickly build a 'clean' DocCare instance.

After you have done all of the above works, you can execute the following command,
On Windows platform, execute:
${BURGEONSOFT_HOME}\bin\restore.bat <absolute_path_of_the_backup_archive>
For example:

C:\DocCare\bin>restore.bat D:\backups\BAK20071127101852.zip --ignore-error

On Unix/Linux platform, execute:
{BURGEONSOFT_HOME}/bin/doccare.sh restore <absolute_path_of_the_backup_archive>
For example:

[burgeonsoft][~]$ bin/doccare.sh restore /opt/backups/BAK20071127101852.zip --ignore-error

DocCare will re-build the document index during the migration.
If the size of the backup archive is very large, the migration may cost a long time. Currently, DocCare does not know when the migration will complete. If you see ‘Closed Resource Index’ from console output, then it means the migration is completed. You can press Ctrl+C to exit the migration.
After migration is done, you can start DocCare as normal.



Relate topics: