+1I try to connecting the SMB server to as VBO repository and always access denied, even i can write to the SMB folder using windows explorer.
In this article KB2971: How to add SMB repository to Veeam Backup for Microsoft 365 i can see we must computer name authentication on the share permission,
In my case the SMB server and VBO server is not joined to the domain, both of machines is standalone.
Anyone here know how we can use the SMB fo repository?
+12Please don‘t use a SMB Share.
Worst repository type ever for Veeam Backup for Microsoft 365. :)
And is planned to be deprecated (there is a text notification in the wizard about that, and in the KB).
To answer your question, nas and backup server must belong to the same domain. The KB is there to explain this requirement. There is no way around it.
Best,
Fabian
+4When both SMB and VBO servers are standalone (not domain-joined), you cannot use computer account authentication. Instead, configure the SMB share with explicit username/password permissions and add those credentials in VBO when creating the repository.
+1hi
noted with many thanks
+12Instead, configure the SMB share with explicit username/password permissions and add those credentials in VBO when creating the repository.
That option isn’t available with Veeam Backup for Microsoft 365. :-)
Best,
Fabian
+4Instead, configure the SMB share with explicit username/password permissions and add those credentials in VBO when creating the repository.
That option isn’t available with Veeam Backup for Microsoft 365. :-)
Best,
Fabian
if propose this Join both systems to a domain and grant share access to the VBO computer accounts.
+13Instead, configure the SMB share with explicit username/password permissions and add those credentials in VBO when creating the repository.
That option isn’t available with Veeam Backup for Microsoft 365. :-)
Best,
Fabian
if propose this Join both systems to a domain and grant share access to the VBO computer accounts.
Technically that would work but the highest best practice of Veeam (for a long time, luckily) is to not join Veeam systems to domains under normal circumstances due to security risks.
You would need a dedicated management domain that is hardened and that workload imo is only worth it for enterprise environments where user management (that cannot be managed by Veeam due to excessive numbers) is a thing.
Best
Lukas
+4Instead, configure the SMB share with explicit username/password permissions and add those credentials in VBO when creating the repository.
That option isn’t available with Veeam Backup for Microsoft 365. :-)
Best,
Fabian
if propose this Join both systems to a domain and grant share access to the VBO computer accounts.
Technically that would work but the highest best practice of Veeam (for a long time, luckily) is to not join Veeam systems to domains under normal circumstances due to security risks.
You would need a dedicated management domain that is hardened and that workload imo is only worth it for enterprise environments where user management (that cannot be managed by Veeam due to excessive numbers) is a thing.
Best
Lukas
Thank you, Lukas, for sharing that information. It really helped increase my knowledge and understanding. I appreciate your support!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
