none
Cannot restore from tape DPM 2016 RRS feed

  • Question

  • Dear all,

    I have the following issue - DPM 2016 1807 cannot restore backup from tapes. The backups were performed by the same server (not imported).

    As I mentioned, backups are successful, but restore cannot be performed. The following error occurred when I've tried to restore anything from the tapes:

    (l of the services, mentioned below are running.)

    Monday, July 29, 2019 12:48 PM

All replies

  • Hello Marin,

    I just want to make sure, did you check that the services mentioned in the error message are not disabled and that they are running?

    I would also advise you to check the DPM log on the DPM server for more clues, you’ll find it over here:

    • %ProgramFiles%\Microsoft System Center\DPM\DPM\Temp\MSDPMCurr.errlog

    Side note: The support for DPM 1807 end on January 24, 2020, so you have about 6 months of support left, I would advise you to start planning for an upgrade soon.

    Best regards,

    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, July 29, 2019 6:14 PM
  • I've checked the log. After the error .crash file is generated. These are the last lines in it:

    16F8 07/30 13:34:42.662 01 TaskInstance.cs(447) 8F33D589-48E2-4199-BF9A-9AF972447115 NORMAL Task: Initial transition enqueued, startState='Restore.StartState'
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING Caught unhandled exception : Microsoft.Internal.EnterpriseStorage.Dls.DB.DBCorruptionException: Couldn't access DataSourceInfo '00000000-0000-0000-0000-000000000000' in the database
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.DataSourceInfo.GetDataSourceInfo(SqlContext ctx, Guid datasourceIdLocal)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.GetDataSourceInfo(Guid datasourceId)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.WriterHelper.CommandParamsHelper.GetWriterId()
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.WriterHelper.CommandParamsHelper.GetSourceCommunicationParameters(Guid taskId, Guid verbId)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.WriterHelper.DataTransferCommonTaskHelper.get_SourceCommunicationParameters()
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.Prm.StartRestoreBlock.MTARestoreDatasetSend(Message msg)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Transition.Execute(Message msg)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Engine.ChangeState(Message msg)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.TaskInstance.Process(Object dummy)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.FsmThreadFunction.Function(Object taskThreadContextObj)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
    0394 1738 07/30 13:34:42.947 68 DpmThreadPool.cs(121) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING    at System.Threading.ThreadPoolWorkQueue.Dispatch()
    0394 1738 07/30 13:34:42.962 68 DpmThreadPool.cs(149) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING Attempting to write error to the event log Couldn't access DataSourceInfo '00000000-0000-0000-0000-000000000000' in the database
    0394 1738 07/30 13:34:42.962 02 EventManager.cs(143) 8F33D589-48E2-4199-BF9A-9AF972447115 NORMAL Logging event to NT log from DpmThreadPool.cs(163): FatalServiceError
    0394 1738 07/30 13:34:42.962 68 DpmThreadPool.cs(170) 8F33D589-48E2-4199-BF9A-9AF972447115 WARNING Attempting to invoke Watson
    0394 1738 07/30 13:34:42.978 09 everettexception.cpp(762) 8F33D589-48E2-4199-BF9A-9AF972447115 CRITICAL Exception Message = Couldn't access DataSourceInfo '00000000-0000-0000-0000-000000000000' in the database of type Microsoft.Internal.EnterpriseStorage.Dls.DB.DBCorruptionException, process will terminate after generating dump


    Tuesday, July 30, 2019 1:45 PM
  • This is logged in the event viewer with event id 943:

    Problem Details:
    <FatalServiceError><__System><ID>19</ID><Seq>1232</Seq><TimeCreated>8/1/2019 2:30:28 PM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>DBCorruptionException</ExceptionType><ExceptionMessage>Couldn't access DataSourceInfo '00000000-0000-0000-0000-000000000000' in the database</ExceptionMessage><ExceptionDetails>Microsoft.Internal.EnterpriseStorage.Dls.DB.DBCorruptionException: Couldn't access DataSourceInfo '00000000-0000-0000-0000-000000000000' in the database

    I've did DBCC check db, everything seems ok.

    Thursday, August 1, 2019 3:03 PM
  • Is the tape from another DPM or just the same that the backups were performed from?

    A few things to try:

    1. You could try verifying the tape to see whether the tape is bad or not, you can check this with the Test-DPMTapeData PowerShell cmdlet.

    2. Have you tried picking a different recovery point to see if the restore also fails or not? Try with the same and with another tape to see the behaviour.

    3. Instead of recovering from the Recovery tab, right-click the tape in the library and "view tape details", click on the dataset representing the data you need to recover, then click on the Copy button. That will copy that dataset to a location of your choice. See if that restores correctly.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 6, 2019 8:09 PM
  • Hi,

    1. I'm using VTL so no need to test the tape.

    2. I've tried several tapes, including brand new - created specially for the test. Every one of them fails.

    3. This particular problem (the screenshot) occurs exactly when I try the Copy button.

    Br,

    Marin

    Thursday, August 8, 2019 1:54 PM
  • What types of workloads are stored on these virtual tapes?

    There was a fix for DPM 2016 (not DPM 1807) in the latest Update Rollup 7 that fixes an issue when trying to recover Hyper-V VM as files in 'Disk to Tape (D-T)' backup scenarios.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 12, 2019 8:10 AM
  • Hi Leon,

    Virtual machines backed up from Hyper-V cluster. Never had an issue with 2012/2012 R2 with the same DD2200.

    The server is a virtual machine on the same cluster, but the backups are performed without any problems, event at the moment. So I can't understand the source of the problem.

    Br,

    Marin

    Monday, August 12, 2019 1:08 PM
  • It might have to do with the code defect that Mike is talking about over here:
    https://social.technet.microsoft.com/Forums/en-US/7f8c0f43-043d-4906-ab9b-a0d773ca77aa/dpm-2019-is-it-possible-to-choose-not-to-use-rct-but-child-partition-?forum=dataprotectionmanager

    (See Mike Jaquet's reply at the bottom).

    This code defect has only been fixed for DPM 2016 in the latest Update Rollup as I mentioned above.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, August 12, 2019 1:13 PM
  • Thanks Leon.

    My version is 1807 which assumes that I cannot do anything, correct?

    I cannot find any information whether downgrade from 1807 to DPM 2016 is possible?

    Br,

    Marin

    Tuesday, August 13, 2019 8:27 AM
  • As DPM 1807 is part of a different release channel "Semi-Annual Channel (SAC)", it is unfortunately not possible to downgrade or upgrade to DPM 2016.

    You can however upgrade to DPM 2019, but the issue persists there (until Update Rollup 1 for DPM 2019 is out).

    Here's the supported upgrade paths:

    Since Microsoft has decided to discontinue the Semi-Annual Channel release channel, I would strongly recommend you to start planning an upgrade, as the support for DPM 1807 end on January 24, 2020.

    If you do decide to perform an upgrade from DPM 1807 to DPM 2019, you can follow my step-by-step guide over here:
    https://thesystemcenterblog.com/2019/03/17/upgrading-to-dpm-2019-step-by-step/


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Proposed as answer by Leon Laude Tuesday, August 20, 2019 7:06 AM
    Tuesday, August 13, 2019 8:38 AM