Get in touch with us!

(ID 104 Details: Internal error code: 0x80990EF1) after MABSv2 update

Got problems after updating to MABS may update? | Microsoft recently released an update for Microsoft Azure Backup Server, “May 2017 update for Microsoft Azure Backup Server”. If you like me where protecting VMware server, you may have encountered this problem.

The Problem

After the update all protected vmware items fail, leaving you with an generic error.

unable to configure protection DPM could not start a recovery, 
consistency check, or initial replica creation job for VMware XXXXX on XXXXXXXXXXXX 
for following reason: (ID 3170) An unexpected error occurred while the job was running. 
(ID 104 Details: Internal error code: 0x80990EF1) 

If we dig deeper in the log files we will find that vixDiskLib generates VMWareErrorCode = 6.
In the VIX API reference documentation we can see that error code 6 is “VIX_E_NOT_SUPPORTED ,The operation is not supported.
https://www.vmware.com/support/developer/vix-api/vix17_reference/errors/errors.html

The solution

To fix this we need to get a newer version of VMware vSphere Virtual Disk Development Kit (VDDK).

  1. Go to https://my.vmware.com/web/vmware/details?productId=614&downloadGroup=VDDK65
  2. Download Virtual Disk Development Kit (VDDK)
  3. Use bugmenot.com if you don’t want to register for VMware 🙂
  4. Unzip the file and grab vixDiskLib.dll
  5. Replace the file located “[MABS Install location]\DPM\DPM\bin\VDDK\”
  6. Rerun consistency check or backup job.

Another solution

I think this problem is unique and probably only exists when upgrading MABS on Server 2012 R2. A better alternative solution is to make a new installation of MABS. Because of version 2 we now have support for Server 2016 and ReFS block cloning that will save you storage and time.

When moving protected vmware items from one MABS to another they may be locked by the origin server.

Bildresultat för vmware server is already protected by another dpm server

To release this configuration do the following.

  1. Stop protecting the member server on the old MABS
  2. Change the custom attribute “DPMServer” in vmware
  3. Refresh the production server in a new protection group on the new MABS
  4. Add the member server to a new or existing protection group on the new MABS

To change the custom attribute for your vmware server you can use the following script.

Connect-VIServer vcenter.internal.contoso.com

$vm = @(
"server1"
"server2"
"serverA"
"serverB"
)

$VM | % {
 $vmObject = Get-VM -Name $_ -ErrorAction Stop
 Set-Annotation -Entity $vmObject -CustomAttribute "DPMServer" -Value "" -ErrorAction Stop
}

And you are done!
Thanks for reading and happy backuping!
@MeapaX

Submit a Comment

Your email address will not be published. Required fields are marked *