When I was configuring SRM SRA then I was getting following error when array where rescanned
Someone suggested that
For ESX host 3.5 you would be enabling “LVM.EnableReSignature ” under advance option for esx host. ESX4 performs this function automatically whereas in version 3.5 you had to enable it in the advanced settings section of the host configuration.
This did not fixed my problem yet and then I followed KB 1016862 and its resolution says
“Virtual machine components can be on an array which is replicated to another array.
However, VMware does not support virtual machine components on multiple arrays which replicate to a single array as the VMX configurations do not match in terms of UUID of the datastores.
Ensure that virtual machine components are not on multiple arrays that replicate to a single array.”
Well in our case it was different. Then I start looking at config again. I found that VM’s were mounted using different export IP then what I have added under array manger.
What I meant is NFS IP were different for ESX host and Array manager. I changed the IP and now I was able to see the datastore.
Posts
1 comment:
Just to add the below requirements for NetApp NFS mounts;
1. The hostname referenced in snapmirror.conf must match the actual hostname. If it does not (as in our case where the hostname is uppercase and in snapmirror.conf its lowercase), then SRA will have a problem discovering the array device.
2. Ensure that snapmirror relationships are not in a transferring state. If there are, transfers need to complete to confirm that SRA is able to pair the devices
3. Remove unneeded export statements for RO snapmirror destinations. Having these export statements may cause issues when attempting a Recovery operation in that the destination hosts may not be able to mount the volume due to the existing export statements. It's best to remove these and to allow SRA to create them during the Recovery operation.
Post a Comment