Data Backup and Recovery Discussions

Activity 'Registering Backup and Applying Retention' failed with error: Value cannot be null.

RickCrutzen

At some servers I get the message: "Activity 'Registering Backup and Applying Retention' failed with error: Value cannot be null." when I try to backup them with SnapCenter.

At other servers it works fine. I don't get this message. The servers use the same Resourcegroup and Policy.

 

Does someone know ho to fix this?

3 REPLIES 3

Re: Activity 'Registering Backup and Applying Retention' failed with error: Value cannot be null.

Ontapforrum

Have a look at these pointers, and also look for any error messages on the storage side, that should give some clue.


Error "Activity 'Registering Backup and Applying Retention' failed. Snapshot has not expired or is locked."
https://mysupport.netapp.com/site/article?lang=en&type=solution&page=%2FAdvice_and_Troubleshooting%2FData_Protection_and_Security%2FSnapCenter%2FSCV_B...

 

Also, have a look here:
Backup operation fails if Snapshot copies on the secondary storage reaches maximum limit:
http://docs.netapp.com/ocsc-41/index.jsp?topic=%2Fcom.netapp.doc.ocsc-dpg-wfs%2FGUID-0B291A9E-FB21-4A8B-903C-CF1352F9455A.html

 

Another thread has this 'null' error mentioned': (Take a look)

https://community.netapp.com/t5/Data-Backup-and-Recovery-Discussions/SnapCenter-4-Exchange-snapvault-integration-NOT-working/m-p/137957#M11777

 

Something to do with Policy/retention/snapshot.

 

Thanks!

Re: Activity 'Registering Backup and Applying Retention' failed with error: Value cannot be null.

mrahul

Please check Customer public report https://mysupport.netapp.com//NOW/cgi-bin/bol?Type=Detail&Display=1267314

 

This issue is fixed in version 4.3.1 

Re: Activity 'Registering Backup and Applying Retention' failed with error: Value cannot be null.

RickCrutzen

Hi,

 

Thanks for the replies guys!

@Ontapforrum : I already saw those posts.

Error "Activity 'Registering Backup and Applying Retention' failed. Snapshot has not expired or is locked."

I think that de retention is ok. At other servers wich use the same Resourcegroup/Policy (and retention) it works fine. 

 

Backup operation fails if Snapshot copies on the secondary storage reaches maximum limit:

I think that's also ok. At other servers wich use the same Resourcegroup/Policy (and retention) it works fine. 

 

@mrahul : That's strange because I already use version 4.3.1

 

Earn Rewards for Your Review!
GPI Review Banner
All Community Forums
Public