Backing up the content indexes

Contrary to legacy Content Manager (TRIM) versions before 7.21, TRIMEvent.exe is now incorporated in the Content Manager Workgroup Server and does not run as a service. Therefore, it is not possible any longer to stop it to back up the content indexes. Instead, you now have two options to pause content indexing for a content index backup using your own backup technique, and two more options to back up by using IDOL's built-in backup commands:

  • Suspend indexing, then back up the indexes
  • Stop the Workgroup service and then back up
  • Back up by using IDOL DREBACKUP
  • Export the index data as IDX files
  1. In Content Manager Enterprise Studio, suspend the Content Indexing processor - see Configuring event processing
  2. Save and deploy the new configuration to the running Workgroup Servers - see Content Manager Enterprise Studio Help
  3. Back up the two index databases using your preferred method.
    By default, these are C:\Micro Focus Content Manager\IDOL\TRIM Content Service 1 and TRIM Content Service 2. If your implementation of IDOL is using a different location, refer to the TRIM IDOL Service.cfg configuration file's Paths section to determine it.
  4. In Content Manager Enterprise Studio, enable the Content Indexing processor and save and deploy the new configuration.
    The Workgroup Servers continue processing.

You can use this method successfully under these circumstances:

  • Document content indexing is being processed on a single Workgroup Server
  • There are no users accessing Content Manager through the content indexing Workgroup Server
  1. When your system meets these requirements, stop the content indexing computer's Content Manager Workgroup Service
  2. Back up the two index databases using your preferred method
  3. Start the Content Manager Workgroup Service to continue processing

Autonomy IDOL enables you to back up your indexes manually or using a schedule.

  1. Make sure that at least one Content Manager IDOL Content Service is running on the server
  2. In an Internet browser window, enter in the address field: http://IDOLhost:IndexPort/DREBACKUP?path&HostDetails=True, for example http://mycomputer:9001/DREBACKUP?F:\Backups&HostDetails=True, replacing the following with your data:

    The parameter &HostDetails=True backs up the index to a backup path subfolder, which is named in the format hostname-port, e.g. mycomputer-9001. This makes it easy to distinguish between multiple server backups within that folder and enables you to restore a host-specific backup using that parameter, as well.

    The IDOL Server backs up the index data and saves it to the backup location.

    In the browser window, IDOL displays INDEXID= followed by the ID of the content index backup for your records.

  1. Using a text editor, navigate to the Content Manager installation folder and in each folder IDOL\TRIM Content Service [number], open the respective file TRIM Content Service [number].cfg
  2. Edit the section [Schedule]. If there is none, create one like the following:

    [Schedule]
    Backup=true
    BackupCompression=true
    BackupTime=08:00
    BackupInterval=24
    BackupMaintainStructure=true
    BackupRetryAttempts=3
    BackupRetryPause=5
    NumberOfBackups=3
    BackupDir0=F:\IDOLBackup\ContentServer2\1\
    BackupDir1=F:\IDOLBackup\ContentServer2\2\
    BackupDir2=F:\IDOLBackup\ContentServer2\3\

  3. Edit these parameters to with your backup settings:
    • BackupTime= followed by the backup start time in the format hh:mm
    • BackupInterval= followed by the number of hours between backups. Use 0 to back up daily.
    • NumberOfBackups= followed by the number of backups you want to maintain. IDOL creates the first backup and the next one after the number of hours for BackupInterval.

      When the index has been backed up as many times as specified in NumberOfBackups, IDOL overwrites the first backup, then the second, and so on. With multiple backups, you will always have a backup available, even if a backup was overwriting an existing backup and then failed, making both backups incomplete.

    • BackupDir[number]= followed by the path to the location to write the backup to. You must specify a path for as many BackupDir[number] parameters as you have specified in NumberOfBackups.
  4. Save your changes to the configuration files and close them.
    Your setup of scheduled backups is complete.

If you used the parameter &HostDetails=True to back up and arrange the data in host specific folders, you can use an Internet browser to send the DREINITIAL command.

  1. In the address field, enter http://IDOLhost:port/DREINITIAL?path&HostDetails=Trueand press Enter, for example http://mycomputer:9001/DREBACKUP?F:\Backups&HostDetails=True, replacing the following with your data:

    IDOL restores the backup to the server specified and displays INDEXID= followed by the index backup number that was restored.

To restore an individual IDOL Content Service's index, send the command without the parameter &HostDetails=True to the specific IDOL Content Service's index port, which is specified in its configuration file as IndexPort.

IDX files that were exported from IDOL can easily be moved to another IDOL environment, for example to add the data to an Enterprise IDOL instance.

  1. Using a browser, send: http://localhost:9001/DREEXPORTIDX?filename=c:/export/output&hostdetails=true.
    IDOL creates IDX.gz files in the export directory with a name starting with output, computer name and port details, for example export.myCMserver.domain.lab-9100-0.idx.gz.

To restore the data, send the DREADD command, for example:

http://localhost:9001/DREADD?c:\export\export.myCMserver.domain.lab-9100-0.idx.gz &DREDbname=CM_45

You need to run the command for each IDX file that was created in the export process. In the example above, IDOL would import the IDX file to the Content Manager database instance with the name CM_45.

Related Topics Link IconRelated information