similar to: 4.8.5 + TimeMachine = Disk identity changed on every connect, cannot backup

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

Hi, tl;dr - Samba 4.8.5 broke macOS's Time Machine support (at least for me), patching in the "follow-up patch" from https://bugzilla.samba.org/show_bug.cgi?id=13441 makes it work again. It would be great if it could be included in an official patch release soon. :) Just writing about the problem and solution here, in case someone else stumbles upon it. Couldn't find any

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

Is it possible to backup Mac OS devices through a Samba share on Samba 4.4.6 on Fedora 24 with Time Machine? I am able to successfully advertise the share through Avahi, connect to it in Finder, and read/write files. I am also able to see the share as a destination in Time Machine, but selecting it shows an error that "The selected network backup disk does not support the required

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

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

======================================================== "The best artists know what to leave out." Charles de Lint ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Changes since 4.8.4: -------------------- o Jeremy Allison <jra at samba.org>

======================================================== "The best artists know what to leave out." Charles de Lint ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Changes since 4.8.4: -------------------- o Jeremy Allison <jra at samba.org>

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

Well, I've made some progress. Excuse the detail, but this might help others as I've so far found NOTHING on this, including with the Mac Enterprise maillist (so far). If I unchecked all the Directory Utility mapping options, I was able to log in! Yeah! But, the UID.GID numbers were 1793602029.1840809715. Next I tried just setting the "Map group GID to attribute" to 10000 (my

Hi all, We use the vfs_fruit module and lately we have experienced that random files copied with Finder are being grayed out. We think this is probably due to the extended attribute "user.DosStream.AFP_AfpInfo:$DATA" not being updated/removed after the file is copied. If we manually remove the xattr in question with the command setfattr -d 'user.DosStream.AFP_AfpInfo:$DATA', the

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

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

Hello all, am considering setting up centos as a file storage/ backup destination for Mac's TimeMachine. all my users would get synced directly to specific folders on this machine.. needless to say space is of importance. where every user has an average 200 GB of data to b synced (entire system)... I have 27 users hence 27 *200 equals to almost 6 TB so I was considering getting either 4 *

======================================================== "Fall forward!" Denzel Washington ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include: ------------------------ o dns: Fix CNAME loop prevention using counter regression (bug

======================================================== "Fall forward!" Denzel Washington ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include: ------------------------ o dns: Fix CNAME loop prevention using counter regression (bug

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]

Hai, Can anyone tell me the "adviced" extra package versions for this release. I did a checkup at : https://www.samba.org/ftp/?C=M;O=D And i noticed the following. Ldb from 1.1.27 to 1.1.28, as mentiond in the changelog Talloc from 2.1.8 to 2.1.9, not mentioned in the changelog. Tdb 1.3.11 to 1.3.12, not mentioned in the changelog. Tevent 0.9.31 stays at 0.9.31 no change.

Release Announcements ===================== This is the fourth release candidate of Samba 4.6. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.6 will be the next version of the Samba suite. UPGRADING ========= vfs_fruit option