You can back up the entire IDOL Content component data index in several ways:
Immediately, using a DREBACKUP index action.
NOTE: You can also back up Content by using the BackupServer ACI action. However, Micro Focus generally recommends that you use the index action, because BackupServer uses an ACI thread, which reduces the number of other processes that Content can run.
At regular intervals, by setting up a scheduled backup.
Dynamically, by taking a snapshot of the data.
Send a DREBACKUP action (case sensitive) from your Web browser to copy all the IDOL Content component data index *.DB files to a new location.
http://ContentHost:indexPort/DREBACKUP?Path=path
where:
|
|
is the IP address or host name of the Content machine. |
|
|
is the Content index port (specified by the |
|
|
is the path to the location where you want to create the backup. In Windows, you can use a Unicode path. |
For example:
http://MyHost:20001/DREBACKUP?Path=E:\Backup
This action uses port 20001 to create a backup of the Content data index on E:\Backup. The Content whose data index is backed up is located on a machine with the host name MyHost.
You can set the optional parameter CheckIndexUpdates to True if you want to check for updates to the index since the last backup. In this case, Content skips the backup if the index has not been modified.
DREBACKUP also accepts the optional parameter HostDetails. Set HostDetails to True to write the backup to a subdirectory in the specified directory path. Content names this directory using its host and port. In this way, a series of servers under a Distributed Index Handler (DIH) can all accept the same directory as input, and they write to a subdirectory named with their own host and port.
Use the following procedure to back up the data index at regular intervals.
Open the IDOL Content component configuration file in a text editor.
[Schedule] section. If the configuration file does not contain a [Schedule] section, add one.Specify the following parameters in the [Schedule] section:
For example:
[Schedule] Backup=True BackupCompression=True BackupTime=00:00 BackupInterval=24 BackupMaintainStructure=True BackupRetryAttempts=3 BackupRetryPause=5 NumberOfBackups=3 BackupDir0=E:\DataIndex_Backup0 BackupDir1=E:\DataIndex_Backup1 BackupDir2=E:\DataIndex_Backup2
Use the following procedure to back up the data index automatically whenever you send a DRECOMPACT action.
Open the IDOL Content component configuration file in a text editor.
[Schedule] section. If the configuration file does not contain a [Schedule] section, add one.Specify the following parameters in the [Schedule] section:
PreCompactionBackup
|
Set this parameter to The backup maintains the Content directory structure. You can compress the backup by setting |
PreCompactionBackupPath
|
If you set If Content shuts down without completing a compaction, it uses the contents of this directory to restore itself. |
If your IDOL Content component storage is a SAN with disk-snapshot capabilities, you can perform a hot backup (snapshot) of the data index.
Send the DREFLUSHANDPAUSE action to prepare Content for the hot backup by flushing all files to disk and pausing indexing:
http://IDOLhost:indexPort/DREFLUSHANDPAUSE?
Note the index ID returned from this action (for example, INDEXID=41); you need this ID later to restart the paused indexing queue.
Poll Content with the IndexerGetStatus action to view the status of the flush and pause process:
<autnresponse> <action>INDEXERGETSTATUS</action> <response>SUCCESS</response> <responsedata> <item> <id>41</id> <origin_ip>127.0.0.1</origin_ip> <received_time>2006/10/06 13:47:15</received_time> <start_time>2006/10/06 13:47:16</start_time> <end_time>Finished</end_time> <duration_secs>0</duration_secs> <percentage_processed>0</percentage_processed> <status>-16</status> <description>Indexing Paused</description>* <index_command>/DREFLUSHANDPAUSE? HTTP/1.1</index_command> </item> </responsedata> </autnresponse>
When the returned status is –16 (Indexing Paused), you can perform the hot backup.
Take the snapshot according to the procedures defined by your SAN.
After the snapshot completes, restart the indexing queue. Issue another IndexerGetStatus action, this time specifying a Restart action:
action=IndexerGetStatus&Index=indexNum&IndexAction=restart
where indexNum is the index ID (for example, 41) returned from DREFLUSHANDPAUSE.
|
|