Hi there
I've run into a problem and can't figure a solution at all. I'm running SRM 5.8 trial edition for Uni Project work along with HP StoreVirtual VSA creating a Virtual SAN. I'm using SRA 10.5.0.92 which seems to be the correct version required for SRM 5.8 and while SRM is detecting my Replications in vCenter Web Management, it is not recognising a datastore, thus when I come to create a protection group I am presented with the error message:
I definitely have an ESX datastore which is being replicated and the datastore has virtual machines on it.
I've been literally banging my head against a wall for the past 2 weeks-ish trying to figure out what's going wrong.
The SRM logs seemingly indicate that all my storage devices are being skipped under detection as they are "neither iSCSI or FC"
| SRM 5.8 Logs |
|---|
2015-02-17T23:28:07.255Z [02732 verbose 'DatastoreGroupManager' opID=4b543b6f] Skipping extent 't10.ATA_____VB0250EAVER_____________________________Z2ADTEJB____________:3' of VMFS volume '4f050297-02b9807a-2cbb-2c768aadf716:datastore' which is neither FC nor iSCSI 2015-02-17T23:28:07.255Z [02732 verbose 'DatastoreGroupManager' opID=4b543b6f] Skipping extent 't10.ATA_____VB0250EAVER_____________________________Z3T0L3NN____________:3' of VMFS volume '50ad5dea-704efe81-169d-a0b3ccdf2aaf:datastore1' which is neither FC nor iSCSI 2015-02-17T23:28:07.255Z [02732 verbose 'DatastoreGroupManager' opID=4b543b6f] Skipping extent 't10.ATA_____WDC_WD1002FAEX2D00Z3A0________________________WD2DWCATRC128181:1' of VMFS volume '5473e723-b6dc8dbb-4e55-e83935f08fef:PR SAN' which is neither FC nor iSCSI 2015-02-17T23:28:07.255Z [02732 verbose 'DatastoreGroupManager' opID=4b543b6f] Skipping extent 'naa.6000eb354b962645000000000000001d:1' of VMFS volume '54d40a68-8b085f00-ec16-001f2958247c:Server Volume (iSCSI)' which is neither FC nor iSCSI |
The first 3 are correct as they are standard SATA disks but the final entry is my iSCSI target from the HP LeftHand.
Ignoring the last entry which was a test target and currently inactive, the Server Volume (iSCSI) is volume being presented from HP LeftHand, and all the vHosts in the primary group have access to it. vCenter confirms this as it can read the datastore.
I've no idea what else to try and was wondering if anyone has experienced this problem.