Skip to main content
NetApp Knowledge Base

SCE 4.5 and 4.6 UTM retention fails after backup marked as Point In Time

Views:
868
Visibility:
Public
Votes:
1
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter Server (SC) 4.5 and 4.6
  • SnapCenter Plug-in for Microsoft Exchange Server (SCE) 4.5 and 4.6
  • Up to the minute (UTM) retention

Issue

  • When using SCE, if UTM retention is triggered during a backup job, log snapshot copies (suffix_1) are not getting deleted from ONTAP and NSM database. This issue occurs if the UTM retention is based on days
  • The backup is marked as point in time (PIT) but the Full backup log snapshots (suffix _1) that are outside of desired retention are not deleted
  • The user database volume and SCEBackupInfo folder retention is successful
  • There are no errors shown in the logs but there are entries showing the backup being marked as PIT and the log backup snapshot (no _1 suffix) being deleted:
    <installation_path>\NetApp\SnapCenter\App_Data\log\SnapManagerWeb_<id>.log:

INFO  SnapManagerWeb_225137 PID=[7744] TID=[112] GetUtmLogBackupByDays - Log backup snapshot name is: <snapshot_name_1>, created date is: 11/8/2021 9:01:36 PM, 
start date is: 11/8/2021 9:01:36 PM, excluded is: True,  is log folder marked for deletion: True.
DEBUG SnapManagerWeb_225137 PID=[7744] TID=[112] Mark '<snapshot_name_1>' PIT

  • The database snapshot (without the _1 suffix) from the full backup is successfully removed
    <installation_path>\Program Files\NetApp\SnapCenter\SMCore\SnapDriveSALDebug.log:

Verbose SAL PID=[3376] TID=[7080] Command starts: Remove-NcSnapshot -Volume <vol_name> -Snapshot <snapshot_name>
Verbose SAL PID=[3376] TID=[7080] Command completes: Remove-NcSnapshot -Volume <vol_name> -Snapshot <snapshot_name>

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.