N2WS-23418 - Incorrect display of scheduled exclude time

N2WS-23418 - Incorrect display of scheduled exclude time

Issue:
Schedule UI is might show incorrect exclude time
In addition, the the enabled/disabled toggle will show off even when enabled,



Solution:
  1. v4.2.2 - install attached patch: 
    https://n2ws.com/wp-content/uploads/2024/03/4.2.2_N2WS-23418_incorrect_display_of_sched_exclude_time.patch
    NOTE: This is UI patch that might take 10-15 min to complete, during which UI might no be available 

    • Related Articles

    • N2WS-19081 - Resource Control Group schedules might change unintentionally

      Issue: Resource Control Group schedules might change unintentionally When opening RCG in the UI, it shows incorrect schedule times, then when clicking save it changes the time of the Resource Control Group. In addition, schedules for RCG might also ...
    • N2WS-23140 - incorrect dr cleanup message

      Issue: during DR cleanup, there is an incorrect error message saying there might be issues because all backups succeeded. Cleanup did not mark any AWS dr backup for deletion for AWS policy testing. Only 7 of 7 dr backups completed successfully. ...
    • N2WS-18084 - Volumes may be excluded from backup unexpectedly

      Issue: When configuring a backup to exclude a volume for an instance, after policy run configuration might change to exclude all volumes. Solution: Patch for v3.2.1 Available and attached to this KB Click here to go back to the Release notes: Release ...
    • N2WS-19901 - UI Agents screen times out

      Issue: When there are lots of VSS agents and trying to open the Agent tab in the UI, it get timed out and does not load Solution: Patch for v4.0.0c Available and attached to this KB Click here to go back to the Release notes: Release notes for the ...
    • Backups/DR/tag scans may start to fail because of clock issues or connectivity issues.

      Problem descriptions: If you start seeing failures in the logs of AWS API calls saying that "AWS was not able to validate the provided access credentials", this is likely caused by either lack of connectivity with AWS endpoints or time ...