Note: This applies to DocuShare 6.6.x and 7.
Note: You should consider the amount of disk space this might take if backing up to disk.
To configure IDOL to do scheduled automatic backups
1. Stop DocuShare.
2. Make a copy of the \IDOLServer\IDOL\AutonomyIDOLServer.cfg file and save the rename the copy AutonomyIDOLServer.cfg.orig.
3. Open the AutonomyIDOLServer.cfg in a text editor.
4. Add a [Schedule] section, if not present, and set the following parameters:
Note: If you are running more than one content you will need to edit the content0.cfg and content1.cfg instead.
[Schedule]
Backup=true
BackupCompression=true --(creates compressed backup files)
BackupTime=00:00 --(midnight; use 24 hour notation)
BackupInterval=0 --(elapsed time in hours between backups; 0=everyday)
BackupMaintainStructure=true
NumberOfBackups=2 --(backup cycles through each one)
BackupDir0=/contentX_Backup0 --(backup0 directory location ... must be unique for each content0 and content1)
BackupDir1=/contentX_Backup1
Note: The value for the BackupInterval needs to elapse before the first backup occurs. For example: If BackupInterval is set to 0, one full day would need to elapse for the first backup to occur.
Note: The BackupInterval time gets reset every time DocuShare is restarted. For example: If BackupInterval is set to 0 (every day) and DocuShare was restarted, one full day would need to elapse for the next backup to occur.
Note: The number of backups must correspond to the number of BackupDirN directories that are specified.
5. Save the file.
6. Start DocuShare.
7. Verify if the scheduled automatic IDOL backup worked.
Note: If you have more than one content configured you will need to look in each content to verify the automatic backup worked.
a. Open the \IDOLServer\IDOL\logs\content_application.log or if running more than one content \content\logs\application.log and review the entries. (See example below)
b. Open the \IDOLServer\IDOL\logs\content_index.log or if running more than one content \IDOLServer\content\logs\index.log and review the entries. (See example below)
c. You can also verify by making sure the backup resides in the destination directory.
Example of the \IDOLServer\IDOL\logs\content_application.log:
21/10/2013 13:36:40 [1] Backing up database into existing directory 'C:\BackupIDOL'
21/10/2013 13:36:40 [1] Backing up "Main" files into directory 'C:\BackupIDOL/main'
21/10/2013 13:36:40 [1] Backing up "Status" files into directory 'C:\BackupIDOL/status'
21/10/2013 13:36:40 [1] Backing up "Dynterm" files into directory 'C:\BackupIDOL/dynterm'
21/10/2013 13:36:43 [1] Backing up "Nodetable" files into directory 'C:\BackupIDOL/nodetable'
21/10/2013 13:36:44 [1] Backing up "Refindex" files into directory 'C:\BackupIDOL/refindex'
21/10/2013 13:36:44 [1] Backing up "Numeric" files into directory 'C:\BackupIDOL/numeric'
21/10/2013 13:36:44 [1] Backing up "BitField" files into directory 'C:\BackupIDOL/bitfield'
21/10/2013 13:36:44 [1] Backing up "Secindex" files into directory 'C:\BackupIDOL/secindex'
21/10/2013 13:36:44 [1] Backing up "TagIndex" files into directory 'C:\BackupIDOL/tagindex'
21/10/2013 13:36:44 [1] Backing up "SortField" files into directory 'C:\BackupIDOL/sortfield'
21/10/2013 13:36:44 [1] Backing up "IndexQueue" files into directory 'C:\BackupIDOL/indexqueue'
21/10/2013 13:36:44 [1] Backup Complete.
Example of the \IDOLServer\IDOL\logs\content_index:
21/10/2013 13:36:40 [0] Index Queue Command: /DREBACKUP?C:\BackupIDOL
21/10/2013 13:36:40 [1] Index Queue Command: DREBACKUP?C:\BackupIDOL
21/10/2013 13:36:44 [1] Index command finished. Took 4.02 s
To Restore the IDOL Content Index Data from Backup
1. Stop DocuShare.
2. Open a Command Prompt Window or Terminal Window.
3. Change into the \bin directory.
4. Run idoltool -s resetserver all y and press Enter.
5. Start DocuShare.
6. Run the one of the following commands depending on your environment.
· idoltool.bat -s restore (Windows)
· idoltool.sh -s restore (Linux / Solaris).
Where <path to backup directory> is replaced with the path to the backup folder. For example, D:\content_backup.
Note: If you are running multiple content engines, the restore command will need to be modified and run on each content.
Example:
For content0: idoltool.sh -s restore /content0_backup0 content0
For content1: idoltool.sh -s restore /content1_backup0 content1
Below are examples of the information that will be displayed in the log files after performing the command line restore in step 6 above.
Below are examples of the information that will be displayed in the log files after performing the command line restore in step 6 above.
Example of the <dshome>/logs/idoltool.log:
20131021 15:40:22 - Submitted DREINITIAL, jobid = 1
20131021 15:40:24 - waitForJobCompletion: id = 1: Finished; documents processed: 0...
20131021 15:40:24 - restore: Done.
Note: If you are running multiple content engines the logs displayed in examples below will be named slightly different and will be found in the following locations.
For Content0: <dshome>\IDOLServer\content0
· application.log
· index.log
For Content1: <dshome>\IDOLServer\content1
· application.log
· index.log
Example of the <dshome>/IDOLServer/IDOL/logs/content_index.log:
20131021 15:40:22 - Submitted DREINITIAL, jobid = 1
20131021 15:40:24 - waitForJobCompletion: id = 1: Finished; documents processed: 0...
20131021 15:40:24 - restore: Done.
7. Once the restore has completed, run one of the following commands from the <dshome>\bin directory.
For Sites running DocuShare 7 or 6.6.1 Update 3 and higher.
· Dsindex.bat -reindexSince MM/dd/yyyy-MM/dd/yyy index_all (Windows)
· Dsindex.sh -reindexSince MM/dd/yyyy-MM/dd/yyy index_all (Solaris)
Notee: The MM/dd/yyyy should be set to a date shortly before the backup was created.
Example: dsindex -reindexSince 05/01/2019-05/30/2019 index_all
This command re-indexes all objects with modified/create date at or after 05/01/2019 (inclusive) and before 05/30/2019 (exclusive).
For sites running DocuShare 6.6.x Update 2 and below:
· reindexChangesSince.bat MM/dd/yyyy hh:mm:ss (Windows)
· reindexChangesSince.sh MM/dd/yyyy hh:mm:ss (Solaris)
Note: The MM/dd/yyyy hh:mm:ss should be set to a time shortly before the backup was created.
Solution Published: November 26, 2019
Solution ID: 2010