Veeam Community - Unable to add an AD server

Hi ​@Infra ALAINE -

Welcome to the Community. Needing more info here, though not entirely sure we can assist. I’ll start off with saying your best bet is to contact Support...even if you’re using free version of whatever Veeam backup product, you can still contact Support. 

So, what product are you using?..VBR or Agent for Windows or combination of both? What are you trying to do?...backup, recover, or both? Is your domain controller down? If so, and you’ve used domain accounts for everything, then the error you’re getting makes sense. If you’re using Veeam Agent for Windows, you can check the logs and see if anything definitve shows there:

C:\ProgramData\Veeam\Endpoint\

or, for VBR:

C:\ProgramData\Veeam\Backup\<job-folder>\<job-name>.log

Please provide more info and we can try and assist.

Thanks.

Hello,

Thank you for your feedback.

We use Veeam B&R Community to back up our servers. Our domain controller has no problems at the moment.

We will examine the logs and report them here.

[SHostNameResolver] Using hostnames resolving policy: UseOnlyOriginalHostNames
[14.11.2024 19:31:06.371]    <14>    Info (3)    [SNetworkAddressResolver] Resolved ['SRVDOMAINEAF2', '10.33.61.32'] by Kerberos preferred strategy host names and IP addresses. IPAddressKind: [IPv4]. Result: ['SRVDOMAINEXXX', 'XX.XX.XX.XX].
[14.11.2024 19:31:06.403]    <18>    Info (3)    [RPC] Getting version of the deployment service. Failed.
[14.11.2024 19:31:06.403]    <18>   Error (3)    [RPC] Accès refusé.
[14.11.2024 19:31:06.403]    <18>   Error (3)    [RPC] RPC function call failed. Function name: [GetSvcVersion]. Target machine: [SRVDOMAINXXXX:6160].
[14.11.2024 19:31:06.403]    <14>   Error (3)    Native method execution failed: ping service - Accès refusé.
[14.11.2024 19:31:06.403]    <14>   Error (3)    RPC function call failed. Function name: [GetSvcVersion]. Target machine: [SRVDOMAINEXXXX:6160].
[14.11.2024 19:31:06.434]    <14> Warning (3)    [SRVDOMAINEXX] Failed to connect to Installer service on SRVDOMAINEAF2:6160. Reason: [SRVDOMAINEXX] Failed to check whether remote Installer service is available.

Based on the error you are getting you should check your domain health to ensure it is functional.  To me that is where there failure points to but checking the logs will also help.

it's very strange, it worked a little while ago and my domain is fully functional...

Can you try another account for the backup instead of the Domain Admin to see if that works?  Maybe create a service account with domain rights to test.

i have tested with another account with domain admin privilege, and the result it’s the same

Then you will need to see if the logs can point you to the issue or symptom otherwise I would suggest a Support ticket at this point to get better assistance.  The community is not technical support and we offer as many suggestions as we can to try and help.

J’ai ouvert le ticket et jattend le retour. Voici un extrait des logs :

[SHostNameResolver] Using hostnames resolving policy: UseOnlyOriginalHostNames
[14.11.2024 19:31:06.371]    <14>    Info (3)    [SNetworkAddressResolver] Resolved ['SRVDOMAINEAF2', '10.33.61.32'] by Kerberos preferred strategy host names and IP addresses. IPAddressKind: [IPv4]. Result: ['SRVDOMAINEXXX', 'XX.XX.XX.XX'].
[14.11.2024 19:31:06.403]    <18>    Info (3)    [RPC] Getting version of the deployment service. Failed.
[14.11.2024 19:31:06.403]    <18>   Error (3)    [RPC] Accès refusé.
[14.11.2024 19:31:06.403]    <18>   Error (3)    [RPC] RPC function call failed. Function name: [GetSvcVersion]. Target machine: [SRVDOMAINEAF2:6160].
[14.11.2024 19:31:06.403]    <14>   Error (3)    Native method execution failed: ping service - Accès refusé.
[14.11.2024 19:31:06.403]    <14>   Error (3)    RPC function call failed. Function name: [GetSvcVersion]. Target machine: [SRVDOMAINEXXX:6160].
[14.11.2024 19:31:06.434]    <14> Warning (3)    [SRVDOMAINEXXX] Failed to connect to Installer service on SRVDOMAINEAF2:6160. Reason: [SRVDOMAINEXXX] Failed to check whether remote Installer service is available.

we have already opened a support ticket and are waiting for feedback

That is great.  That will be the best thing to get a quicker answer for your issue.

Ok..good. Keep us posted what they say.

Hello ​@Infra ALAINE 

do you respect the BP on your Veeam server ?
https://bp.veeam.com/vbr/3_Build_structures/B_Veeam_Components/B_VBR_Server/Backup_Server.html

Hi ​@Infra ALAINE 

Yesterday, I successfully completed the task in my production environment before configuring any VAW backup jobs. Here’s a summary of the steps I followed:

Check Connectivity: I first verified connectivity from the Veeam Backup & Replication (VBR) server to the guest machine where the Veeam Agent for Windows (VAW) is installed. I ensured that the required ports are open between the VBR server and the guest machine.

Install Agent: I then proceeded to install the VAW agent from the VBR console. During the installation, I provided the service account credentials, ensuring that the account had local admin access on the guest machine. Once the installation was successful, I configured the agent within the backup job.

Troubleshooting Backup Job Failures: If the backup job fails after this, there is likely another separate issue. In that case, we need to check the connectivity from the backup repository server to the agent machine and ensure the required ports are open for communication.

Check this blog regarding DC:

https://www.veeam.com/blog/backing-up-domain-controller-best-practices-for-ad-protection.html

Glad to hear you solved the issue and it was fairly simple.

Glad the reinstall took care of the issue for you 👍🏻