topic Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes in Active IQ Unified Manager Discussions

Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

mauro — Thu, 05 Jun 2025 06:25:01 GMT

netapp-dr:/vol_W_FN_bexec: Failed to create secondary snapshot on netapp-dr:/vol_W_FN_bexec. Reason : Could not get creation time for snapshot 2012-06-14_0941+0200_daily on volume netapp-dr:/vol_W_FN_bexec after 6 retries.

The jobs status is "partially failed". Tha snap was correctly created, but an "error" event was generated by operation manager.

netapp-dr> snap list vol_W_FN_bexec

Volume vol_W_FN_bexec

working...

%/used %/total date name

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

0% ( 0%) 0% ( 0%) Jun 14 09:46 2012-06-14_0941+0200_daily.20120614_094611_CEST (snaplock)

0% ( 0%) 0% ( 0%) Jun 14 09:46 netapp-dr(0135079115)_vol_W_FN_bexec-base.3 (busy,snapvault)

From the dpfm.log:

giu 14 09:46:13 [dfpm:DEBUG]: [2296:0x2e0]: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

giu 14 09:47:14 [dfpm:DEBUG]: [2296:0x2e0]: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

giu 14 09:48:15 [dfpm:DEBUG]: [2296:0x2e0]: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

giu 14 09:49:16 [dfpm:DEBUG]: [2296:0x2e0]: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

giu 14 09:50:17 [dfpm:DEBUG]: [2296:0x2e0]: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

giu 14 09:51:18 [dfpm:DEBUG]: [2296:0x2e0]: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

giu 14 09:52:19 [dfpm:DEBUG]: [2296:0x2e0]: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

It searches for a different name.. It seems a bug...

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

adaikkap — Thu, 14 Jun 2012 09:36:22 GMT

Is this volume dedupe enabled ? Looks like you are running DFM version 5.0 is that right ?

Regards

adai

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

mauro — Thu, 14 Jun 2012 09:46:03 GMT

Yes . Deduped .

5.0

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

adaikkap — Thu, 14 Jun 2012 12:51:51 GMT

This basically means that your controller is overloaded. Pls take a look at the below public report.

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=420257

There is a workaround in the NOTES section, which I am copy pasting.

DFM 4.0D9 provides a workaround for ONTAP burt 354566. When the default of 3

retries and 60 seconds between the retires in the current DFM code is not

enough, use these two hidden options in DFM 4.0D9 to allow users to set the

retries and time period between the retries to allow for getting creation time

of the snapshot.

Set hidden options from DFM command line:

dfm option set dpMaxSnapshotListingRetries=<retries>

dfm option set dpSnapshotListingRetryInterval=<time period between retries>

But there is no guarntee that it will solve the problem. It will only make DFM/Protection Manger wait longer before it timesout with the error you posted.

Regards

adai

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

mauro — Thu, 14 Jun 2012 13:04:11 GMT

I’ve already tried with 6 retries .. but nothing change.

It seems a bug because it searches for a different name:

At 9,46 a snap

0% ( 0%) 0% ( 0%) Jun 14 09:46 2012-06-14_0941+0200_daily.20120614_094611_CEST

Was created

But ,at same time, it searches for a snap that doesn’t exist…

giu 14 09:46:13 Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes: Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes: Snapshot '2012-06-14_0941+0200_daily' not found in volume 'vol_W_FN_bexec'

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

adaikkap — Thu, 14 Jun 2012 13:10:48 GMT

I think the culprit here is snaplock. Protection Manger does not support snapvault of volumes which are snaplock enabled.

Is this happening in other volumes which are dedupe enabled but not snaplocked as well ? Then we will have to dig deeper.

Regards

adai

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

mauro — Thu, 14 Jun 2012 13:15:36 GMT

All volumes are snaplocked in this filer…

This problem happens on all snapvault relationships

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

adaikkap — Thu, 14 Jun 2012 13:22:34 GMT

Snapvault of snap locked enabled volumes are not supported in Protection Manager. You are trying to run a unsupported configuration.

Regards

adai

Re: Failed to create secondary snapshot , Reason : Could not get creation time on snaplock volumes

adaikkap — Thu, 14 Jun 2012 13:31:21 GMT

BTW I strongly recommend you to use OC 5.0.1 as it a GA candidate of OC 5.0

Regards

adai

Note: Though this does not solve your problem of snaplock being unsupported. Also my initial hunch of filer overloaded is not the cause here as its more a snaplock and dedupe combination than load.

Regards

adai