Patch for slow loading of backup monitor after upgrade to 2.4.0

• Related Articles

• How to upgrade CPM using a patch

  Please note: upgrading using patch does not upgrade Apache 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 Backup record with archived/Glacier backup may be deleted prematurely by the clean-up operation, once it cleans all the snapshot and S3 backups ...

• How to upgrade to the latest CPM version using the patch method

  How to upgrade CPM using a patch This KB article details the steps needed to upgrade the N2WS CPM server instance to the latest version using the patch method. Prerequisites: Make sure you have no active backup policies running or DR ( including ...

• 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. ...

• 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 ...