Skip to main content
NetApp Knowledge Base

The SnapCenter Purge Job is no longer running on its weekly schedule

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

Applies to

SnapCenter Server 4.x

Issue

Checking the Job History, the Purge Job has not been running for a while, despite the Windows Task Scheduler claiming that the related "SnapCenterJobsRetention" Job ran last Sunday.
 
Since the Purge Job is run from Powershell in the Task Scheduler, the PSSnapIn  logs from %PSModulePath%\SnapCenter\log, should show some error on execution if the Job is not created in SnapCenter. The only error seen in this instance, is in the SmJobPurgeResponse gotten from the SmJobPurgeRequest sent by the Powershell Plug-in to the SnapCenter WebApp Port 8146, which on german Windows looks like this:

<_message>Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.</_message> <_errorCode>-1</_errorCode>

English translation: "Object reference not set to an instance of an object."

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.