rpenny at samba.org
Fri Aug 28 17:52:33 UTC 2020
On 28/08/2020 16:49, Christopher Wensink via samba wrote:
> Thank you everyone in advance for your time and support I am the
> Administrator of a small network, with about 60 desktops (mostly windows
> 10) that connect to a Linux VM running samba for file sharing). In the
> last few months I completed the transition from the Samba server running
> as a vm on an OpenVZ machine. It was running Centos 6, with an older
> version of samba. Now the server has been migrated to a vmware esxi
> server, with the same amount of provisioned CPU and Ram resources, and a
> bigger hard drive, running Centos 7 with Samba 4.10.4.
> Aug 28 10:22:27 luigi2 smbd: [2020/08/28 10:22:27.284420,
> 0] ../../source3/modules/vfs_default.c:1287(vfswrap_fsctl)
> Aug 28 10:22:27 luigi2 smbd: FSCTL_GET_SHADOW_COPY_DATA:
> connectpath /shares/documents/<share>, failed - NT_STATUS_ACCESS_DENIED.
> Aug 28 10:24:29 luigi2 smbd: [2020/08/28 10:24:29.937661,
It looks the shadow copy does not have access to a file it is trying to
> vfs objects = shadow_copy2
> comment = Public files read by all but written by few
> path = /shares/documents/public
> valid users = @users
> read only = no
> inherit permissions = Yes
> shadow:basedir = /shares/documents
> shadow:snapdir = ../.documents
You only appear to be using the shadow_copy2 vfs object with one share,
so I would move the 'vfs objects' line into the share from 'global'
> A separate backup system is taking backups of the server on a vm
> snapshot level daily and on a file level hourly, unrelated to
> snapshots. Do I need the snapshots functionality? I have not set this
> up, and I don't know if I need to? What are your recommendations?
I would read 'man vfs_shadow_copy2', especially the section at the bottom.
Only you can decide if you need this facility, why was it set up
More information about the samba