Volume Snapshot Policy - bug in acquisition?

stephen2 — Thu, 05 Jun 2025 05:37:16 GMT

Trying to incorporate current snapshot policy into a workflow, but it is null.

All, I am running 2.2.0.2.4RC1 with OCUM 5.2.0.16214 (5.2RC1) against CDOT 8.2.1RC1 and it looks like the WFA is not acquiring snapshot policy.

I can see the policy attached to volumes on the filer:

cdot1::volume> show -fields snapshot-policy

vserver volume snapshot-policy

-------- ------ ---------------

cdot1-01 vol0 -

cdot1a cdot1a_root

default

cdot1a cdot1b_srcvol_vault

none

cdot1b cdot1b_root

default

cdot1b test1 keep-more-snapshot

cdot1b test2 keep-more-snapshot

cdot1b test3 keep-more-snapshot

cdot1b test4 keep-more-snapshot

cdot1b test5 keep-more-snapshot

cdot1b userdata

default

cdot1c cdot1c_root

default

11 entries were displayed.

However, after acquisition, the cm_storage.volume table shows snapshot_policy_id as null - see attached screenshot

I dont know if the problem is with OCUM acquisition from the controllers or WFA acquisition from OCUM (don't know how to query for it in OCUM)

Anyone seen this or have any ideas?

Re: Volume Snapshot Policy - bug in acquisition?

adaikkap — Fri, 25 Apr 2014 22:02:40 GMT

Hi Steve,

OCUM 5.2 doesn't monitor the snapshot policy details. I suggest you use OCUM 6.1 to get the same or use the cDOT custom datasource written by mike goddard for snapshot related data.

Regards

adai

topic Volume Snapshot Policy - bug in acquisition? in Active IQ Unified Manager Discussions

Volume Snapshot Policy - bug in acquisition?

Re: Volume Snapshot Policy - bug in acquisition?