Should Veeam server be in the domain?

[frankive]

As the topic states, should the Veeam server be in the domain as a best practice?
I have tried a veeam server outside the domain out to a customer, but when I try to run surebackup I get the same error as the guy in this blog:
http://www.rickygao.com/cannot-start-hy ... s-invalid/

The problem is that I cant run that powershell since the vm is removed after the job has failed.

Pretty sure this error would go away if the server is in domain?
What is pros and cons for putting the domain server in domain or not?

Thanks.

[Gostev]

No, it's definitely not required. We fully support workgroup environments, and I know of a quite a few customers who simply do not have Active Directory deployed in the first place (almost purely Linux shops). Of course, you need to be prepared for dealing with various security issues when using Windows components in this case, and those issues are really not going to be specific to Veeam. Microsoft designs most of their things around Active Directory, so it can be very challenging to try to exist without one. Thanks!

[frankive]

Thanks. Good to know it is supported
Any chance that someone has seen this behaviour with the same error message that I got? Or should iI open a support case?

[foggy]

Yes, it is always recommended to contact support directly with technical issues like that, as most likely deep logs analysis is required for investigation.

[frankive]

Thanks. Case # 00636271

hopefully we can get the rid of this error without joining the server to the domain so the surebackup can run fine

[foggy]

Thanks for providing the case ID, much appreciated.

[frankive]

This "solves" the problem if i just do a test restore of a vm. ( http://blogs.msdn.com/b/virtual_pc_guy/ ... 70539.aspx )

But it will not work with Surebackup. I even tried to hit the powershell every seconds during the surebackup but it didn't work.
So it seems that Veeam (or Hyper-V) doesn't make the new host the owner of the VM.
Fair enought when running a VM-restore, but with Surebackup there should perhaps be a workaround to make it 100% automagical?