System Manager workflow is incorrect

[pascaldewild]

Page URL

https://docs.netapp.com/us-en/ontap/snaplock/commit-snapshot-copies-worm-concept.html

Page title

Commit snapshots to WORM on a vault destination

Summary

Hi team, the flow in 'System Manager' and 'CLI' do not correspond in this article. The System Manager flow lacks the 'Protect a volume' option. The option described (which is called "Lock the destination snapshots" by the way) is only available in the 'Protect' GUI option. So when creating a SnapMirror relationship. Not when creating a volume?

It furthermore lacks the instruction on which cluster (source or destination) this should be done.

Please revisit this page, because it's wrong. See attach for the option at the end of a SnapMirror Creation wizard. The option 'Lock the destination snapshots' is available both when using a 'vault' type and a 'mirror-vault' type relationship. The choice which locking mechanism is only available when using a 'vault' relationship though.

Public issues must not contain sensitive information

• This issue contains no sensitive information.