similar to: Samba 4.8.5 breaks Time Machine support

Hi I apt installed Samba Version 4.9.5-Debian (latest in their repos) on a fresh-built Raspbian Buster Lite release 2020-02-05. I put together the configuration outlined below by using the docs at https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X and https://www.samba.org/samba/docs/current/man-html/vfs_fruit.8.html. The underlying usb hard drive is an ext4 partition

TL;DR: Time Machine cannot create a *new* backup on my shared drive, but can add to an *existing* backup. I'm running macOS Catalina and my Time Machine backs up to a Debian 10 server with NetAtalk and Avahi. Since Mavericks macOS has preferred SMB, and given SMB is marginally faster I decided to switch to using SMB for the Time Machine shares. On a fresh AFP share I can start a new Time

I configured Samba 4.8.5 on Debian with vfs_fruit as a TimeMachine destination and while it detects it and does the initial backup to some extent (300GB out of 600GB), TimeMachine then fails with a message about the disk identity having changed. Options are “don’t backup” and “backup anyway”. When using “backup anyway”, the backup creates a secondary sparse image and starts from scratch, and won’t

Hi, I configured Samba 4.8.5 on Debian (Buster) with vfs_fruit as a TimeMachine destination and while it detects it and does the initial backup to some extent (30GB out of 200GB), TimeMachine then fails with a message about the disk identity having changed. Options are “don’t backup” and “backup anyway”. When using “backup anyway”, the backup creates a secondary sparse image and starts from

Computer A runs my samba server. Has unix extensions = off, wide links = on (don't think this one matters with unix extensions off...) This way, if I have a symlink on my shares, clients see it as a normal file, not as a symlink. This works fine, even for symlinks to files outside the shares paths. Except when the symlink points to a file that is on a CIFS mount. So say I have computer B

Hi. I try to make backups from one disk to another. I have .sparsebundle[1] directories on the source drive (/Volumes/data/). When rsync reaches the first .sparsebundle it stalls and stays there until i ctrl+c. I'm using OS X Yosemite and rsync version 3.1.1 protocol version 31 installed via homebrew. However, I had this problem on OS X Lion too using rsync 3.0.9. Actually, the reason I

I am an old UNIX and Mac hand but new to samba. My ultimate aim is to use a samba share with Time Machine. I have built an up to date version of samba (4.9.2) which has the necessary support for Time Machine and installed it on my linux system (ubuntu 18.04), and I have it sharing a volume which I can mount from my Mac. A good start ;) The problem is that I get permission errors whenever I try

Just chiming in here, I haven’t read all the previous posts so may be repeating… Mike Bombich has a good piece on benchmarks for various source/destination scenarios with rsync. https://bombich.com/kb/ccc3/how-long-should-clone-or-backup-take Note that copying to sparsebundle on local media is as fast as to local disk. Sparsebundle is a mac filesystem whereas NAS is not so certain file

On 2020-01-31 12:30, Johan Hattne wrote: > Dear all; > > On the recent topic of Time Machine backups: when backing up a machine > running macOS Mojave to a Samba server on Debian Buster with > buster-samba410 packages from https://apt.van-belle.nl/debian, we see > our logs filling up with messages like > > ../../source3/modules/vfs_fruit.c:7001(fruit_tmsize_do_dirent)

Hai, https://downloads.van-belle.nl/samba4/examples/ Here are 2 files for a time machine setup. An example config : samba-491-conf.txt And the timemachine.service file Get them and adjust your config. These are tested by other samba list users and they reported this works. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org]

Thank you. I will try your suggestions. First I will connect the NAS directly to the computer (Do you recommend USB2 or 1 Gb Ethernet? Or should I daisy chain external HD and NAS? Then it would look like this: Computer <--FW800--> HD <--USB2--> NAS The other option is HD <--FW800--> Computer <--USB2 or Ethernet 1000Mbit --> NAS But I still must say it is weird that

Hello Kevin, Mac OS by default looks for TimeMachine volumes over AFP not CIFS-SMB… Like you, I experimented with Samba a couple of years ago to try to get it to work anyway. With a few modifications on the client’s part and some configuration on the Samba server I got it to work… but recovery only worked for clients that I had configured in advance… Recovery with the Mac OS tools (Migration

Hai Daniel, Yes yes.. As you can see in my change log. ( found here, http://downloads.van-belle.nl/samba4/Buildlogs/stretch-experimental/ ) >From my changelog. samba (2:4.9.0+dfsg-1.1nmu~deb9) stretch; urgency=medium . * Non-maintainer upload. * Rebuild from Debian stretch from Debian Experimental * Bump build-depends cmocka 1.1.2 * enabled --enable-spotlight to make TimeMachine work

Hi everybody! I have a QNAP at home running firmware 4.4.2.1273 and I have configured it with NFS (for my iMac and FireTV) and SMB access (standalone server, for Win10 and iPhone/iPad Files access) Everything went fine till a certain point where many application would crash or behave in a very strange way when accessing SAMBA shares. Application can be Explorer++, OneCommander or File.app from

> On 11/02/2019, at 10:02 AM, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Mon, 11 Feb 2019 09:14:03 +1300 > Russell Fulton via samba <samba at lists.samba.org> wrote: > >> I am an old UNIX and Mac hand but new to samba. My ultimate aim is >> to use a samba share with Time Machine. I have built an up to date >> version of samba

TimeMachine is NOT enabled in the official debian packages. If you want time machine, report it at debian as bug/request if you want this enabled, and untill then, You can use my packages, where timemachine is enabled. Or rebuild the the debian packages your self and enable it, that part only is very easy. + what Rowland told you. ;-) Greetz, Louis > -----Oorspronkelijk

I have now - the 'net view' output is now sensible, and reports "Time Machine for gac" (which is the expected comment). But in log.smbd, it is now looking for a folder called "/backups/timemachine/DOMAIN\username" so access to the share itself is still not working 18 Sep 2019, 11:54 by samba at lists.samba.org: > Have you tried to replace?%U in the path

dbonde+forum+rsync.lists.samba.org at gmail.com wrote: > It is exactly as I wrote. On a network volume (A) a "sparse disk image bundle" (B), i.e., a type of disk image used in OS X, is stored. B is then mounted locally (i.e., local to where rsync is run) on a computer (C) where it appears as one of many volumes. > > In other words, B is stored on A. A is then mounted (using

I've set up a Samba share to allow Windows machines to connect to a Linux server. Samba is set up as so: # testparm Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[Pelena]" Processing section "[TimeMachine]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see

I am on a Mac OS 12.6.8. I have gotten Samba to work great with TimeMachine and general sharing of directories off the server which is running FreeBSD 13.2 with Samba Version 4.16.10. The one issue I am seeing is that when I have a Mac Disk Image mounted from a Samba share it will not unmount unless I hit the force eject option. When I run ?sudo smbstatus? on the server I see the mounted disk