@gck303
What happens if you spin up a new Windows Server 2019 and on the old Windows Server 2019 run the backup program and restore the backup on the new Windows Server 2019? Might be a solution?

I've encounter this error on a few occasions. There might be a few reasons:

• The VM has features or hardware requirements that cannot be met by the host (too much assigned memory, Network, CPU-cores, GPU or storage does not match with the server)
• The XOA has not been refreshed (it can help to sign out/sign in again and get a new session going)
• Force shutdown (Works sometimes, but sometimes not that even helps and might not always be a good solution)
• Try to use the XCP-NG Center (Even though it is old, it can also give some hits of what is wrong, it does not work though in 8.3)
• Restart the host (Last resort to resolve the issue for me at least)

Looking at your error message, it looks like there is some trouble with the network and storage. Have you maybe migrated the VM or such?