Patch for slow loading of backup monitor after upgrade to 2.4

Patch for slow loading of backup monitor after upgrade to 2.4.0

Customers with a large number of backup history records may notice slower loading of the "Backup Monitor" view after upgrading to 2.4.0

If you are seeing this issue, please update to the latest version of CPM, v2.5.0
Reference defect number – N2WS-4985, fixed in v2.5

    • Related Articles

    • How to upgrade CPM using a patch

      Please note: upgrading using patch does not upgrade Apache/OS General: 1. It is recommended to deploy the patch when you have no active backup policies, DR or recovery running - as it will restart Apache and require few min downtime. 2. When using ...
    • N2WS-13434 - Backup archived to Glacier disappears from the Backup Monitor

      Issue summary Archive backups records might be deleted before their retention period. Issue description A backup record that contains Only archived backup(s), and Does not contain AWS snapshots nor S3 backups or cleanup process deleted all the ...
    • Upgrade instructions for v3.x/4.x

      This guide outlines the steps required to upgrade to N2WS Backup & Recovery version 3.x/4.x We strongly recommend that you follow every step contained within this guide to ensure version 3.x/4.x is configured correctly and no data loss occurs. ...
    • N2WS-22694 - Post upgrade recovery screen running slow

      Issue: UI for recovery screen is working very slowly or getting timed out. Solution: Patch for v4.2.0 is available and attached to this KB. The root cause is the new feature of custom recovery tags. there is a performance issue in case of huge ...
    • Backups may fail with "CPM Server identified this backup as orphaned: marking as failed" after upgrade to v2.3.x

      Backups may fail with "CPM Server identified this backup as orphaned: marking as failed” error after upgrading to 2.3.0X and logs may show the below prints: update_request(agentapi_requests.py:<line_number>) failed calling url ...