HPE Storage Users Group

So it seems in 3.1.3 when you create a RC Group it automatically creates a VV Set with RCP_"name of RC Group". I get the feature, but it clutters the number of vvsets when you have 250+ RC Groups and you can not even delete them. And on the target side it create the same name and append r."3par serial number" to the name. And since vv sets have a low character limit if you have description names the end will get truncated.

I appreciate features, but make them optional or allow me to delete them once created, what a mess this creates when you try to list things out and have to sort through the noise.

Is that being done by the Inserv or the IMC?

My understanding is the Inserv. The 3.1.3 release notes mention it, I just assumed you could delete it, but you can't. Does look like you can rename it. I believe they are headed more to using vv sets and such for management, but they are short sighted and here is why.
They append RCP_ to the beginning and then .r and the last 4 of the serial number, I assume to create uniqueness, problem is the character limit is 31 so if you have more than 21 characters in the name you start to truncate the serial number and if you have more than 25 characters you loos uniqueness and potentially truncate the part that is based on your name.

Taken from the CLI reference guide

NOTES
When a Remote Copy group is created, a VV set will also be created. Its name will be the remote copy group's name prepended with RCP_, with numbers appended if necessary to make the set name unique. Volumes will automatically be added to and removed from this set when volumes are admitted to and dismissed from the group.

hdtvguy wrote:My understanding is the Inserv. The 3.1.3 release notes mention it, I just assumed you could delete it, but you can't. Does look like you can rename it. I believe they are headed more to using vv sets and such for management, but they are short sighted and here is why.
They append RCP_ to the beginning and then .r and the last 4 of the serial number, I assume to create uniqueness, problem is the character limit is 31 so if you have more than 21 characters in the name you start to truncate the serial number and if you have more than 25 characters you loos uniqueness and potentially truncate the part that is based on your name.

The solution to that is easy, fix it so the internal structure is a 64bit GUID and the name is just a display name which can be a say 256 character string. It might take some cleanup in the code, but that's probably a good thing if they have cruft like a 31 character limit. The GUID can start with the serial number of the system that the vvol was created on so that it's guaranteed globally unique.