similar to: Share problem : vfs object and preexec

I am trying to use shadow copy with Samba 4.0.9 on Debian 7 (wheezy), Linux kernel 3.2. Windows 7 clients on the LAN can not see Previous Verions of files stored on the server, although I believe I have set up directories with snapshots. Here are some highlights from smb.conf :- [global] server role = active directory domain controller domain logons = yes ... [Pluto] path

On Sun, 2016-10-30 at 14:10 +0100, Leander Schäfer via samba wrote: > Hi, > > I make use of shadow_copy2 and root preexec. The vfs root preexec is  > responsible to auto create home directories which initially don't > exist.  > The script behind it is well tested and works perfectly. > Unfortunaltely  > shadow_copy2 seems to be called before root preexec and fails due

Hi, I make use of shadow_copy2 and root preexec. The vfs root preexec is responsible to auto create home directories which initially don't exist. The script behind it is well tested and works perfectly. Unfortunaltely shadow_copy2 seems to be called before root preexec and fails due to the missing ZFS home share which causes the session to fail completely before root preexec even has a

We have: vfs objects = shadow_copy2 zfsacl (Actually, vfs objects = shadow_copy2 zfsacl fruit streams_xattr, but I wanted to point out the order of shadow_copy2 and zfsacl). To rule out shadow:format problems, I would create just one snapshot with a simple name and configure shadow:format accordingly. Also, is /public the mountpoint of the ZFS dataset? If not, then you might need

Hi, I have a FreeBSD 12.1 system with Samba 4.11.8 using ZFS and I want to get shadow copies working, however the clients (Windows 10) don't show anything in the 'previous versions' tab. I think it's doing something as it say 'working' for a short amount of time. Also if I crank up vfs debugging to 10 I get: [2020/10/05 16:50:03.879093, 10, pid=50572, effective(0, 0),

On 17/02/16 17:27, Ian wrote: > > On 2/17/2016 5:00 AM, Rowland penny wrote: >> On 17/02/16 00:03, Ian wrote: >>> I've recently attempted to migrate some windows server files over to >>> samba 4 hosted on a FreeNAS server. >>> >>> Using robocopy with the /copyall switch, I expected everything, >>> including ACL's and ownership

Hello I'm having a problem using the virusfilter and shadow_copy2 modules which, unless I'm mistaken, seems like a conflict between these modules. If I use the virusfilter, acl_xattr, recycle, shadow_copy2 and full_audit modules together, everything works perfectly, if I use the NOTHING, RENAME or DELETE actions of the virusfilter module. If I choose to use the QUARANTINE action for the

Hello I'm having a problem using the virusfilter and shadow_copy2 modules which, unless I'm mistaken, seems like a conflict between these modules. If I use the virusfilter, acl_xattr, recycle, shadow_copy2 and full_audit modules together, everything works perfectly, if I use the NOTHING, RENAME or DELETE actions of the virusfilter module. If I choose to use the QUARANTINE action for the

On 2/17/2016 9:43 AM, Rowland penny wrote: > On 17/02/16 17:27, Ian wrote: >> >> On 2/17/2016 5:00 AM, Rowland penny wrote: >>> On 17/02/16 00:03, Ian wrote: >>>> I've recently attempted to migrate some windows server files over to >>>> samba 4 hosted on a FreeNAS server. >>>> >>>> Using robocopy with the /copyall switch,

Sorry if config was messy, we were using this server for various tests including ADS tests and n-way master replication. Back on topic, I've done changes to configuration as you suggested. Runing debian as standalone server with beforementioned enviroment I can still copy files between shares on the same pool without pushing them through Windows client. Is this intended behavior? cat

On Thu, 2 Aug 2018 11:17:47 -0400 pisymbol <pisymbol at gmail.com> wrote: > On Thu, Aug 2, 2018 at 11:11 AM, Rowland Penny via samba < > samba at lists.samba.org> wrote: > > > On Thu, 2 Aug 2018 11:02:45 -0400 > > pisymbol <pisymbol at gmail.com> wrote: > > > > > Whoops! Replying to all! > > > > > > On Thu, Aug 2, 2018 at

I have: interfaces = lo0, eth2 and: socket address = 192.168.3.1 socket address = 127.0.0.l in my smb.conf, but when I try to "net group add anything" (on server running samba 3.5.2, as a DC): <asks for current log'ed in users's password> mypwd Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_CONNECTION_REFUSED So what am I missing? Shouldn't

Hi, When samba is joined to a 2k3 domain, UPN authentication does not work. It works using smbclient, but not from a workstation that is not part of the domain. I can reproduce this easily and provide logs and tcpdump's if necessary. The same problem does not occur when samba is joined to 2k8 or 2k12 domains. Is this by design? Am I missing something? - John -------------- next part

Hi there I'm having some troubles with Shadow Copy2 & zfs Snapshots. I have hourly and daily snapshots. If I use the following settings it works (but omits daily snapshots): vfs objects = shadow_copy2 shadow:snapdir = .zfs/snapshot shadow:sort = desc shadow:localtime = yes shadow:format = easysnap-hourly_%Y-%m-%d-%H-%M-UTC However when I try to use the BRE with the prefix,

On 2/17/2016 5:00 AM, Rowland penny wrote: > On 17/02/16 00:03, Ian wrote: >> I've recently attempted to migrate some windows server files over to >> samba 4 hosted on a FreeNAS server. >> >> Using robocopy with the /copyall switch, I expected everything, >> including ACL's and ownership information to transfer over. For the >> most part they have.

Hello, i installed zfs-auto-snapshot with Samba/Windows Shadow Copy. If the share contains "path = /srv/userdata/" it runs for me. But if I use "path = /srv/userdata/%U" I get no "Previous Versions" on my Win10 Client. I think the problem is the variable "shadow: snapdir = .zfs/snapshot". I tried with "shadow: snapdir = ../.zfs/snapshot" and

Hi Jeremy, Here's the log with log level 10: https://pastebin.com/0EAuz2B8 The location of the shared folder: /pool/shadowtest The location of the snapshots: /pool/shadowtest/.zfs/snapshot Here are how snapshots are named: autosnap_2019-09-01_13:29:01_daily autosnap_2019-09-01_13:29:01_hourly autosnap_2019-09-01_13:44:09_frequently And this is currently in my smb.conf file: [shadowtest]

The last email had 1 little error in the smb.conf that I forgot to edit for the email: skyhawk2x4tb was the old poolname, I have it renamed to /pool now, so this is not a source of the problem. ??????? Original Message ??????? On Sunday, September 1, 2019 2:20 PM, douxevip <douxevip at protonmail.com> wrote: > Hi Jeremy, > > Here's the log with log level 10:

Hi, Over the past several days I have been trying to get the shadow to work with samba but haven't been successful. Can someone check below config and let me know if I am missing something? We are using Equallogic SAN and iSCSI LUNS to mount volumes. I can cleanly access samba shares on Windows 7 clients but just not shadow copy. I have referred the official how-to but couldn't get it to

On 5/23/24 22:58, Andrew Bartlett wrote: > Can you post your smb.conf. Actually no, as I don't have *one* smb.conf. I'll add three of them (the last three were I had this problem) at the end of this email. As you can see they are not exactly identical. > Have you used any of our fallback VFS modules instead of xattrs? I'd say not, but see the smb.confs. > (This would