The account being used is a domain administrator, tested with admin shares, and also added as local admin on the server just because. Same account currently being used for my other backup solution.
Are you able to access the [10.X.X.X:/volume1/BACKUPS/TEST/] folder from file backup proxy server via NFS and create/modify/read files there using the same account?
Can you please clarify what was selected as a source for nas job? Specifically the .vbk file or the folder that contains the vbk file? Any chance you have other Veeam jobs running that may lock the vbk file? Thank you!
wishr wrote: ↑Mar 12, 2020 4:33 pm
Are you able to access the [10.X.X.X:/volume1/BACKUPS/TEST/] folder from file backup proxy server via NFS and create/modify/read files there using the same account?
I just logged into the windows VM that B&R is installed on as the backup service account and used the Windows NFS client to mount to the NFS share, and successfully created then deleted a folder.
Can you please clarify what was selected as a source for nas job? Specifically the .vbk file or the folder that contains the vbk file? Any chance you have other Veeam jobs running that may lock the vbk file? Thank you!
I've got a handful (4) of HyperV VM's that I'm backing up and only have this single backup job and this is my only instance of Veeam. Also, nothing else is backing up these VM's either.
Even though I read the documentation on the fact earlier, I still had it in my head to treat it like my existing backup solution where backups are sent to NFS storage from the VM network address.
My HyperV host IP is on a separate management network and I did not have that specified in NFS security on the Synology, only the default network that the VM's utilize.
Added the management network and it's running right now.