[Not actual answer, as i am interested in finding the correct answer]
i had similar problem. And I have worked around it by (if i can recall correctly) un-tagged the device, added to storage group and re-tagged it.
Its clearly won't have any side affect if a consistency group, replication sets, production copies and replication copies all are new - as replication won't start until the replication has been enabled. Not sure in other cases regarding side affects.
Not too sure about SymmCmds as i used to use provider to manage VMAX (so familiar with provider programming API). Give it a try with ESI 3.5 Recover point PowerShell Cmdlets (https://support.emc.com/search/?text=ESI%203.5). They may have what you are looking for.
Dream93
1 Rookie
•
72 Posts
592
0
Posted October 22nd, 2014 18:00
[Not actual answer, as i am interested in finding the correct answer]
i had similar problem. And I have worked around it by (if i can recall correctly) un-tagged the device, added to storage group and re-tagged it.
Its clearly won't have any side affect if a consistency group, replication sets, production copies and replication copies all are new - as replication won't start until the replication has been enabled. Not sure in other cases regarding side affects.
Regards.