none
0x80990f43 Trying to backup ISCSI drive after switching hardware RRS feed

  • Question

  • We are using DPM 2012 to backup a Windows 2008 R2 server. It was running under Hyper-V and had a ISCSI attached as drive F.

    We migrated the server to another cluster and also moved the F drive to new ISCSI storage. When I try to set up the backup I get this error trying to backup the F drive:

    DPM cannot access the path F:\ because part of the path has been deleted or renamed.

    Check the path and enter it again.

    ID: 36
    Details: Internal error code: 0x80990F43

    I uninstalled the DPM agent and deleted the server from DPM, rebooted, reinstalled the agent, rebooted again, but I get the same error.

    Monday, February 16, 2015 6:16 PM

Answers

  • Hi,

    DPM tracks protected volumes using the Windows assigned volume guid as seen in mountvol.exe output.  Since you changed the F: volume to new Iscsi storage that means Windows assigned a new volume GUD to that volume.

    You can use Migrate-Datasource powershell script to re-associate that new volume to the DPM replica volume

    Using Migrate-Datasource

    Migrate-Datasource is a command-line script that lets you continue protecting a data source (file, folder, volume, or share) to the same replica volume even after it has been migrated to a different volume on the same protected computer. You have to run the Migrate-Datasource script even if you have not changed the drive letters of the volume because DPM recognizes volumes by the GUID and not the drive letter.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, February 16, 2015 7:03 PM
    Moderator

All replies

  • Hi,

    DPM tracks protected volumes using the Windows assigned volume guid as seen in mountvol.exe output.  Since you changed the F: volume to new Iscsi storage that means Windows assigned a new volume GUD to that volume.

    You can use Migrate-Datasource powershell script to re-associate that new volume to the DPM replica volume

    Using Migrate-Datasource

    Migrate-Datasource is a command-line script that lets you continue protecting a data source (file, folder, volume, or share) to the same replica volume even after it has been migrated to a different volume on the same protected computer. You have to run the Migrate-Datasource script even if you have not changed the drive letters of the volume because DPM recognizes volumes by the GUID and not the drive letter.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, February 16, 2015 7:03 PM
    Moderator
  • This is what I get when I run the script:

    Windows PowerShell transcript start
    Start time: 20150216140916
    Username  : AD\chapan 
    Machine  : ITMD-1D0ZCZ1 (Microsoft Windows NT 6.1.7601 Service Pack 1) 
    **********************
    Transcript started, output file is c:\temp\cmh.txt
    PS C:\Program Files\Microsoft Data Protection Manager\DPM2012R2\bin>  migrate-datasource -dpmservername scdpm -option auto -psname tv25.ad.milwaukee.gov 
    WARNING: Connecting to DPM server: scdpm
    Running inquiry on the PS
    Finished running inquiry
    NEW-OBJECT : Exception calling ".ctor" with "0" argument(s): 
    "DatabaseInfoRegKey RegKey shouldn't be null"
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:47 char:12
    +     $ctx = NEW-OBJECT -Typename 
    Microsoft.Internal.EnterpriseStorage.Dls.DB.SqlC ...
    +            
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [New-Object], MethodInvoca 
       tionException
        + FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.Power 
       Shell.Commands.NewObjectCommand
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:49 char:5
    +     $ctx.open()
    +     ~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:51 char:5
    +     $cmd = $ctx.createcommand()
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    The property 'commandtext' cannot be found on this object. Verify that the 
    property exists and can be set.
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:53 char:5
    +     $cmd.commandtext = $query
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : PropertyNotFound
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:55 char:5
    +     $reader = $cmd.executereader()
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:64 char:5
    +     $reader.close()
    +     ~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:66 char:5
    +     $cmd.dispose()
    +     ~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    You cannot call a method on a null-valued expression.
    At C:\Program Files\Microsoft Data Protection 
    Manager\DPM2012R2\bin\Migrate-DataSource.ps1:68 char:5
    +     $ctx.close()
    +     ~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull
     
    Could not find any volumes for migrating automatically

    PS C:\Program Files\Microsoft Data Protection Manager\DPM2012R2\bin>  stop-transcript 
    **********************
    Windows PowerShell transcript end
    End time: 20150216141026
    **********************

    Monday, February 16, 2015 8:11 PM
  • Hi,

    Please run from the DPM PowerShell command window.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, February 16, 2015 8:34 PM
    Moderator
  • That is where I did run it.
    Monday, February 16, 2015 8:46 PM
  • Hi,

    The above is showing the Windows power shell - please launch the DPM power shell - and let it prompt for input.

    Copyright (C) 2014 Microsoft Corporation. All rights reserved.


         Welcome to the DPM Management Shell!

     Full list of cmdlets: Get-Command
     Only DPM cmdlets: Get-DPMCommand
     Get general help: help
     Get help for a cmdlet: help <cmdlet-name> or <cmdlet-name> -?
     Get definition of a cmdlet: Get-Command <cmdlet-name> -Syntax
     Sample DPM scripts: Get-DPMSampleScript

    PS C:\Program Files\Microsoft DPM\DPM\bin> .\Migrate-DataSource.ps1
    DPMServer:


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, February 16, 2015 9:24 PM
    Moderator
  • Hi Mike

    I too get the same error when attempting to setup protection again for some drives moved (detached/attached) to another host server.   I have already deleted the DPM replicas.    Migrate-DataSource does not show the volumes which exhibit this error. (ID 36).  Any ideas?

    Ray

    Monday, March 23, 2015 5:45 AM
  • Hi,

    The script will not work across protected servers, it only re-associates DPM replica volumes with changed volumes guids on the same protected server.  You will need to re-protect the volume on the new protected server, it will be seen as a new data source, so it will have to create new replica. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, March 23, 2015 2:18 PM
    Moderator
  • Hi Mike

    It's when I try and re-protect the volume (by modifying PG and selecting server/volume again) that I get this error even though the replica is deleted off DPM server disks.

    Tuesday, March 24, 2015 9:04 PM
  • Hi,

    Do you have a secondary DPM Server in the configuration ?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, March 24, 2015 10:05 PM
    Moderator
  • No - single DPM server.

    Tuesday, March 24, 2015 10:25 PM
  • Hi,

    Unfortunately, it seems like a DPM SQL DB inconsistency that will require additional investigation that cannot be done if a forum setting.

    If you want to pursue this immediately, you can visit the following web site to open a support incident. The charge to your Credit Card will not be processed until your case is resolved and closed, if it's a code defect in the DPM then we wave all charges.

    http://support.microsoft.com/select/Default.aspx?target=assistance

    In the Quick product finder, enter:

    System Center Data Protection Manager [2007 or 2010]
    System Center 2012 then select System Center 2012 Data Protection Manager
    System Center 2012 R2 then select System Center 2012 R2 Data Protection Manager


    In the next screen, chose the option that applies.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, March 25, 2015 2:48 PM
    Moderator