Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
A Partner is currently setting up WFA and Unified Manager to extend protection relationships Primary -> SnapVault -> SnapMirror. It all works fine with “Extend protection > From secondary” but the name of the destination volume has a suffix of “_001”. However, the customer would like to remove that suffix and select the volume name themselves. Is it possible ?
The OCUM and WFA integration is tightly copuled one. You cannot change the behaviour AFAIK.
The integrated workflow uses incremental naming convention. So unless you change the workflow to make it as user input you cannot achieve what you are looking for.
So best way forward is copy/clone the workflow and change the incremental naming to user input. Once you do that you can associate the same from UM as its tight integration based on UUID of the wokflows.
So your cloned workflow would have a new UUID and cant be launched from the current version of OCUM's.
The suffix is indeed generated by OCUM and passed on to the WFA workflow.
From the OCUM online help of the SnapVault protection dialogue:
A suffix between 001 and 999 is appended to the secondary name when the relationship is created, replacing the nnn that displays in the preview text, with 001 being assigned first, 002 assigned second, and so on.
The idea is to circumvent duplicate names that would cause the workflow to fail as mostly the name is dynamically created based on other variables that can be identicale for different relationships.
The intention is correct, but I can understand that people may not like that behavior.
Unfortunataly there is no build-in way to remove it.