topic Partner detected volume name conflict in Array Performance and Data Protection

Partner detected volume name conflict

RLemmens — Mon, 28 Oct 2019 09:37:19 GMT

Last week I created a new volume on one of our two Nimbles. After creation of the volume I saw that I had chosen the wrong performance policy. I then deleted the volume and recreated it again with the correct performance policy.

I now have a problem, that I got the error "Partner detected volume name conflict". The other Nimble had already made a volume with the same name, but I forgot to delete this volume,.

Re: Partner detected volume name conflict

Nick_Dyer — Wed, 30 Oct 2019 14:02:49 GMT

Hi!

This is because the downstream array still has a volume replica which has become orphaned.

Re: Partner detected volume name conflict

RLemmens — Thu, 31 Oct 2019 09:23:35 GMT

How can I fix this?

Is there a possibility to point the orphaned volume to the newly created volume?

Re: Partner detected volume name conflict

Nick_Dyer — Thu, 31 Oct 2019 09:34:29 GMT

Should just be a case of logging in to the downstream array and deleting the orphaned replica.

If you get stuck, feel free to give Nimble Support a call.

Re: Partner detected volume name conflict

RLemmens — Mon, 11 Nov 2019 06:59:42 GMT

I had to claim the disk first, I dindn't know what would happen if I selected the claim disk option.