Known Issues

Learn about the known issues in each IBM® QRadar® Data Synchronization app release.

Version 2.1.0 or later

In certain scenarios, the Log Source status is not considered, and events are pulled from both sites simultaneously. This issue affects only ‘pull-type’ log sources. As a workaround, manually disable the affected log sources on the host that is in STANDBY mode. For more information, see Known Issue.

Version 3.0.0 or later

Known issue 1
With IBM QRadar 7.5.0 Update Package 1 or Update Package 2, the failback process can continue running without completing in deployments with paired IBM QRadar Network Insights hosts. For a workaround, contact Customer Support.
Known issue 2
Users might encounter a security token error message when opening the Data Synchronization app v3.0.0 for the first time after logging in. After logging in to QRadar, the app displays the message: There was an error validating the security token. Please click close to reload the app. As a workaround, click Close, and the app will reload successfully.
Note: For more information, see Known Issue IJ38806.

Version 3.1.1 or later

Sometimes, the QRadar Data Synchronization app might display failures in the Host Summary status window due to a time calculation issue. The Timestamp field shows the current time, but the Data Content field references the wrong hour of data, resulting in a Failure status for each entry. However, the actual data synchronization continues to function normally despite these errors.
Note: For more information, see Known Issues.

Version 3.2.1 or later

Known issue 1
The system is running IBM QRadar 7.5.0 Update Package 11 with the Data Synchronization app v3.2.1 that is installed. Upgrading QRadar to 7.5.0 Update Package 13 while keeping the same app version causes the Data Synchronization app to stop working. As a workaround before initiating failover (DR site activation), upgrade the app to v3.2.2 on both sites (Main and Destination) to ensure continued functionality.
Note: For more information, see Known Issues.
Known issue 2
In a console-only setup, failover works as expected. However, when a user attempts to perform a failback, the process does not complete successfully. The main site restoration completes successfully, but the destination site restoration may encounter technical issues. Upgrade the Data Synchronization App to version 3.2.2 before performing failover (destination site activation).
Note: For more information, see Known Issues.

Version 3.2.2 or later

In some cases, during the failback process, the Ariel data copy may enter an infinite loop and fail to complete. Consequently, Ariel data may not be fully transferred from the destination site to the main site. As a workaround, contact Customer Support.
Note: For more information, see Known Issues.

Version 3.3.0 or later

Known issue 1
In a hybrid DR setup, stale references to deleted Managed Hosts or Managed Host HA configurations might remain on the destination site during the pairing configuration process. The issue can occur when a host mismatch is not detected and the required delete or add operation is not triggered. During failover or failback, these stale references can cause the restore operation to fail. Contact Customer Support before you initiate the failover or failback process.
Note: For more information, see Known Issues.
Known issue 2
In a hybrid DR setup that runs IBM QRadar 7.5.0 Update Package 14, after a failover and subsequent failback, the first deployment attempt might time out for the paired managed hosts. In this case, the user must deploy the changes a second time after which the deployment completes successfully.
Note: For more information, see Known Issues.
Known issue 3
In a hybrid DR setup that runs IBM QRadar 7.5.0 Update Package 14, during repeated failover and failback cycles, duplicate entries for rehomed managed hosts might remain in the host token files. As a result, deployment attempts for the rehomed managed hosts might time out. Contact Customer Support before you initiate the failover or failback process.
Note: For more information, see Known Issues.
Known issue 4
During a hybrid configuration setup, if the Data Synchronization app is configured simultaneously on both the main site and the destination site, the hybrid flow setting might not be enabled correctly on the destination site. In this scenario, failover is not allowed. Perform a factory reset on both sites, then configure the main site first, followed by the destination site.
Note: For more information, see Known Issues.
Known issue 5
In a hybrid configuration setup, during the pairing configuration process, attempts to add or delete a managed host might fail after three retries. When the issue occurs, the pairing configuration process cannot complete successfully. Contact IBM Support to manually add or delete the managed host.
Note: For more information, see Known Issues.
Known issue 6
In hybrid setups that runs IBM QRadar 7.5.0 Update Package 14 or 15, the configuration file (dr.conf) might not be restored correctly during activation or failback due to permission changes. This issue can cause the restore process to fail. Contact IBM Support for further assistance.
Note: For more information, see Known Issues.

All versions

Known issue 1
On patched QRadar deployments, the time zone of a managed host's PostgreSQL database can be incorrectly set, which might result in the QRadar Data Synchronization app synchronizing Ariel data with an incorrect time period. Updating to QRadar 7.5.0 Update Package 2 resolves this issue.
Known issue 2
Users may experience an issue during activation if the activation call takes more than 60 seconds. In such cases, the request can exceed the NGINX default connection timeout value, causing the activation to fail and displaying the following error: JSON.parse: unexpected character at line 1 column 1 of the JSON data. As a workaround, contact Customer Support.
Note: For more information, see Known Issues.
Known issue 3
In an environment that runs IBM QRadar 7.5.0 Update Package 14, with the Data Synchronization app that is configured for 1:1 pairing, restoring a backup on the destination site might fail. Contact Customer Support before you initiate the restore operation.
Note: For more information, see Known Issues.