Error adding External DPM in Azure Backup Server

Félix J Torres Tavárez 20

I have a new Azure Backup Server MABS v4. When I try to add my old Azure backup server I got an error: Adding External DPM : myoldserver failed:

Error 298: Recovery failed for NO_PARAM NO_PARAM on NO_PARAM.

Recommended action: Recover to an alternate location or try recovering from another recovery point.

Félix J Torres Tavárez 20 Reputation points

2024-07-30T17:04:50.16+00:00

Azure backup agent version is 2.0.951.0
SadiqhAhmed-MSFT 46,461 Reputation points Microsoft Employee

2024-07-31T08:11:25.98+00:00
@Félix J Torres Tavárez The error message "Error 298: Recovery failed for NO_PARAM NO_PARAM on NO_PARAM" indicates that there was an issue with the recovery process for the old Azure Backup Server. This could be due to a number of reasons, such as a corrupted backup database or an issue with the backup data.

Here are some steps you can try to resolve the issue:

Check the backup database: Make sure that the backup database on the old Azure Backup Server is not corrupted. You can do this by running a consistency check on the backup database using the following command in an elevated command prompt: dpmbackup -dbcc

Check the backup data: Make sure that the backup data on the old Azure Backup Server is not corrupted. You can do this by running a consistency check on the backup data using the following command in an elevated command prompt: dpmbackup -replicaconsistencycheck

Check the network connectivity: Make sure that there is network connectivity between the old Azure Backup Server and the new Azure Backup Server. You can do this by pinging the old Azure Backup Server from the new Azure Backup Server.

Check the credentials: Make sure that you are using the correct credentials to add the old Azure Backup Server to the new Azure Backup Server. You can do this by checking the credentials in the Azure portal.

Check the version compatibility: Make sure that the version of the old Azure Backup Server is compatible with the version of the new Azure Backup Server.

If none of the above steps work, try reinstalling the Azure Backup Server on the old server and then try adding it to the new Azure Backup Server again.

Hope this helps!
Félix J Torres Tavárez 20 Reputation points

2024-07-31T18:30:00.12+00:00

Hi. Thank you for your answer.

I haven't initiated the recovery process yet. The error occurred when I try to add the external DPM for a recovery. I want to have access to the online backups made by the old server.
Amardeep Saini 1,255 Reputation points Microsoft Employee

2024-08-02T12:17:03.3133333+00:00

@Félix J Torres Tavárez - Request you to please share a screen shot of the error message for better understanding and request you to please check the DPMUI logs which will help us to understand the failure reason.
Félix J Torres Tavárez 20 Reputation points

2024-08-02T21:11:17.3833333+00:00
Félix J Torres Tavárez 20 Reputation points

2024-08-02T21:56:32.1566667+00:00

This is the MSDPMCurr.errlog:

2148 2CC8 08/02 21:30:50.749 17 IntentServices.cpp(2201) 49EF13B6-A5FC-4642-8D12-CCF0E64F6B1E NORMAL CIntentServices::GetCloudRecoverableMachinesFromVaultCredential(). vaultCredentialsFilePath=C:\Users\user\Documents\OCE-RS-Vault_Tue Jul 30 2024.VaultCredentials

2148 2CC8 08/02 21:31:04.046 17 IntentServices.cpp(2263) 49EF13B6-A5FC-4642-8D12-CCF0E64F6B1E NORMAL CIntentServices::RefreshExternalDPMServersCloudMetadata().

2148 2CC8 08/02 21:31:04.062 08 Task.cs(235) NORMAL Changing task state from 'Invalid' -> 'Start' (5941ad7d-cb3a-44e0-b33e-97e032daacb5)

2148 2CC8 08/02 21:31:04.108 08 EventManager.cs(100) NORMAL Publishing event from ActiveJob.cs(291): JobStateChange, [JobID=da3ab77a-8268-47d9-b9ce-edcb79b4e97d]

2148 229C 08/02 21:31:04.108 08 ActiveJob.cs(316) NORMAL Start execution of job:'da3ab77a-8268-47d9-b9ce-edcb79b4e97d' in state:'Start'

2148 229C 08/02 21:31:04.108 08 ActivityWindow.cs(75) NORMAL Add new wait : da3ab77a-8268-47d9-b9ce-edcb79b4e97d(wait until: Thursday, August 22, 2024) @ Friday, August 2, 2024UTC

2148 229C 08/02 21:31:04.108 08 ActivityWindow.cs(198) NORMAL Setting timer for '1727999.9531293's...

2148 229C 08/02 21:31:04.108 08 ActiveJob.cs(1080) NORMAL Changing state of job: 'da3ab77a-8268-47d9-b9ce-edcb79b4e97d' from 'Start' -> 'GenerateWorkplan'

2148 229C 08/02 21:31:04.108 08 EventManager.cs(100) NORMAL Publishing event from ActiveJob.cs(1089): JobStateChange, [JobID=da3ab77a-8268-47d9-b9ce-edcb79b4e97d]

2148 229C 08/02 21:31:04.108 08 ActiveJob.cs(580) NORMAL Begin GenerateWorkplan:JobID=da3ab77a-8268-47d9-b9ce-edcb79b4e97d, ItemID=5941ad7d-cb3a-44e0-b33e-97e032daacb5

2148 229C 08/02 21:31:04.108 08 TaskExecutor.cs(82) 5941AD7D-CB3A-44E0-B33E-97E032DAACB5 NORMAL GenerateWorkplan(job=da3ab77a-8268-47d9-b9ce-edcb79b4e97d) - Entering

2148 229C 08/02 21:31:04.124 08 EventManager.cs(100) NORMAL Publishing event from TaskExecutor.cs(107): TaskCreated, [TaskID=5941ad7d-cb3a-44e0-b33e-97e032daacb5]

2148 229C 08/02 21:31:04.249 08 CloudToSaRestoreMetadataMachine.cs(71) 5941AD7D-CB3A-44E0-B33E-97E032DAACB5 NORMAL CloudToSaRestoreMetadataMachine : inside OnStartCloudBackupProviderJob call

2148 229C 08/02 21:31:05.452 08 ApplicationSettings_expanded.cs(4279) 5941AD7D-CB3A-44E0-B33E-97E032DAACB5 NORMAL cbpVersionInstalled :2.0.9251.0, cbpVersionRequired :2.0.9025.0

2148 229C 08/02 21:31:06.265 08 CloudToSaRestoreMetadataMachine.cs(219) 5941AD7D-CB3A-44E0-B33E-97E032DAACB5 WARNING Caught exception while recovering metadata: machine :oceazurebck02.oce.local, taskId:5941ad7d-cb3a-44e0-b33e-97e032daacb5. Exception = System.IO.DirectoryNotFoundException: Could not find a part of the path 'S:\Recover\ffd392ff-39ce-4c5d-bcf2-e6d8f8ff24c8'.

2148 229C 08/02 21:31:06.265 08 CloudToSaRestoreMetadataMachine.cs(219) 5941AD7D-CB3A-44E0-B33E-97E032DAACB5 WARNING at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

I think I found the error. The recover disk had a different drive letter than S.

I change the drive letter in the disk and now it's working but, where can I change this path (disk location)?

Accepted answer

Amardeep Saini 1,255 Reputation points Microsoft Employee

2024-08-05T10:09:08.1333333+00:00
@Félix J Torres Tavárez - If you are referring to Staging location for online restore which you needs to update from 'S:\Recover\ffd392ff-39ce-4c5d-bcf2-e6d8f8ff24c8'.

There are different ways to update the Staging Location. I am giving you the way to update the path using SQL query for DPM DB.

Open SSMS and run the following SQL Query against MAB Server DB:

select * from tbl_DLS_GlobalSetting where PropertyName='CloudRecoveryStagingArea'

It will retrieve the actual path, it might be S:\Recover\ffd392ff-39ce-4c5d-bcf2-e6d8f8ff24c8 in your case

update Tbl_dls_globalsetting set PropertyValue='C:\onlinerestore1' where propertyName='CloudRecoveryStagingArea'

It will update to the new path

Make sure to keep the staging location on a NTFS volume and not on REFS volume as restore will fail on REFS volume.

If the suggestions were helpful, click “Accept Answer” and Up-Vote it.
Please sign in to rate this answer.

1 person found this answer helpful.
Félix J Torres Tavárez 20 Reputation points

2024-08-06T13:18:56.9033333+00:00

It worked. Thank you!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error adding External DPM in Azure Backup Server

0 additional answers

Your answer