I had a little trouble setting this all up too. I assume you are going to utilize the Nimble replication and that is working. In SRM you are using array based replication and not VMware replication. I hate to say read the manual, but what helped me was relying heavily on chapter 2 of the SRM Admin guide. I think, if I understand your issue, the array based replication needs to be configured or refreshed to discover the replicated Nimble Volume Collections or protected single volumes.
In the vSphere web client, under SRM, from the Array Based Replication section, have you discovered the array pairs? Then pick one of the storage arrays and run the discover devices operation. This should get you past the error you are currently seeing.
Thanks Dan, appreciate the response.
Currently the arrays are paired and also did run the discovery for array and device operations.
Showing below is a screenshot of the error message.
What is interesting, and not sure if this is the way it is suppose to work, but local array shows NimbleVA01 and the local device shows SRMVC01 but on that particular array the I have another volume which is local. the SRMVC01 is the replicated volume from other pairs Nimble array. This could be part of reason why showing unknown.
Yeah, I saw this too when I had first setup the Nimble Volume Collection
but it had not replicated anything to the remote site. If you force a
replication or change your schedule to replicate right away and then you
should be good.
Dan Bauder, VCP 3, 4, 5, DCV
UNC Charlotte, Information & Technology Services
9201 University City Blvd., Charlotte, NC 28223
I had the same issue as you yesterday. I was in the last stage of upgrading a customers vSphere / SRM environment and hit this little beauty.
After laborious trouble shooting with an engineer it was the fact that the SRM Volumes which had been created for SRM 5 had not been given initiator group authentication.
In SRM 5 they worked fine but after the upgrade to 6 + it wont accept it. I added initiator groups and had to removed the unrestricted access, after a rescan of the Array Devices on the SRM side they showed again.
Hope this helps.
Thank you for the response.
I had opened a case but been offsite with customers since then and just totally forgot to update the case but your are spot on with your response.
I did not assign the initiator groups and was set to unrestricted access which was causing our issue.
Appreciate the help.