Partner detected volume name conflict

[RLemmens]

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,. 

[Nick_Dyer]

Hi!

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

[RLemmens]

How can I fix this?

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

[Nick_Dyer]

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.

[RLemmens]

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