similar to: vfs_shadow_copy2 not working

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:

On Sun, Sep 1, 2019 at 3:24 PM douxevip via samba <samba at lists.samba.org> wrote: > > 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 > >

On Sat, Aug 10, 2019 at 11:22:53PM +0000, douxevip via samba wrote: > So I'm trying to get shadow copies to work with Windows clients. The snapshots are being stored at /test/.zfs/snapshot > > The snapshots are being named like so: > > autosnap_2019-08-10_21:00:00_frequently > autosnap_2019-08-10_21:00:00_monthly > autosnap_2019-08-10_22:00:00_hourly > > This is

I'm actually on Debian 10, Proxmox standard installation. I'm not hitting the limit as far as I can tell. Do you know how I can find out where the mistake is? Is there an easier way to troubleshoot this? ??????? Original Message ??????? On Sunday, September 1, 2019 8:48 PM, Andrew Walker via samba <samba at lists.samba.org> wrote: > On Sun, Sep 1, 2019 at 3:24 PM douxevip via

Hello Dear Samba Users, I have sucessfully set a samba share on a centos 7 box (samba 4.6.2) and succeeded into make work snapshots (vfs_shadow_copy2 with xfs and lvm). The snapshots appears well in windows previous versions. However, I expected to go further with snapshots and use the options "shadow:snapprefix" and "shadow:delimiter"in order to filter daily, weekly

Hi I could not get a custom "shadow:delimiter" for the vfs shadow_copy2 module to work successfully for me with Samba 4.6.2. I did not try previous versions. Based on my testing it seems that an additional line of code is needed in vfs_shadow_copy2.c as shown in the patch below (some comment updates are included too for code readability). Without the below patch, previous versions

Hi Sebastian, why are you using shadow:snapprefix if this is just ?snap?? Does it work using ONLY shadow:format = snap_GMT-%Y.%m.%d-%H.%M.%S ? If you use snapprefix you also need to use shadow:delimiter (in your case this would be ?_?). However, I never managed to get it working with snapprefix on my machines. Alexander > On Monday, May 22, 2023 at 2:52 PM, Sebastian Neustein via samba

Hello all, I already successfully configured shadow copy service without a delimiter and regex. But as soon as I try to get this to work with regex, nothing shows up on the win client. My config looks like this: [global] shadow: localtime = yes shadow: sort = desc shadow: format = _%FT%T shadow: delimiter = _ shadow: snapprefix = ^\(monthly\)\{0,1\}\(weekly\)\{0,1\}\(daily\)\{0,1\}$

Hi I am trying to get shadow_copy2 to read gluster snapshots and provide the users with previous versions of their files. Here is my smb.conf: [global] ??????? security = ADS ??????? workgroup = AD ??????? realm = AD.XXX.XX ??????? netbios name = A32X ??????? log file = /var/log/samba/%m ??????? log level = 1 ??????? idmap config * : backend = tdb ??????? idmap config * : range =

Hi Alexander # net conf delparm projects shadow:snapprefix does not change a thing. The error persists. (I killed my smb session before trying again). log still says: [2023/05/22 15:23:23.324179,? 1] ../../source3/modules/vfs_shadow_copy2.c:2222(shadow_copy2_get_shadow_copy_data) ? shadow_copy2_get_shadow_copy_data: SMB_VFS_NEXT_OPEN failed for

On Thu, 2023-05-25 at 16:45 +0200, Sebastian Neustein wrote: > > Does it make a difference if you re-mount the volume without 'acl' > > option? Even otherwise can you try listing the snapshot contents > > from the server as a user(and not super user) who in reality tries > > to list previous versions from Windows? I feel like it has > > something to do with

> Does it make a difference if you re-mount the volume without 'acl' > option? Even otherwise can you try listing the snapshot contents from > the server as a user(and not super user) who in reality tries to list > previous versions from Windows? I feel like it has something to do with > permissions setup for the user accessing the share. It does make a difference! First

Hi, As per the list.samba.org link, did you try including the delimiter within the format, ie as shown in the following? shadow:snapprefix = ^d[A-Za-z0-9]*y$ shadow:delimiter = _IPG_ shadow:format = _IPG_%Y.%m.%d-%H.%M.%S Regards, Mike On 16/02/2018 16:50, Edouard Guigné via samba wrote: > Hello Dear Samba Users, > > I have sucessfully set a samba share on a centos 7 box (samba 4.6.2)

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,

Hi (+mailing list again for the archives) My config which does show previous versions: # /usr/local/samba/sbin/smbd --version Version 4.6.11 To avoid having this config block within in each share, I define the following within the [global] section:   shadow:snapprefix = ^\(monthly\)\{0,1\}\(weekly\)\{0,1\}\(daily\)\{0,1\}$   shadow:delimiter = _UTC_   shadow:format =

Hi, I notice you're using 4.6.2 and I'm using 4.6.11. I made the following comment at some point within [global]:   #disable "unix extensions" to avoid using "allow insecure wide links"   #  for access to ../xxxx_SNAPS for BTRFS "previous versions" snapshots   #  --it seems to have reverted once more to not need the below two settings   ##unix

On Wed, Jul 31, 2019 at 11:02:18AM +0000, douxevip via samba wrote: > Hi all, is there anybody on the mailing list who is more knowledgeable about SMB direct? Would appreciate some pointers. See below. Thanks. > > -------- Original Message -------- > On Jul 25, 2019, 22:52, douxevip via samba < samba at lists.samba.org> wrote: > Hello all, I was reading up on SMB Direct

Hello all, I was reading up on SMB Direct support and it seems very interesting. I looked through slides of a presentation by Stefan Metzmacher about SMB Direct last year: https://www.samba.org/~metze/presentations/2018/SDC/StefanMetzmacher_SDC2018-SMB-Direct-Status-rev1-presentation.pdf I was wondering what the current support of of SMB Direct for Samba. I have a Windows 10 Pro for Workstations

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