Full Restoration of LogicalDOC on new server fails

We tried to make LogicalDOC as intuitive as possible, but an advice is always welcome.

Moderator: car031

die7fox
Posts: 51
Joined: Thu Sep 18, 2014 10:20 am

Full Restoration of LogicalDOC on new server fails

Wed Aug 15, 2018 5:38 pm

LogicalDOC 8.0.1 on CentOS 7

Hello. We recently suffered some catastrophic hardware loss due to a lightning strike. I am trying to restore my LogicalDOC backups to a new server. The application is already configured and activated. I'm getting some strange feedback from restore.sh. For one thing, it appears to be skipping some of my backup increments. Also, it's referring to a .bcfg file that does not appear in either my conf or ldbackup_config_backup folders (application.bcfg).

Below is the output I received when I ran restore.sh

Buildfile: ./build.xml

restore:
[echo] Restoring

init:

tomcat-stop:
[exec] /LogicalDOC/bin/logicaldoc.sh: line 42: /LogicalDOC/tomcat/bin/catalina.sh: No such file or directory
[echo] stopped
[echo] Restoring configs

restore-task:
[echo] /LogicalDOC/backup_home/conf/conf.bcfg
[exec] INFO - Configuration path : /LogicalDOC/backup_home/conf/conf.bcfg
[exec] INFO - Target : Incremental Backup
[exec] INFO - Recovery in progress ...
[exec] INFO - Data recovery ...
[exec] INFO - Recovering /mnt/backup/conf/20180713.zip (19 files) ...
[exec] INFO - 0%
[exec] INFO - Skipping /mnt/backup/conf/20180713_1.zip
[exec] INFO - Skipping /mnt/backup/conf/20180716.zip
[exec] INFO - 10%
[exec] INFO - Skipping /mnt/backup/conf/20180717.zip
[exec] INFO - Skipping /mnt/backup/conf/20180718.zip
[exec] INFO - 20%
[exec] INFO - Skipping /mnt/backup/conf/20180719.zip
[exec] INFO - Skipping /mnt/backup/conf/20180720.zip
[exec] INFO - Skipping /mnt/backup/conf/20180723.zip
[exec] INFO - 30%
[exec] INFO - Skipping /mnt/backup/conf/20180724.zip
[exec] INFO - Skipping /mnt/backup/conf/20180725.zip
[exec] INFO - 40%
[exec] INFO - Skipping /mnt/backup/conf/20180726.zip
[exec] INFO - Skipping /mnt/backup/conf/20180727.zip
[exec] INFO - Skipping /mnt/backup/conf/20180730.zip
[exec] INFO - 50%
[exec] INFO - Skipping /mnt/backup/conf/20180731.zip
[exec] INFO - Skipping /mnt/backup/conf/20180801.zip
[exec] INFO - 60%
[exec] INFO - Skipping /mnt/backup/conf/20180802.zip
[exec] INFO - Skipping /mnt/backup/conf/20180803.zip
[exec] INFO - Recovering /mnt/backup/conf/20180806.zip (3 files) ...
[exec] INFO - 70%
[exec] INFO - Recovering /mnt/backup/conf/20180807.zip (2 files) ...
[exec] INFO - Recovering /mnt/backup/conf/20180808.zip (2 files) ...
[exec] INFO - 80%
[exec] INFO - Recovering /mnt/backup/conf/20180809.zip (2 files) ...
[exec] INFO - Recovering /mnt/backup/conf/20180810.zip (5 files) ...
[exec] INFO - 90%
[exec] INFO - 100%
[exec] INFO - Creating missing directories and symbolic links ...
[exec] INFO - Applying metadata ...
[exec] INFO - Metadata applied.
[exec] INFO - Recovery completed.
[move] Moving 33 files to /LogicalDOC/conf
[echo] Restoring the application
[delete] Deleting directory /LogicalDOC/tomcat
[mkdir] Created dir: /LogicalDOC/tomcat

restore-task:
[echo] /LogicalDOC/backup_home/conf/application.bcfg
[exec] INFO - /LogicalDOC/backup_home/conf/application.bcfg does not exist (not migrated to new configuration format yet). Switching to /LogicalDOC/backup_home/conf.xml with target uid : application.
[exec] INFO - ------------------------------------------------------------------
[exec] INFO - LogicalDOC Backup
[exec] INFO - Copyright 2005-2014, LogicalDOC
[exec] INFO - List of valid arguments :
[exec] INFO -
[exec] INFO - Show informations about LogicalDOC Backup :
[exec] INFO - infos
[exec] INFO -
[exec] INFO - Describe targets :
[exec] INFO - describe -config (xml configuration file or directory)
[exec] INFO -
[exec] INFO - Launch a backup :
[exec] INFO - backup -config (xml configuration file or directory) [-f] [-d] [-c] [-wdir (working directory)] [-s] [-title (archive title)]
[exec] INFO - -f to force full backup (instead of incremental backup)
[exec] INFO - -d to force differential backup (instead of incremental backup)
[exec] INFO - -c to check the archive consistency after backup
[exec] INFO - -wdir to use a specific working directory during archive check
[exec] INFO - -resume to resume a pending backup if found
[exec] INFO - -cresume (nb days) to resume a pending backup if younger than 'nb days'
[exec] INFO - -s to disable asynchronous processing when handling a target group
[exec] INFO - -title to set a title to the archive
[exec] INFO -
[exec] INFO - merge -config (xml configuration file) [-title (archive title)] [-k] -date (merged date : YYYY-MM-DD) / -from (nr of days - 0='-infinity') -to (nr of days - 0='today')
[exec] INFO - Merge archives :
[exec] INFO - -k to keep deleted files in the merged archive
[exec] INFO - -title to set a title to the archive
[exec] INFO - -c to check the archive consistency after merge
[exec] INFO - -wdir to use a specific working directory
[exec] INFO - -date to specify the reference date used for merging
[exec] INFO -
[exec] INFO - OR -from/-to (nr of days) to specify the archive range used for merging
[exec] INFO - Delete archives :
[exec] INFO - delete -config (xml configuration file) [-date (deletion date : YYYY-MM-DD) / -delay (nr of days)]
[exec] INFO -
[exec] INFO - Recover archives :
[exec] INFO - recover -config (xml configuration file) -destination (destination folder) [-date (recovered date : YYYY-MM-DD)] [-c]
[exec] INFO - -c to check consistency of recovered files
[exec] INFO - -o to overwrite existing files
[exec] INFO - -nosubdir to prevent LogicalDOC Backup to perform the recovery in a subdirectory
[exec] INFO - -date to specify the recovery date
[exec] INFO -
[exec] INFO - Check archives :
[exec] INFO - check -config (xml configuration file) [-wdir (working directory)] [-date (checked date : YYYY-MM-DD)] [-a]
[exec] INFO - -wdir to use a specific working directory
[exec] INFO - -a to check all files (not only those contained in the archive denoted by the date argument)
[exec] INFO - -date to specify the archive which will be checked
[exec] INFO -
[exec] INFO - ------------------------------------------------------------------
[exec] INFO - Error : invalid arguments (Invalid target UID : application)
[exec] INFO - recover -config /LogicalDOC/backup_home/conf/application.bcfg -destination /LogicalDOC/tomcat
[echo] The following error occurred while executing this line:
[echo] /LogicalDOC/backup_home/build.xml:546: The following error occurred while executing this line:
[echo] /LogicalDOC/backup_home/build.xml:47: exec returned: 2

BUILD FAILED
/LogicalDOC/backup_home/build.xml:585: The following error occurred while executing this line:
/LogicalDOC/backup_home/build.xml:546: The following error occurred while executing this line:
/LogicalDOC/backup_home/build.xml:47: exec returned: 2

Total time: 2 seconds

I can provide more information if needed. Thanks for your help!
agaspa
Posts: 628
Joined: Tue Apr 20, 2010 8:24 am

Re: Full Restoration of LogicalDOC on new server fails

Tue Aug 21, 2018 8:19 am

Hi die7fox,

in the context.properties of the backup locate the key restore.application and put restore.application=false
This avoids the deletion of the application folder.

Then i see the database was not restored so in the same file locate the settings db.xxx and properly configure the connection to the database.
Also locate the setting restore.db.command and there put the path to your mysql command.

Return to “Usage”

Who is online

Users browsing this forum: No registered users and 1 guest