Use the recommendations provided in this section to back up the Endeca index files used by the MDEX Engine.
Back up the Dgraph input directory after each baseline update. Periodically, back up the dgraph_input directory and all its subdirectories to an alternate location. dgraph_input is the directory where the MDEX Engine index is stored. When backing it up, ensure that you use a naming scheme that will allow you to retrieve baseline update files based on date and time.
Back up the dgraph_input directory only when the MDEX Engine is stopped. Do not back up this directory when the Dgraph is running. If you try to copy it while the Dgraph is running, you may capture files in an inconsistent state.
Back up partial update files. Prior to running partial updates, ensure that the partial update files are saved automatically in another backup directory. You may need to modify your partial updates script so that this backup occurs automatically. Use a time stamp naming scheme to ensure that you can retrieve the update files if needed.
The files in the dgraph_input/updates directory are deleted after a partial update completes successfully. Therefore, if you want to revert to a particular partial update, back up all files and subdirectories in this directory.
Periodically delete previous backups of partial update files. In other words, you do not have to retain all incremental backups—only retain those incremental backups that occurred since the most recent baseline or snapshot backup. When you restore the index, you only need to use the partial update files since the baseline backup or snapshot backup of the dgraph_input directory (this is the copy of the directory on which you will restart the MDEX Engine).
Once you do a baseline or snapshot backup, you can delete all backups of partial updates that took place before the baseline or snapshot backups, if you choose to do so.