none
DPM and vCentre issue

    Question

  • Trying to backup virtual machines within VMware and connecting to VCentre to create a snapshot.  The job fails in DPM and removes the snapshot off each VM.

    DPN encountered error from VMware Disk SubSsytem. Server - #### ErrorCode - 18000 (ID 33620 Details: Internal error code 0x80990EF1)

    Anyone know the resolve?  At present we can only perform host level backups rather than direct target to vCentre.

    Monday, September 17, 2018 1:42 PM

All replies

  • Hello!

    What version and build of DPM are you running and what is your vCenter version?

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, September 17, 2018 1:53 PM
  • DPM 1807 v5.1.378.0

    vCentre 5.5.0 3000241

    Monday, September 17, 2018 2:08 PM
  • Hi Leon,

    This has already been done,

    These are the logs from DPM:

    0938       0CE8      09/13     16:36:14.437       31           vixdiskutils.cpp(24)                         E102A650-DD5C-4024-9341-9770D8338736   NORMAL             Message From VDDK Lib:VixDiskLibVim: Login failure. Callback error 18000 at 2500.

    0938       0CE8      09/13     16:36:14.439       31           vixdiskwrapper.cpp(317)                              E102A650-DD5C-4024-9341-9770D8338736            WARNING           VMWareErrorCode = 18000

    When connect directly to an ESX host, the VM's back up with no issue.

    When you point the DPM at the VCentre server and attempt a backup, a snapshot is created but within minutes it's removing the snapshot and the backup has failed with the original error on our first post but the logs show as the above.

    Thanks

    Carl

    Monday, September 17, 2018 2:32 PM
  • Since DPM is agentless on the VMware server and all VMware API calls are performed by the DPMAgent in the DPM Server, I'd suggest you start looking for errors returned by VMware.

    You could also have a look inside the DPMRACurr.errlog under the C:\Program Files\Microsoft System Center\DPM\DPM\Temp folder.

    Search for VMWareErrorCode and check whether one is found.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, September 17, 2018 8:24 PM
  • Hi Leon,

    The following from above is from the DPMRACurr.errlog.

    0938       0CE8      09/13     16:36:14.437       31           vixdiskutils.cpp(24)                         E102A650-DD5C-4024-9341-9770D8338736   NORMAL             Message From VDDK Lib:VixDiskLibVim: Login failure. Callback error 18000 at 2500.

    0938       0CE8      09/13     16:36:14.439       31           vixdiskwrapper.cpp(317)                              E102A650-DD5C-4024-9341-9770D8338736            WARNING           VMWareErrorCode = 18000

    Tuesday, September 18, 2018 8:01 AM
  • 18000 – VIX_E_CANNOT_CONNECT_TO_HOST
    Cannot connect to host.

    DPM is always remotely authenticating with the VMware server. This authentication is required and performed every time DPM interacts with VMware servers. DPM securely stores the required credentials locally in Windows Credentials Manager and uses them whenever needed. Since these credentials can be changed periodically, and because a datacenter may have multiple vCenters or ESX hosts that need different credentials, DPM has built-in credentials management.

    However, before creating a credential in DPM, the VMware user account used for the credential must have certain privileges.

    (These privileges are assigned to Roles in the vCenter or the vSphere client).


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, September 18, 2018 8:20 AM
  • As a test we are using administrator@vsphere.local which has all privileges within VCentre
    Tuesday, September 18, 2018 9:13 AM
  • If the ESXi servers are managed by vCenter, the vCenter should be added to DPM. Otherwise, add the ESXi server to DPM.

    DPM uses a certificate to communicate securely with the VMware server,  DPM connects to VMware via https so the certificate that is installed on VCenter or ESX host must be trusted by the DPM server.

    Also note that each ESX server will have its own certificate, however if the vCenter server is added as a protected server, you do not have to deal with the certificates of all the other ESX servers that are managed by that vCenter server.

    Have you tried by only having the vCenter as a protected server in DPM?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, September 18, 2018 9:34 AM
  • Hi Leon,

    Yes we've tried it with only VCentre being added and the connection is successful.

    The backup job starts, creates a snapshot > tries to capture a disk and gets denied > removes snapshot > job shows as failed in DPM.

    When you connect directly to the host and backup a VM - successful 


    Tuesday, September 18, 2018 10:15 AM
  • Can you provide the settings of one of your VMware virtual machine?

    Also are you using FQDN or IP address to identify your vCenter?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, September 18, 2018 2:10 PM
  • How do you mean by settings?

    We are using the FQDN of the VCentre which it has a successful connection and as I said it does initiate a snapshot creation when a job starts from DPM within VCentre.

    Tuesday, September 18, 2018 3:55 PM
  • What I meant was do the VMware virtual machines have any "special" configuration like shared disks/pass-through disks and so on.

    Did you have a look at the prerequisites and limitations on the following link?

    https://docs.microsoft.com/en-us/system-center/dpm/back-up-vmware?view=sc-dpm-1801#prerequisites-and-limitations


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, September 19, 2018 1:11 PM
  • Hi Leon yes I did look at the link prior to installing.

    In regards to the VM hard disks, they are not set to independent or protected.

    I think the issue is in VCentre because when we connect the DPM server to a host directly and a back VM up, it's fine.

    Something in VCentre is refusing an API call.

    Thursday, September 20, 2018 12:11 PM
  • I agree, it does seem that something's not right on the vCenter, you could try asking in the VMware Community.

    Blog: https://thesystemcenterblog.com LinkedIn:

    • Proposed as answer by CarlOrmesher88 Tuesday, November 20, 2018 3:24 PM
    Thursday, September 20, 2018 12:21 PM
  • Hi,

    Just checking if you have any update on your issue?


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, October 3, 2018 8:40 PM
  • Hey there - did you ever find a solution to this issue?
    Friday, May 3, 2019 10:14 PM