similar to: vfs_shadow_copy2 with different snapshot format

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 in my smb.conf: [test] vfs objects = shadow_copy2 shadow:snapdir = /test/.zfs/snapshot shadow:snapprefix =

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]

Greetings, I am trying to use vfs_shadow_copy2 with samba samba-4.2.7. I have a share exported at /export/smb400/. A snapshot of the share is on a separate block device, which is mounted at /export_shadows/volume-00000001/@GMT-2016.02.08-11.48.00/. Samba configuration for the share is: vfs objects = shadow_copy2 shadow:snapdir = /export_shadows/volume-00000001 shadow:fixinodes = yes (Note: I

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 Mon, Feb 08, 2016 at 06:33:25PM +0200, Alex Lyakas wrote: > Greetings, > > I am trying to use vfs_shadow_copy2 with samba samba-4.2.7. > > I have a share exported at /export/smb400/. A snapshot of the share is on a > separate block device, which is mounted at > /export_shadows/volume-00000001/@GMT-2016.02.08-11.48.00/. Samba > configuration for the share is: > >

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 Uri, Thanks for your response. We do not want to delete the share in smb.conf and later to reconfigure it without the shadow copy. We want to keep the shadow copy and rotate the snapshots. For example, we want to keep 24 hourly snapshots, and every hour we create a new snapshot and unmount the oldest one. But since customers can be restoring from the oldest snapshot right now, it is not

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 Jeremy, The use case is that we want to automatically rotate the snapshots. For example, we want to keep 24 hourly snapshots, and every hour we create a new snapshot and unmount the oldest one. But since customers can be restoring from the oldest snapshot right now, it is not deterministic when we will be able to unmount the oldest snapshot. So at that moment we want all active restore

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

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

Hi all, At some point recently my customers can no longer see GPFS snapshots under the Windows Previous Versions tab. It simply says "No previous versions available". If a fileset is exported with the flag "force user = root" then Previous Versions *are* displayed. [2016/07/06 10:07:35.602080, 3] ../source3/smbd/vfs.c:1322(check_reduced_name) check_reduced_name:

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),

Hi, Wondering if anyone can help with a weird issue I'm having - Just set up a new server (RHEL 7.4) and have migrated my samba configuration from my old server (Fedora 25), I'm experiencing an issue where by if my the name of my workgroup a domain i.e. it has a period in it, then none of my Linux clients can detect the broadcast and smbtree on both client and server is completely empty.

In IRC today, someone who was hitting that same IB performance ceiling that occasionally gets reported had this to say [11:50] <nissim> first, I ran fedora which is not supported by Mellanox OFED distro [11:50] <nissim> so I moved to CentOS 6.3 [11:51] <nissim> next I removed all distibution related infiniband rpms and build the latest OFED package [11:52] <nissim>

I'm about to do some testing with a an OSX 10.9 client connected to sernet samba 4.1.5 to see what things work and don't both from the finder and from the terminal with unix extensions = yes and no. Does anyone know of any show stopping issues that occur with unix extensions = yes and the latest samba (or 3.6.x, or 4.0.x a) and the latest OSX (or latest update with 10.7 & 10.8)?

On Sun, 2017-04-02 at 22:42 +0100, Michael Miller via samba wrote: > 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  >

Hi, I've been migrating data from an old striped 3.0.x gluster install to a 3.3 beta install. I copied all the data to a regular XFS partition (4K blocksize) from the old gluster striped volume and it totaled 9.2TB. With the old setup I used the following option in a "volume stripe" block in the configuration file in a client : volume stripe type cluster/stripe option

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, 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)