Recovering the index

You can recover the index by reverting to a particular baseline or partial update.

You can revert the MDEX Engine to the index representing the state of data after a specific baseline or partial update. To do so, restart the MDEX Engine on the index files that were backed up after this baseline update, and point the MDEX Engine at the dgraph_input/updates directory that contains partial update files that occurred since this baseline update.

To revert to a previously applied baseline or partial update:

  1. Stop the MDEX Engine.

  2. Clean up the active dgraph_input and dgraph_input/updates directories.

  3. In the backup directory for baseline update files, locate the files from the last successful baseline update.

  4. Copy the backed-up baseline update files into dgraph_input.

  5. In the backup directory for partial update XML files, locate the files since the baseline update you are reverting to.

  6. Copy all backed-up partial update XML configuration files from all partial updates that occurred since the baseline update to which you want to revert into the dgraph_input/updates directory.

    If you are using the Deployment Template, the app-dir/data/partials/cumulative_partials directory is where all partial updates since the last baseline are typically stored. You can reapply them by copying the necessary files to the Dgraph updates directory and apply the updates afterwards.

  7. Restart the MDEX Engine. The MDEX Engine reads the files in dgraph_input and in dgraph_input/updates.

If you are using the Deployment Template, the numPartialsBackups setting (in the PartialForge module of the AppConfig.xml configuration file) determines how many cumulative partials to store. If you do not define this number high enough, you may not have all the previous update files to even restore the state of the index. If this is the case, you will have to run a full baseline.

Copyright © Legal Notices