N2WS-22694 - Post upgrade recovery screen running slow

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 policies with many resources and tags. 
This patch offers the option to disable this feature. When the feature is disabled, the performance problem would be resolved and tags behavior during recovery will revert to the way it was in previous versions, either no tags or preserve original tags.

To disable it you need to install the attached patch and add an option in the cpmserver config file.

Steps:
1. Install patch attached to this KB
2. SSH into the N2WS server, user is cpmuser and your ssh key
      Note: If SSH fails with "Server refused our key", see this KB: SSH to the CPM instance fails after upgrade to CPM 4.2.x with "Server refused our key
3. create or modify this file /cpmdata/conf/cpmserver.cfg
and add the following

[recovery]
skip_recovery_tags=True
 
4. When no backups are running, restart the EC2 or restart Apache with command: sudo systemctl restart apache2

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

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

    • 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-23233 - Recovery from DR region might fail or select wrong snapshot

      Issue: During recovery from DR region, wrong snapshot might be selected which can lead to recovery failing or recovering incorrect data. Solution: v4.2.0 & v4.2.1 - upgrade to 4.2.2 and install patch v4.2.2 - install attached patch

    • N2WS-22712 - Unable to select S3 source for recovery when N2WS is in recovery mode

      Issue: When N2WS Server is in recovery mode, User can't select S3 as the source for the recovery Solution: v4.2.0 - upgrade to 4.2.2 and install patch 4.2.1 & v4.2.2 - install attached patch