vCenter Host Profile Core Storage PSP Configuration - Nimble Storage
| 3 minutes
I’m working on rolling out vCenter Host Profiles at work, to keep an eye on our configuration and also to assist in the deployment of new ESXi servers into our environment. If you haven’t checked out host profiles and you have a VMWare Enterprise Plus license, it is a must!
I’m working through a few of our clusters that are connected to our Nimble Storage arrays using the iSCSI Software Initiator, and that use the Nimble Path Selection Policy (PSP) to determine the best path policies from the ESXi host to the storage.
VMWare SRM Duplicate initiator 'iqn.1998-01.com.vmware:Server1-280206e1' found in SRA's 'discoverDevices' response.
| 2 minutes
When setting up VMWare SRM 6.1 with array based replication, I was seeing an error after adding the array managers into SRM. The error was Duplicate initiator ‘iqn.1998-01.com.vmware:Server1-280206e1’ found in SRA’s ‘discoverDevices’ response.
In the vmware-dr-xxx.log file found in C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs there was a tiny bit more info:
2016-01-13T09:39:10.757+11:00 [03508 info 'DrTask' opID=5cacf7dd] Task 'dr.storage.ReplicatedArrayPair.discoverDevices112' failed with error: (dr.storage.fault.DuplicateInitiator) { --> faultCause = (vmodl.MethodFault) null, --> command = "discoverDevices", --> responseXml = "<Initiator id="iqn.
VMWare SRM Array Based Replication Volume Mounted as 'snap-xxxxxxx-VolumeName' After Failover
| 2 minutes
I’m going through the process of installing VMWare Site Recovery Manager (SRM) 6.1 in our production environment, which is currently running vSphere 6.0U1.
We use Nimble Storage arrays and have elected to make use of array based replication (ABR) for data replication between sites.
During our initial testing and doing full failovers of some dev applications, I noticed that the datastore name within vCenter for the protected volume on the SAN was getting renamed, and had a prefix of snap-5b356a02-VolumeName