I wanted to try Veeam B&R Free again, now that I discovered a trick on re-issuing the 60 day trial key on ESXi hosts so I should be able to get past my old issue I blogged about “The VMware Screw“…
So I D/L the latest n greatest from Veeam and that’s B&R 9.5 Update 4, grab the latest builds here (Veeam Login Req)…
Run the installer, nothing special here. Love the new UI, amazing how much nicer it is vs the old Free Edition.
Anyway, navigate to Backup Infrastructure to add a Repo, in this case a simple USB HDD I was sharing via SMB on a FreeNAS server. I had created it with open access so no authentication was required to access the share.
As shown here, I was accessing the file share without issue in Windows Explorer…
However, attempting to add it as a Repo…
Whomp, whomm, whmomomomomom.
Kind of annoying that anonymous SMB is I guess not supported as a Repo type, or maybe just not with my particular setup, I’m not exactly sure what the exact reason for this error being hit as I don’t have access to Veeam source code. Anyway, I started to google for a possible solution, annoying the first result was simply a post which a Veeam rep simply posted to the second most common solution post which basically stated:
“add the registry setting:
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
DWORD: NetUseShareAccess = 1
As per KB1735”
Did that and…. Failed to get disk free space. Since a lot of people on these threads are mentioning the user of a username and password I decided to follow this guide on creating a user for an SMB share on FreeNAS.
Follow the Veeam wizard and… “Can’t get disk free space”
Ughhhh… I was about to give up and actually attempt a physical alternative then I noticed something people were saying…
ender – “Depending on your SMB server, you may need to enter the username as DOMAIN\user or SERVERNAME\user before it’s accepted.”
StivoBerlin – “Have you tried to write “YOUDOMAINONYOURSYNOLOGY\youruser” instead of only “youruser” for the NAS login ?”
michaelbrandi – “I have found that it makes a difference if you enter “full” credentials so not admin but IP\admin, not sure it’s universal, but it helped me.”
That’s when I added an account to Veeam as “FREENAS\TestUser” along with the password, and used that credential after entering the path, and got past the error!
I was actually rather impressed at the speed of the backups considering it was a USB drive shared over the network via SMB from FreeNAS…
Look at that, backed up a 20 gig vm in 8 minutes wooo! Not bad for Free.
Maybe I’ll re-follow up on my old free VM backup series and bring it back with a proper tut on each step required to make it work.
For now I hope this information helps someone!