@apol
apol wrote:
I'm wondering why ssmc appends ".r" to all the secondary vv's names it creates automatically. This makes scripting more complicated imho - can I prevent this from happening?
The current alternative is to use manual creation of the remote volumes. That way, you can completely control the volume names on the remote 3PAR. I'll add an enhancement request to define the volume name on the destination array.
apol wrote:
And the RemoteCopy-part is strange, it makes me select "User CPG" and "Copy CPG" not only for the non-existent secondary vv (which makes perfectly sense), but for the already existing primary vv as well.
Yeah, this is a bit tricky. The CPGs on the source side are used when a switchover/failover occurs and additional volumes are automatically created on that array. Defining the CPGs up front clarifies which CPGs will be used should that happen. I'll ask that the tool tip be enhanced to make this clearer.