Hi ​@spider32 -

What exactly is the question you’re asking with regards to snapshot testing?

I have to agree here that a test would need power off due to the disk being locked as you stated.  You should provide feedback on the article at the bottom using the link to have them update it.

I tried to attach the vmdk based on this KB article and got the following error:

I find Veeam’s article to be accurate so just checking if I miss something. 

I have a backup job that fails using hotadd so trying to isolate where the issue is. 

If you’re just asking if the source VM needs to be powered off...the answer is no. I just tested this myself and it worked. I tried with taking a snap on the source VM in both ways → with memory, and without memory but via quiesence.

Did you review the requirements for Hotadd from the 2 links listed at the top?

https://helpcenter.veeam.com/docs/backup/vsphere/virtual_appliance.html#requirements-for-the-virtual-appliance-mode

and

https://www.veeam.com/kb1054

Is your source VM disk a scsi disk? Independent? IDE? Other? Make sure you’re source VM is supported for Hotadd or the testing won’t succeed.

Let us know.

Best.

When you go to attach the source VM disk ​@spider32 , you attach the PARENT/base/original disk, not the snapshot. Is that the process you’re doing? Again..worked for me. From the log you shared (not sure where you got that from..vSphere?)..looks like you were trying to attach the snap disk and not base/parent disk.

Go through the 2 links I shared...from KB1184...and make sure your source VM is supported. If you have snapshots on it currently, make sure to remove them first before doing the test so you have a ‘clean’ source VM.

Thanks for testing.

Yes, my requirements checked out. Also, I tried the base and the snap vmdks. I got errors on both tries. Good to know that the KB article checks out. I will retry and figure where the issue is in my case. 

Ok...keep us posted. 

For you, it makes sense then that this particular VM you’re having problems with is failing then. In other words a hotadd test failure here just validates the Veeam backup job failure.

You have a hotadd supportability issue with the source VM somewhere. Hopefully one of those 2 links will help you find where.

Best of luck and hopefully you get it sorted out to work as expected.  We are here to help if needed.

I was able to do the hotadd this time. I tried on two different VMs and two different proxies prior, need to go back and review what was the issue.

Thanks again for checking out the KB article and running the test.  

Nice! Glad to hear you got it sorted Spider. 👍🏻

Glad to hear that you got it sorted out.