BlueXP Capacity Management mode should set to Manual when using WORM

[pablogarciaarevalo]

Page URL

https://docs.netapp.com/us-en/bluexp-cloud-volumes-ontap/concept-worm.html

Page title

WORM storage

Summary

BlueXP Automatic mode might not work properly with the WORM feature due to the inability to move volumes between data aggregates automatically. BlueXP Capacity Management mode should set to Manual.

https://docs.netapp.com/us-en/ontap/snaplock/move-snaplock-volume-concept.html

Public issues must not contain sensitive information

• [X] This issue contains no sensitive information.

[netapp-rlithman]

Hi Pablo. Thank you for sharing your feedback. The team will review your request and follow up.

[netapp-driley]

Hi @pablogarciaarevalo - Following up on this item, do you know what version of Cloud Volumes ONTAP you were running when capacity management required manual mode for the WORM feature?

[pablogarciaarevalo]

Hello @netapp-driley , I think it's regardless the CVO version. Using the BlueXP automatic management feature, one volume could be moved from one aggregate to another aggregate due to some capacity constrains. And the volume movement of a WORM volume doesn't work without enabling the snaplock role to an user https://docs.netapp.com/us-en/ontap/snaplock/move-snaplock-volume-concept.html#create-a-snaplock-security-administrator-account

[netapp-driley]

Hi @pablogarciaarevalo - Initially, we were thinking this issue might be related to the version of CVO you're running. I'll take this information back to the CVO team to determine next steps. I'll keep you posted on what we find out.

Thanks,

Don

[netapp-driley]

Following up on this item, the CVO team was able to confirm "cluster admin user that is used in BlueXP does in fact have the required role for moving a SnapLock volume so capacity management should work in automatic mode."

Please feel free to submit a new issue if you feel the cluster admin user still does work with automatic mode.