Hi Cjone147.

Right now, for good reason the VG names are always dynamic to avoid mistakenly tripping over an existing CG, failing a mount for risidual CG information, etc - I will ask if its possible though.

Thanks - James.

Hi there
The reply is that right now, you cannot change the way RM works in assigning different VG names each time...but you can run a simple callout script (see admin guide) after the VG is imported, to determine the new VG name and then mount the FS with that new VGname.

James.

Our folks at engineering would like to know why you need to keep the name persistent / specific so they can ascertain if there is anything they can do as an enhancement to the product.

If you can describe for me what exactly you are doing and why you need the VGname to stay the same / be specific, I will feed this back to them.

Thanks - James

Thank you for your response and assistance. We are using a 3rd party security tool that searches the volume groups and identifies potential hacker activity. In order to do this, we have to specify the name of the VG to search and we can't because the name changes. Hope this makes sense...

It makes sense, it does so, its kind of storage DOS checking, if someone ripped out a VG..ok...

Well, this would be considered a product enhancement via Powerlink
Support --> Request Support --> Request Product Enhancement.

I think best to explain the technical reasoning behind this and of course, your company and contacts so you will recieve an update to your enhancement request later on.

Thanks - James.