Cleanup secondary backups does not automatically trigger with SnapCenter 6.0.1
Applies to
- SnapCenter Server (SC) 6.0.1
- Cleanup secondary backup job
Issue
- Cleanup secondary backups does not automatically trigger with SC 6.0.1.
- Job actually runs successfully but does not show in Monitor UI:
[2024-12-15 03:59:00:021 DBG] Calling Execute on job Tk9ORS1QUkVERUZJTkVE.Tk9ORS1QcmVkZWZpbmVkLTItNQ==
[2024-12-15 03:59:00:021 DBG] Enter QuartzJob.Execute
[2024-12-15 03:59:00:022 DBG] 12/15/2024 3:59:00 AM
[2024-12-15 03:59:00:022 DBG] ResourceManagerStringLocalizer searched for 'ScheduleName' in 'NetApp.DataProtection.Scheduler.Resources.SharedResource' with culture 'en-US'.
[2024-12-15 03:59:00:022 DBG] Schedule Name: 19
[2024-12-15 03:59:00:022 DBG] Enter ScheduledJobHandler.ExecuteJob
[2024-12-15 03:59:00:023 DBG] Batch acquisition of 0 triggers
[2024-12-15 03:59:00:035 INF] JobType: Predefined, PluginCode: NONE, PolicyId: 5, ProtectionGroupId: 2, ReportScheduleId:
[2024-12-15 03:59:00:035 DBG] Metadata Key: Plugin Value: 100
[2024-12-15 03:59:00:035 DBG] Metadata Key: JobType Value: "Predefined"
[2024-12-15 03:59:00:035 DBG] Metadata Key: ProtectionGroupId Value: 2
[2024-12-15 03:59:00:035 DBG] Metadata Key: PolicyId Value: 5
[2024-12-15 03:59:00:035 DBG] Metadata Key: PolicyName Value: "SnapCenter_RemoveSecondaryBackup"
[2024-12-15 03:59:00:035 DBG] Metadata Key: ProtectionGroupName Value: "SnapCenter_RemoveSecondaryBackup"
2024-12-15T03:59:01.0711351+00:00 INFO SnapManagerWeb PID=[6500] TID=[65] Before calling biz for schedule : SnapCenter_RemoveSecondaryBackup
2024-12-15T03:59:01.1018601+00:00 INFO SnapManagerWeb PID=[6500] TID=[65] Operation DeleteBackup started at 12/15/2024 03:59:0
2024-12-15T03:59:01.1466112+00:00 INFO SnapManagerWeb PID=[6500] TID=[65] Operation DeleteBackup ended at 12/15/2024 03:59:01
- SnapCenter_RemoveSecondaryBackup
Remove-SmBackup -CleanupSecondaryBackups
cannot be changed via PowerShell although the command runs.