none
DPM 2010, second tape drive showing up as standalone RRS feed

  • Question

  • Have added another tape drive to the system but it is not adding itself to the existing library but is saying it is a standalone drive instead

    Have tried modifying the .xml file but no luck

    Any help much appreciated

    • Moved by MarcReynolds Tuesday, May 31, 2011 6:51 PM (From:Data Protection Manager)
    Tuesday, May 31, 2011 6:47 PM

Answers

  • Hi,

    All is good now. We discovered that we were using the wrong os architecture of dpmlibrarytest, it should of been x64 and not x86, so when we did that we got different results. Also the drivemapping tools on the server did not work initially either but the one from the download you sent me did so we then tried the 64bit drivemappingtool again and all is good. We recreated the dpmla.xml file and after that I did a rescan and refreshed the library and all was good. One library 2 tape drives.

    Thanks for all the help, much appreciated

    Dyron

    Monday, June 6, 2011 4:59 PM

All replies

  • Hi,

    If the meduim changer driver does not claim the device, it will remain as a standalone.  Try stopping and restarting the tape library (medium changer) device in device manager, then rescan in the DPM Console.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, May 31, 2011 7:53 PM
    Moderator
  • Hi,

     

    So I went into the device manger and diabled the medium changer driver and then did a rescan and then a refresh and still it is standalone

    Is this what you meant me to do?

    I can display my .xml file to see if there is sissues with it?

    Let me know

    Thanks

    Tuesday, May 31, 2011 9:11 PM
  • Hi,

    Please download the run the DPM tape Library Compatibility Checker tool and see what it finds.

    http://cid-885774776d4f197a.office.live.com/self.aspx/Public/DPMTapeLibraryCompatibilityCheckerTool-Beta.zip

    example of command to run:  DPMLibraryTest.exe /CERTIFY /TL \\.\Changer0  /ST 1 2 4 5


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, May 31, 2011 11:02 PM
    Moderator
  • Hi,

    So ran the test and all seemed to past except for the following error that I found in the log file, about not being to get dpmla.xml file path. So this might be the reason why the drive is standalone as when we tried to edit the file when adding another tape drive and it does not seem to make any difference when making changes.

    Any suggestions???

     0E5C 1FE8 06/01 17:55:29.575 30 dpmlibrarytesttool.cpp(954)   NORMAL CMDLINE: dpmlibrarytest.exe /certify /TL \\.\Changer0 /st 1 2 4 5
    0E5C 1FE8 06/01 17:55:29.576 30 utility.cpp(328)   NORMAL DPMLA Service is running, Do you want to stop it [Y/N :Default(Y)]:
    0E5C 1FE8 06/01 17:55:43.822 03 serviceutil.cpp(135) [00113D78]  NORMAL successfully stopped service : [DPMLA]
    0E5C 1FE8 06/01 17:55:43.822 30 utility.cpp(273)   WARNING Failed: Hr: = [0x80070424] QueryServiceStatus failed
    0E5C 1FE8 06/01 17:55:43.823 30 utility.cpp(349)   WARNING Failed: Hr: = [0x80070424] GetServiceStatus for NtmsSvc service failed, ignoring the failure
    0E5C 1FE8 06/01 17:55:43.823 30 utility.cpp(266)   WARNING Failed: Hr: = [0x80070424] : F: lVal : (HANDLE)(schService = OpenServiceW( schSCManager, strServiceName.PeekStr(), 0x0004))
    0E5C 1FE8 06/01 17:55:43.827 30 utility.cpp(195)   WARNING Failed: Hr: = [0x80070002] : F: lVal : HRESULT_FROM_WIN32(2)
    0E5C 1FE8 06/01 17:55:43.831 30 driveremapping.cpp(593) [00113D78]  NORMAL InstallPath path reg key not found
    0E5C 1FE8 06/01 17:55:43.831 30 driveremapping.cpp(594) [00113D78]  WARNING Failed: Hr: = [0x80070057] : R: lVal : E_INVALIDARG
    0E5C 1FE8 06/01 17:55:43.831 30 driveremapping.cpp(487) [00113D78]  NORMAL Failed to get DPMLA.xml file path, manual drive mapping will not be used
    0E5C 1FE8 06/01 17:55:43.832 30 cfgclass.cpp(1104) [00111928]  NORMAL We got 2  devices for class 0
    0E5C 1FE8 06/01 17:55:43.832 30 cfgclass.cpp(176) [02585FB4]  NORMAL Initializing Device with path \\?\scsi#sequential&ven_ibm&prod_ult3580-hh5#5&ee1d4f7&0&000300#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
    0E5C 1FE8 06/01 17:55:43.837 30 system.cpp(1183)   WARNING Failed: Hr: = [0x80070002] Failed to initialize IOCTL timeout from registry. Initializing with default timeout [900000 ms].
    0E5C 1FE8 06/01 17:55:43.837 30 system.cpp(1167)   WARNING Failed: Hr: = [0x80070002] : F: lVal : r.Open((( HKEY ) (ULONG_PTR)((LONG)0x80000002) ), L"Software\\Microsoft\\" L"Microsoft Data Protection Manager" L"\Agent")
    0E5C 1FE8 06/01 17:55:43.842 30 cfgclass.cpp(176) [02586384]  NORMAL Initializing Device with path \\?\scsi#sequential&ven_ibm&prod_ult3580-hh5#5&ee1d4f7&0&000500#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
    0E5C 1FE8 06/01 17:55:43.851 30 cfgclass.cpp(1104) [025869E0]  NORMAL We got 1  devices for class 1
    0E5C 1FE8 06/01 17:55:43.851 30 cfgclass.cpp(176) [0256505C]  NORMAL Initializing Device with path \\?\scsi#changer&ven_ibm&prod_3573-

    Wednesday, June 1, 2011 6:18 PM
  • Hmm - interesting.  Please check the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Setup key, there shoud be an installpath value pointing to c:\Program Files\Microsoft DPM\DPM\
    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, June 1, 2011 7:09 PM
    Moderator
  • Hi,

    That value is there on that setup key pointing to that path.

    What else is interesting is I took out all the tapes before running the dpm tape library compatibilty test just in case it would doing something to the other tapes, did fast inventory and for some reason the standalone drive went missing, but it was still saying it had 2 libraries and 2 drives in the summary window at the top of the page in spm management tab. I did the DPM test after this and it said there was 2 tape drives etc, but DPM itself did not show them properly

    I am now rebooting the server with DPM as there is something going on.

    After reboot the standalone drive showed up.

    I did the test again, followed the same procedure as above, took out all tapes and just added what they say to do, and the standalone did not disappear. Test ran and all was good, with same results as before. I do have the log if you would like to see it, it is quite long..

    Any ideas



    Wednesday, June 1, 2011 8:05 PM
  • HI,

    I'm checking to see what the library checker tool is looking for to get the path to the dpmla.xml file, I think once we fix that then the standalone drive will be moved to the library.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, June 2, 2011 11:02 AM
    Moderator
  • Hi,

    I just reproduced your log entry about the missing file path.

    1B70 17F8 06/02 18:09:28.887 30 driveremapping.cpp(487) [000000000047FAE0]  NORMAL Failed to get DPMLA.xml file path, manual drive mapping will not be used

    The tool is definetly looking for the registry key called HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Setup with an InstallPath value.  If we cannot read that key, we post the error.  Please rename that value and make a new one - then rerun the test and look in the log.  If it still reports problems reading that, then download process explorer from the www.sysinternals.com web site and monitor registry io for the process name DPMLibraryTest.exe.     

    Also, can you send the output of this command:  DPMLibraryTest.exe /certify /ll


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, June 2, 2011 6:22 PM
    Moderator
  • Hi,

    Ok I ran the dpmlibrarytest tool after renaming the reg value and the same results in the log. I downloaded the process explorer and ran it while doing the test again but do not know how to see what io is accessing the registry. The properties did not show anything. Can you help me on this?

    I ran the dpmlibrarytest.exe /certify /ll and here's the results..Thanks again for the help

    1750 12E8 06/02 21:25:12.865 30 dpmlibrarytesttool.cpp(954)   NORMAL CMDLINE: dpmlibrarytest.exe /certify /ll
    1750 12E8 06/02 21:25:12.866 30 utility.cpp(273)   WARNING Failed: Hr: = [0x80070424] QueryServiceStatus failed
    1750 12E8 06/02 21:25:12.866 30 utility.cpp(349)   WARNING Failed: Hr: = [0x80070424] GetServiceStatus for NtmsSvc service failed, ignoring the failure
    1750 12E8 06/02 21:25:12.866 30 utility.cpp(266)   WARNING Failed: Hr: = [0x80070424] : F: lVal : (HANDLE)(schService = OpenServiceW( schSCManager, strServiceName.PeekStr(), 0x0004))
    1750 12E8 06/02 21:25:12.871 30 utility.cpp(195)   WARNING Failed: Hr: = [0x80070002] : F: lVal : HRESULT_FROM_WIN32(2)
    1750 12E8 06/02 21:25:12.874 30 driveremapping.cpp(593) [00DD3D28]  NORMAL InstallPath path reg key not found
    1750 12E8 06/02 21:25:12.874 30 driveremapping.cpp(594) [00DD3D28]  WARNING Failed: Hr: = [0x80070057] : R: lVal : E_INVALIDARG
    1750 12E8 06/02 21:25:12.874 30 driveremapping.cpp(487) [00DD3D28]  NORMAL Failed to get DPMLA.xml file path, manual drive mapping will not be used
    1750 12E8 06/02 21:25:12.875 30 cfgclass.cpp(1104) [023C4FD0]  NORMAL We got 2  devices for class 0
    1750 12E8 06/02 21:25:12.875 30 cfgclass.cpp(176) [023E5F2C]  NORMAL Initializing Device with path \\?\scsi#sequential&ven_ibm&prod_ult3580-hh5#5&ee1d4f7&0&000300#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
    1750 12E8 06/02 21:25:12.880 30 system.cpp(1183)   WARNING Failed: Hr: = [0x80070002] Failed to initialize IOCTL timeout from registry. Initializing with default timeout [900000 ms].
    1750 12E8 06/02 21:25:12.880 30 system.cpp(1167)   WARNING Failed: Hr: = [0x80070002] : F: lVal : r.Open((( HKEY ) (ULONG_PTR)((LONG)0x80000002) ), L"Software\\Microsoft\\" L"Microsoft Data Protection Manager" L"\Agent")
    1750 12E8 06/02 21:25:12.886 30 cfgclass.cpp(176) [023E62FC]  NORMAL Initializing Device with path \\?\scsi#sequential&ven_ibm&prod_ult3580-hh5#5&ee1d4f7&0&000600#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
    1750 12E8 06/02 21:25:12.894 30 cfgclass.cpp(1104) [023E6958]  NORMAL We got 1  devices for class 1
    1750 12E8 06/02 21:25:12.894 30 cfgclass.cpp(176) [023C4FEC]  NORMAL Initializing Device with path \\?\scsi#changer&ven_ibm&prod_3573-tl#5&ee1d4f7&0&000301#{53f56310-b6bf-11d0-94f2-00a0c91efb8b}
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1061) [0009FB5C]  NORMAL Found a device with following details
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1062) [0009FB5C]  NORMAL           Device Name         : \\.\Changer0
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1063) [0009FB5C]  NORMAL           Device Serialnumber : 00X2U78R5412_LL0
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1064) [0009FB5C]  NORMAL           Device Vendor Name  : IBM Corporation
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1065) [0009FB5C]  NORMAL           Device Product Name : IBM TotalStorage 3573 Tape Library
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1066) [0009FB5C]  NORMAL           FirmWare Revision   : A.50
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1068) [0009FB5C]  NORMAL           Device SCSI Props   : (P,B,T,L)4,0,3,1
    1750 12E8 06/02 21:25:13.032 30 dpmdevicelayer.cpp(1076) [0009FB5C]  NORMAL           Driver Name   : ibmcg2k8
    1750 12E8 06/02 21:25:13.033 30 dpmdevicelayer.cpp(1002)   WARNING Failed: Hr: = [0x80070002] : F: lVal : versionBufSize = GetFileVersionInfoSizeW(path.PeekStr(), &dummyHandle)
    1750 12E8 06/02 21:25:13.033 30 dpmdevicelayer.cpp(1102) [0009FB5C]  NORMAL           Driver Version   : Failed to get
    1750 12E8 06/02 21:25:13.033 30 dpmdevicelayer.cpp(1061) [0009FB5C]  NORMAL Found a device with following details
    1750 12E8 06/02 21:25:13.033 30 dpmdevicelayer.cpp(1062) [0009FB5C]  NORMAL           Device Name         : \\.\Tape0
    1750 12E8 06/02 21:25:13.033 30 dpmdevicelayer.cpp(1063) [0009FB5C]  NORMAL           Device Serialnumber : 1068002619
    1750 12E8 06/02 21:25:13.033 30 dpmdevicelayer.cpp(1064) [0009FB5C]  NORMAL           Device Vendor Name  : IBM Corporation
    1750 12E8 06/02 21:25:13.033 30 dpmdevicelayer.cpp(1065) [0009FB5C]  NORMAL           Device Product Name : IBM ULT3580-HH5 SCSI Sequential Device
    1750 12E8 06/02 21:25:13.034 30 dpmdevicelayer.cpp(1066) [0009FB5C]  NORMAL           FirmWare Revision   : B171
    1750 12E8 06/02 21:25:13.034 30 dpmdevicelayer.cpp(1068) [0009FB5C]  NORMAL           Device SCSI Props   : (P,B,T,L)4,0,3,0
    1750 12E8 06/02 21:25:13.034 30 dpmdevicelayer.cpp(1076) [0009FB5C]  NORMAL           Driver Name   : ibmtp2k8
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1002)   WARNING Failed: Hr: = [0x80070002] : F: lVal : versionBufSize = GetFileVersionInfoSizeW(path.PeekStr(), &dummyHandle)
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1102) [0009FB5C]  NORMAL           Driver Version   : Failed to get
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1061) [0009FB5C]  NORMAL Found a device with following details
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1062) [0009FB5C]  NORMAL           Device Name         : \\.\Tape1
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1063) [0009FB5C]  NORMAL           Device Serialnumber : 1068006846
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1064) [0009FB5C]  NORMAL           Device Vendor Name  : IBM Corporation
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1065) [0009FB5C]  NORMAL           Device Product Name : IBM ULT3580-HH5 SCSI Sequential Device
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1066) [0009FB5C]  NORMAL           FirmWare Revision   : B171
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1068) [0009FB5C]  NORMAL           Device SCSI Props   : (P,B,T,L)4,0,6,0
    1750 12E8 06/02 21:25:13.035 30 dpmdevicelayer.cpp(1076) [0009FB5C]  NORMAL           Driver Name   : ibmtp2k8
    1750 12E8 06/02 21:25:13.036 30 dpmdevicelayer.cpp(1002)   WARNING Failed: Hr: = [0x80070002] : F: lVal : versionBufSize = GetFileVersionInfoSizeW(path.PeekStr(), &dummyHandle)
    1750 12E8 06/02 21:25:13.036 30 dpmdevicelayer.cpp(1102) [0009FB5C]  NORMAL           Driver Version   : Failed to get
    1750 12E8 06/02 21:25:13.038 30 dpmdevicelayer.cpp(975) [0009FB5C]  NORMAL  Rescan Operation completed with hr - 0x0
    1750 12E8 06/02 21:25:13.038 30 utility.cpp(590)   NORMAL Found 1 Tape Libraries
    1750 12E8 06/02 21:25:13.038 30 utility.cpp(591)   NORMAL Found 0 Standalone Drives
    1750 12E8 06/02 21:25:13.038 30 utility.cpp(595)   NORMAL --------------------- Tape Library Information ----------------
    1750 12E8 06/02 21:25:13.039 30 utility.cpp(601)   NORMAL LIBRARY (Drive bays - 2, Drives - 2)
    1750 12E8 06/02 21:25:13.039 30 utility.cpp(550)   NORMAL           Device Name         : \\.\Changer0
    1750 12E8 06/02 21:25:13.039 30 utility.cpp(551)   NORMAL           Device Serialnumber : 00X2U78R5412_LL0
    1750 12E8 06/02 21:25:13.040 30 utility.cpp(552)   NORMAL           Device Vendor Name  : IBM TotalStorage 3573 Tape Library
    1750 12E8 06/02 21:25:13.040 30 utility.cpp(553)   NORMAL           Device Product Name : IBM Corporation
    1750 12E8 06/02 21:25:13.040 30 utility.cpp(554)   NORMAL           FirmWare Revision     : A.50
    1750 12E8 06/02 21:25:13.041 30 utility.cpp(559)   NORMAL           Device SCSI Props   : (P,B,T,L)4,0,3,1
    1750 12E8 06/02 21:25:13.041 30 utility.cpp(606)   NORMAL DRIVE - 0, DRIVE Bay Index - 0
    1750 12E8 06/02 21:25:13.041 30 utility.cpp(550)   NORMAL           Device Name         : \\.\Tape0
    1750 12E8 06/02 21:25:13.042 30 utility.cpp(551)   NORMAL           Device Serialnumber : 1068002619
    1750 12E8 06/02 21:25:13.042 30 utility.cpp(552)   NORMAL           Device Vendor Name  : IBM ULT3580-HH5 SCSI Sequential Device
    1750 12E8 06/02 21:25:13.042 30 utility.cpp(553)   NORMAL           Device Product Name : IBM Corporation
    1750 12E8 06/02 21:25:13.043 30 utility.cpp(554)   NORMAL           FirmWare Revision     : B171
    1750 12E8 06/02 21:25:13.043 30 utility.cpp(559)   NORMAL           Device SCSI Props   : (P,B,T,L)4,0,3,0
    1750 12E8 06/02 21:25:13.043 30 utility.cpp(606)   NORMAL DRIVE - 1, DRIVE Bay Index - 1
    1750 12E8 06/02 21:25:13.043 30 utility.cpp(550)   NORMAL           Device Name         : \\.\Tape1
    1750 12E8 06/02 21:25:13.044 30 utility.cpp(551)   NORMAL           Device Serialnumber : 1068006846
    1750 12E8 06/02 21:25:13.044 30 utility.cpp(552)   NORMAL           Device Vendor Name  : IBM ULT3580-HH5 SCSI Sequential Device
    1750 12E8 06/02 21:25:13.044 30 utility.cpp(553)   NORMAL           Device Product Name : IBM Corporation
    1750 12E8 06/02 21:25:13.045 30 utility.cpp(554)   NORMAL           FirmWare Revision     : B171
    1750 12E8 06/02 21:25:13.045 30 utility.cpp(559)   NORMAL           Device SCSI Props   : (P,B,T,L)4,0,6,0
    1750 12E8 06/02 21:25:13.045 30 utility.cpp(611)   NORMAL ------------------- End of Tape Library Information -----------
    1750 12E8 06/02 21:25:13.047 30 dpmlibrarytesttool.cpp(1004)   NORMAL Operation completed successfully....
    1750 12E8 06/02 21:25:13.047 30 dpmlibrarytesttool.cpp(1005)   NORMAL VERBOSE INFORMATION FILE:
    1750 12E8 06/02 21:25:13.047 30 dpmlibrarytesttool.cpp(1005)   NORMAL C:\DPMTapeLibraryCompatibilityCheckerTool-Beta\x86\LibraryTestTool-6-Curr.errlog

     

    Thursday, June 2, 2011 9:30 PM
  •  

    Hi,

    I actually wanted you to make a new InstallPath value to see we could get the tool to recognize it. Re-run the tool with process monitor running with the following filter and process monitor should show it's not found. 

    http://i1101.photobucket.com/albums/g434/mjacquet/path-not-found.jpg

    Then make a new InstallPath value and rerun it again and see if the log is no longer complaining about the path not found. Once we get that fixed, then DPM should use the DPMLA.XML file and hopefully that will fix your issue.  If not, delete the dpmla.xml completly and then rescan.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, June 2, 2011 10:11 PM
    Moderator
  • Hello,

     

    I did make a new InstallPath value in registry, sorry I did not make it clear. I then ran the tool and same error on output file.

    I can try again with the settings you sent for the process filter and see what happens.

    If I remember, we actually tried to recreate a new dpmla.xml file to if it recreated and works properly but that was not the case.

    I will let you know

    Thursday, June 2, 2011 10:30 PM
  • Hi,

     

    How do I get the process monitor to show how your example is. I only see the cmd process which is running the dpmtest exe.

    Thanks

    Friday, June 3, 2011 6:30 PM
  • Hi,

    You can just add the executable to the filter ahead of time, and when the process starts, then it's activity will show in process monitor window.


    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, June 3, 2011 8:26 PM
    Moderator
  • Hi,

    All is good now. We discovered that we were using the wrong os architecture of dpmlibrarytest, it should of been x64 and not x86, so when we did that we got different results. Also the drivemapping tools on the server did not work initially either but the one from the download you sent me did so we then tried the 64bit drivemappingtool again and all is good. We recreated the dpmla.xml file and after that I did a rescan and refreshed the library and all was good. One library 2 tape drives.

    Thanks for all the help, much appreciated

    Dyron

    Monday, June 6, 2011 4:59 PM