@rohitjain70 -

Please share the process you’re doing when you get your error. What Veeam version are you using? Are you creating Virtual Machine backup or physical machine backup. Are you using Veeam Backup & Replication or an Agent Backup. Need wayyy more details to hopefully be able to assist you.

And, keep in mind, this site isn’t Veeam Tech Support. We’re users just like you who can only offer suggestions. Hopefully we can get you going though.

Best.

Hi Shane,

I appreciate your insight and willingness to help out. I also acknowledge that this is a community group

• I am trying to take a backup of a Win11 Machine running on Hyper-V and the Hyper-V is running on a Windows 2022 server.
• I am using a Veeam B&R with administrative credentials. 

Ok, so it appears Veeam isn’t able to create a snapshot. Can you create a snapshot of this ‘attendance’ VM directly on Hyper-V?

Yes I am able to create a snapshot on Hyper-V

Ok. So what are yout Backup Job settings? Meaning, do you have Application Aware Processing enabled? If so, did you run a test on the account used to make sure it’s successful?

Backup Job Settings

Ok, so if you click ‘Test now’ does it run successfully? If so, ok. But, my suggestion is disable Application Aware Processing and try to run the job without it first.

Ok, that’s good. But go ahead & disable Application Aware Processing and try to run the job without it to see if it works.

Shane

• the Job without APplication Aware is turning out the same error. 
• With or Without “application aware”, I am getting error 

This is the summary of the Job & the result

@rohitjain70 -

Ok...well, at this point, I’m outta ideas. You could look at the Job log at:

C:\ProgramData\Veeam\Backup\<backup-job-name>.log and see if there is some more detailed information in there. Otherwise, I recommend getting ahold of Veeam Support so they can look at your logs and get more details about your environment to see what’s going on. If possible, let us know what they find so others who may have this same error and come across this post/thread can see what was done to resolve it.

Thanks.

Shane I really appreciate your time and efforts. I shall post my findings on this thread as soon as I get an answer

Ok. But, the problem is Veeam isn’t able to create a snapshot on the HV VM to be able to back it up. There is something interfering with the process. Firewall maybe? Unavailable network port maybe? Antivirus software running maybe? Something...

I have disabled the domain firewall and in my attempts I have tried various combination yet the error persist. Thats why I said that it should have been straight forward but it has become a nagging issue on why its not working.

ALso one aspect I forgot to mention, I am on a Community version.

Hi @rohitjain70,

Is the issue still present?

I was recently running in such kind of error so I got 2 questions:

Is the service account with that you added the Hyper-V server to Veeam local Administrator of the Hyper-V? Maybe you can post the user groups on the target server of the account you are using within Veeam.

Idea: Maybe you should check the UAC and suggest disabling it for testing purposes.

Second: Are you using Hyper-V SET (Switch Embedded Teaming) by any chance? I am still deep diving into the technology because I ran into very strange issues in the past weeks.

Best regards from Germany

Lukas

Another thought I had on this @rohitjain70 ...do you have latest version of Integration Services installed in the VM?

Since the server was operational since past 11 years, I had brought down the server and did a fresh install of Hyper-V. That solved the problem. 

But I am still unable to get a bare metal recovery of 2 physical IBM Blade servers(windows 2008 R2 server) (running AutoDesk License Services) and I had to virtualize them. The licenses are tied down to the MAC-ID .

Ans1- No I am not using Hyper-V Set

Ans2- everything was running with Highest Admin rights with no Antivirus and firewall disabled

Which version of Veeam are you using? You have to keep in mind that the current Veeam versions are no longer compatible with Win Server 2008 (not even 2012).

You can change the virtual MAC addresses of systems but in case you use physical hardware you will have to contact AutoDesk to change the license parameters.

Nice to hear hat the Hyper-V issue is solved!

Best regards

Lukas

Well, glad you’re at least able to take backups again. As Lukas shared, your OS versions you talk about there aren’t really supported anymore. Interesting you use Autodesk, as I do as well. The system you use for that may not be supported any longer either (tho may still work in your environment). Autodesk no longer has ‘legacy’ licensing models. They now use, as of a couple years ago, an OVA you install in your virtual environment to disseminate licenses. Just something you may wanna look into. 

As you have since resolved this issue, I recommend marking any of the comments which best helped you as ‘Best Answer’ so others with a similar issue who come across your post here may benefit. You can even mark your comment if you feel that helped 

Best.