Troubleshooting a Failed Restore

Edit online

About this task

When a restore fails, you can analyze and understand the reason for failure from the error message that appears after the operation. If the error message instructs you to use the perform_open_indices command, follow the steps given in this section.

When you perform a restore operation, the indices in the API Data Store are closed to avoid any overwriting of data. After the restore process is over, the indices are opened so that the application starts using the Data Store. However, if a restore operation fails, you must open the indices for the regular operations to continue. For example, if a restore operation fails due to insufficient memory, then the error message that appears instructs you to perform open indices.

If the error message does not display enough details, you can check the logs for further details. You can check the logs saved during the process in the SAGInstallDir\InternalDataStore\logs folder.

To open indices

Procedure

  1. From the command prompt, go to SAGInstallDir/IntegrationServer/instances/instance_name/packages/WmAPIGateway/cli/bin.
  2. Run the following command to delete a backup file:
    Linux 
    ./apigatewayUtil.sh perform open_indices
    Windows 
    apigatewayUtil.bat perform open_indices
    You can specify the log file location and log level for the above operation using these parameters:
    Parameter Description
    logLevel Allows you to specify the required level of log that you want to create. Log levels indicate the severity of logs. Available levels are:
    • Info. Provides the list of regular events that occur during the process. These events are informative.
    • Debug. Provides the events that could be useful, if you have to debug the process.
    • Warning. Indicates unexpected events that occurred during the process. Usually, these events do not interrupt or have an immediate effect on the process.
    • Error. Indicates the events that stop the functionality from working as designed.
    • Trace. Provides a much detailed events that could be useful for debugging.
    You can specify one of the log level with the logLevel parameter. For example, to create a log file of Warning level when listing backup files, you can run the following command: 
    apigatewayUtil.bat list backup -logLevel warning
    When you provide Error as the log level, then only the error level logs are saved. When you provide Debug as the log level, then Debug, Info, Warning and Error level logs are saved. When you provide Trace as log level, then all level logs are saved.

    This parameter is optional. If you do not specify the parameter, then the Info level logs are saved by default.

    logFileLocation Allows you to provide the location where you want to save the log file.
    For example, to save the log file in C:/apiglogs/backups, you can provide the location as seen in the following example: 
    apigatewayUtil.bat create backup -name samplebackup 
-logFileLocation C:/apiglogs/backups
    This parameter is optional. If you do not specify the parameter, the logs are saved in the following location SAGInstallDir/IntegrationServer/instances/instance_name/packages/WmAPIGateway/cli/logs/APIGWUtility.log.