N2WS-17075 - logs can be unexpectedly truncated

N2WS-17075 - logs can be unexpectedly truncated

Issue:

CPM logs of Server, API and DR might get unexpectedly truncated, resulting in smaller logs that might make it harder to analyze potential issues.

Solution:
Patch for v3.2.1 Available and attached to this KB


Click here to go back to the Release notes: Release notes for the latest v3.2.x CPM release

    • Related Articles

    • Cleanup Log

      This feature was added to allow CPM users to better understand whether Cleanup process ran successfully. It can be found in the “General Settings” tab. The Cleanup Interval may be set to run every 1 to 24 hours. Last cleanup timestamp will show the ...
    • 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 backups, Cleanup, restores, S3 copy ...
    • MustGather information 3.0: how to collect relevant details for support.

      When opening a support ticket, please provide the following information: Server Logs 1. Always no matter what the issue is, please provide the full CPM Server logs using the link at the top right of the screen:      UI or Download logs not working? ...
    • Does CPM Support rolling forward SQL logs after restore?

      CPM doesn't support rolling forward SQL logs, since CPM performs "full backup", not "logs backup". We recommend to use the simple recovery model with CPM backups.
    • Patch for cost reduction of copy to S3

      Installation of the patch will reduce costs drastically for customers who are using S3 (Between 5 to 20 times less expensive than previous version) The improvements are: For copied volumes which are larger than 512GB, worker’s volume type will be sc1 ...