Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

Why SCV retention looks like it is not being applied

Views:
86
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-in for VMware vSphere (SCV) 4.3

Answer

SCV applies retention based on the backup time and not the snapshot creation time and guarantees the correct amount of snapshots are kept

 
Example for scheduled backups(*):
  • Retention is 2 days
  • Snapshot created is "05-15-2020_00.25.00.0597"
  • The job workflow log (WFE) shows the backup time is "2020-05-15T00:25:12.258-02:00"
  • Should be removed on 17/05, but  job shows a cut-off time of 05/15/2020 00:25:05 "2020-05-17 00:25:06.453 -02:00 [INF] Retention days 2 (Cut-off date & time: 05/15/2020 00:25:05)"
  • Therefore the snapshot will not be deleted until the following day as the backup time is 7 seconds after the cut-off time

Additional Information

To avoid this, in the policy change the retention from Days to keep to Backup(s) to keep

Note: Retention only runs as part of a backup, and only when the backup is successful. This is done to prevent loss of (all) previous backups when backups fail, but subsequently means that OnDemand Backups (manually run) with "Days to keep" do not run retention when they are not manually triggered daily.