If the network is not built using AD, the backup copy job seems to get stuck for 2 days or more waiting for resources.

[Yukinobu]

Hi Guys,

A backup copy job was waiting for resources for more than 2 days.
As for the actual task, there were no resource shortages, so we manually stopped and re-ran the backup copy job, and the resources were immediately allocated to the task and the job was successful.

I checked with Veeam support(Case: 07281685) as to why it was waiting resource, and they replied that it was because it was not name resolved in AD and failed over to NTLM.

According to Veeam Support, Veeam Backup & Replication assumes that the network is built using AD, and the solution is to build a new AD and join the server.

I am not understanding this answer of Veeam support, does anyone know?

Kind Regards,
Yukinobu Asami

[PetrM]

Hello,

Please allow me to have some time to contact our support leaders in order to get more clarity or to escalate your support request. The provided statement looks a bit confusing, I agree.

Thanks!

[pmichelli]

I purposely kept Veeam off the domain. It lives in a workgroup in a secure vLan and I have had zero problems

[DanielJ]

What is the target of the copy job? I have the same problem with StoreOnce Catalyst jobs, at least since version 11. Waiting for resources for days until killed, immediately retried, works. Not on a domain.

[Yukinobu]

Hi,

I do not believe Veeam needs to join the domain, but Veeam support seems to disagree.

HPE Storeonce is not used.
The issue occurred with a backup copy job from Scale-out repository(Windows extent) to Linux repository.

[PetrM]

Hello,

Please let me clarify the details with the support team, I'll update the topic once I hear back from my colleagues. There is no requirement to join the backup server to a domain, for example on this page:

For large environments, adding the backup server and other backup infrastructure components to a management domain in a separate Active Directory forest is the best practice for building the most secure infrastructure.

For medium-sized and small environments, backup infrastructure components can be placed to a separate workgroup. If you want to use specific Veeam Backup Enterprise Manager features, for example, SAML authentication or restore of Microsoft Exchange items, you can add this component to the domain.

Also, you may have a look at this topic.

Thanks!

[Yukinobu]

Hi,

Thank you for your confirmation.
Veeam support says that they are seeing frequent "Resolved by NTLM only strategy" messages in the logs, which is what is causing the delays.

[PetrM]

Hello,

My colleagues from our support team escalated the request to a higher level in order to analyze the issue deeper and look for more convenient solutions than to rebuild AD. I'm pretty sure our engineers will find out the root cause, but the case seems to be sophisticated and it takes some time.

Thanks!