4 Replies Latest reply: Jun 18, 2012 5:04 PM by warkem01 RSS

    Srm 5, IBM V7000 6.3 and SRA IBMSVCSRA_v2.0.0.120417

    warkem01 Novice

      So now finally with the release (still not official) of the latest SRA from IBM SRM can now see the replicated storage on the V7000s however the SRA do not appear to be able to control the storage for some reason. Everytime I try to test a Recovery plan I get the below failed to create snapshots of replica devices errors.

       

      Just wondering if anyone has seen these errors or even had any success with SRM 5 and V7000/SVC 6.3?

       

       

       

      4. Create Writeable Storage  SnapshotError - Failed to create snapshots  of replica devices. Failed to create snapshot of replica consistency group  SRM_NLSAS. Expected consistency group 'SRM_NLSAS' not found in SRA's  'testFailoverStart' response.

       

      2012-05-14T10:30:47.625+10:00 [01836 trivia 'Recovery' ctxID=460757c opID=044E4BDA-00000034] Running job failoverMain <recovery-plan-14746> [class Dr::Recovery::Engine::FailoverMainJob]

      2012-05-14T10:30:47.625+10:00 [01836 error 'Recovery' ctxID=460757c opID=044E4BDA-00000034] [failoverMain] Execution failed: (dr.storageProvider.fault.StorageTestFailoverStartFailed) {

      -->    dynamicType = <unset>,

      -->    faultCause = (dr.storageProvider.fault.StorageDeviceGroupTestFailoverStartFailed) {

      -->       dynamicType = <unset>,

      -->       faultCause = (dr.storage.fault.DeviceGroupNotFound) {

      -->          dynamicType = <unset>,

      -->          faultCause = (vmodl.MethodFault) null,

      -->          command = "testFailoverStart",

      -->          responseXml = "",

      -->          id = "SRM_NLSAS",

      -->          msg = "",

      -->       },

      -->       deviceGroup = "SRM_NLSAS",

      -->       msg = "",

      -->    },

      -->    msg = "",

      --> }

       

      2012-05-14T10:30:57.329+10:00 [01200 verbose 'PlaceholderVmManager' opID=044E4BDA-0000006D] [PlaceholderVm] Reloading placeholder VM '[vim.VirtualMachine:vm-341]' from path '[DRSRMPlaceholders] rm-db-prod/rm-db-prod.vmx'
      2012-05-14T10:30:57.344+10:00 [01576 verbose 'HostDomain' opID=044E4BDA-0000006D] [vim.HostSystem:host-19] is now connected
      2012-05-14T10:30:57.344+10:00 [01576 verbose 'HostDomain' opID=044E4BDA-0000006D] [vim.HostSystem:host-19] is no longer in maintenance mode.
      2012-05-14T10:30:57.344+10:00 [01576 verbose 'HostDomain' opID=044E4BDA-0000006D] [vim.HostSystem:host-19] is now poweredOn
      2012-05-14T10:30:57.344+10:00 [01576 verbose 'HostDomain' opID=044E4BDA-0000006D] [vim.HostSystem:host-9] is now connected
      2012-05-14T10:30:57.344+10:00 [01576 verbose 'HostDomain' opID=044E4BDA-0000006D] [vim.HostSystem:host-9] is no longer in maintenance mode.
      2012-05-14T10:30:57.344+10:00 [01576 verbose 'HostDomain' opID=044E4BDA-0000006D] [vim.HostSystem:host-9] is now poweredOn
      2012-05-14T10:30:57.360+10:00 [01576 verbose 'LocalVC'] [PCM] Using token '28' for pending filter creation
      2012-05-14T10:30:57.563+10:00 [01052 error 'RemoteTaskMonitor'] Dr::Internal::RemoteTaskBase::HandleTaskError: The task MoId=task-6565 failed, error=
      --> (vim.fault.AlreadyExists) {
      -->    dynamicType = <unset>,
      -->    faultCause = (vmodl.MethodFault) null,
      -->    name = "rm-db-prod",
      -->    msg = "The specified key, name, or identifier already exists.",
      --> }
      2012-05-14T10:30:57.563+10:00 [01052 error 'RemoteTaskMonitor'] Dr::Internal::RemoteTask<void>::Fail: The task MoId=task-6565 failed, error=
      --> (vim.fault.AlreadyExists) {
      -->    dynamicType = <unset>,
      -->    faultCause = (vmodl.MethodFault) null,
      -->    name = "rm-db-prod",
      -->    msg = "The specified key, name, or identifier already exists.",
      --> }
      <Children>",
      [#3] -->       "        <Step elapsedTime="00:00:00" endTime="2012-05-14T00:30:47" objectId="protected-vm-14118" startTime="2012-05-14T00:30:47" status="error">",
      [#3] -->       "          <Key>RecoveryStepRecoverVm.name</Key>",
      [#3] -->       "          <Name>rm-db-prod</Name>",
      [#3] -->       "          <fault>",
      [#3] -->       "              <_type>dr.fault.MultipleFault</_type>",
      [#3] -->       "              <faults>",
      [#3] -->       "                  <_length>1</_length>",
      [#3] -->       "                  <_type>vmodl.MethodFault[]</_type>",
      [#3] -->       "                  <e id="0">",
      [#3] -->       "                      <_type>dr.storageProvider.fault.StorageTestFailoverStartFailed</_type>",
      [#3] -->       "                      <faultCause>",
      [#3] -->       "                          <_type>dr.storageProvider.fault.StorageDeviceGroupTestFailoverStartFailed</_type>",
      [#3] -->       "                          <deviceGroup>SRM_NLSAS</deviceGroup>",
      [#3] -->       "                          <faultCause>",
      [#3] -->       "                              <_type>dr.storage.fault.DeviceGroupNotFound</_type>",
      [#3] -->       "                              <command>testFailoverStart</command>",
      [#3] -->       "                              <id>SRM_NLSAS</id>",
      [#3] -->       "                              <msg/>",
      [#3] -->       "                              <responseXml/>",
      [#3] -->       "        </faultCause>",
      [#3] -->       "                          <msg/>",
      [#3] -->       "      </faultCause>",
      [#3] -->       "                      <msg/>",
      [#3] -->       "    </e>",
      [#3] -->       "  </faults>",
      [#3] -->       "              <msg>Failed to create snapshots of replica devices. Failed to create snapshot of replica consistency group SRM_NLSAS. Expected consistency group &apos;SRM_NLSAS&apos; not found in SRA&apos;s &apos;testFailoverStart&apos; response.</msg>",
      [#3] -->       "</fault>",

       

      Cheers!