Quantcast
Channel: Data Protection Manager - Tape Protection forum
Viewing all articles
Browse latest Browse all 706

DPM 1801 - External DPM Tapes disappears after closing console

$
0
0

Dear folks,

we are trying to upgrade a DPM2010 system to DPM v. 1801


Unfortunately, there doesn't seem to be any way to import the old database information, so we decided we will have to make do with losing disk protection.

However, we would like all the old tape backups to still be available in the console. Hence, on the test system, we imported a few tapes and recataloged them.

Now the data shows under "External DPM tapes". Recovery works. Fine.

However, when closing the console, "External dpm tapes" does no longer show when re-opening. Also, recataloging tapes doesn't work until they are marked free and unfree again!

If trying to recover from the tape by right clicking->View Contents->Copy, once the job starts, DPM crashes:

>> Microsoft.Internal.EnterpriseStorage.Dls.DB.DBCorruptionException: Couldn't access DataSourceInfo '00000000-0000-0000-0000-000000000000' in the databaseat Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.DataSourceInfo.GetDataSourceInfo(SqlContext ctx, Guid datasourceIdLocal) at Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.GetDataSourceInfo(Guid datasourceId) at Microsoft.Internal.EnterpriseStorage.Dls.WriterHelper.CommandParamsHelper.GetWriterId() at Microsoft.Internal.EnterpriseStorage.Dls.WriterHelper.CommandParamsHelper.GetSourceCommunicationParameters(Guid taskId, Guid verbId) at Microsoft.Internal.EnterpriseStorage.Dls.WriterHelper.DataTransferCommonTaskHelper.get_SourceCommunicationParameters() at Microsoft.Internal.EnterpriseStorage.Dls.Prm.StartRestoreBlock.MTARestoreDatasetSend(Message msg) at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Transition.Execute(Message msg) at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Engine.ChangeState(Message msg) at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.TaskInstance.Process(Object dummy) at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.FsmThreadFunction.Function(Object taskThreadContextObj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

Surely, DPM 1801 can't be so broken as to make recovering data after upgrading so iffy??

Alternatively, if there is a way to upgrade from the old database, we could take a look at that, too.


Viewing all articles
Browse latest Browse all 706

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>