Timemachine Application Support Thread

[BeardElk]

On 8/22/2023 at 1:01 AM, wgstarks said:

This usually means that you are mapping the backup to a destination in the image. Attach your docker run command to your next post.

Thanks for your input, but I've decided to not continue forward with my timemachine setup as I already have a nextcloud thats working and it would only be a few apps that the timemachine would govern over. 

[EdgarWallace]

This Docker is great and it is backing up one MBAir (256GB) one MBPro (512GB) and one iMac (1TB). It was running rock solid but now it caused an issue: I am using disk1 exclusively for this TM Docker and it filled up the drive by 100%. It's a 3TB drive and Docker run command is:

-e 'VOLUME_SIZE_LIMIT'='3 T'

 

I thought that TM is removing the oldest files. What is best practice?

[ScottAS2]

49 minutes ago, EdgarWallace said:

This Docker is great and it is backing up one MBAir (256GB) one MBPro (512GB) and one iMac (1TB). It was running rock solid but now it caused an issue: I am using disk1 exclusively for this TM Docker and it filled up the drive by 100%. It's a 3TB drive and Docker run command is:

-e 'VOLUME_SIZE_LIMIT'='3 T'

 

I thought that TM is removing the oldest files. What is best practice?

 

I suspect this is a powers of 10 vs powers of 2 issue and the 3TB you're declaring in the Docker parameters is slightly larger than the 3TB your drive actually holds. Time Machine's "do I need to delete old backups?" check looks only at the declared size, and pays no regard to the underlying storage (it will also ignore any storage contents that aren't sparsebundles!). I suspect if you declare a slightly smaller size, say 2.5TB*, Time Machine will realise it's full and start deleting.

* n TB is about 9.05% smaller than n TiB, but some wiggle room is probably a good idea.

[EdgarWallace]

Great explanation, thanks a lot @ScottAS2 I wasn't aware that 2.5 TB is possible but no complaints with that setting from a dockers perspective 🙂

TM is reporting 1.32 TB available but it's still not running. Hopefully I don't have to delete files manually.....

[ScottAS2]

15 hours ago, EdgarWallace said:

TM is reporting 1.32 TB available but it's still not running. Hopefully I don't have to delete files manually.....

 

Deleting backups from Time Machine manually isn't all that hard. If you connect to your Time Machine share in the Finder, mount the disk image, and go into it, you'll see a bunch of folders named for the date and time they represent a backup of. You can then delete as you see fit.

 

With regards to Time Machine not recognising the reduced quota, try removing the backup location and adding it again (which you can do without disrupting your history. Although it will say the angst-inducing "waiting to complete first backup" when you re-add the location, don't panic: it'll find the history once it does the first "new" backup).

[EdgarWallace]

Thanks @ScottAS2

There were only 20k left on the drive and i think that's why i couldn't delete the old datasets. I then deleted the complete TM-set and now everything is up and running again.

[jackieyang9]

Question: what should be selected as network type? I tried leaving it default (none) and custom eth0. Neither of them work.

[ScottAS2]

On 9/6/2023 at 9:06 AM, jackieyang9 said:

Question: what should be selected as network type? I tried leaving it default (none) and custom eth0. Neither of them work.

 

Usually the custom eth0 is the one to go for, because that allows the service to advertise itself on the network. What sort of not work are you getting?

[jackieyang9]

18 hours ago, ScottAS2 said:

 

Usually the custom eth0 is the one to go for, because that allows the service to advertise itself on the network. What sort of not work are you getting?

Thanks for the response. Running with custom eth0 does seem better. At least I can connect to the drive. However, I'm getting "The backup disk image could not be created." when backing up on my Mac.

I checked log in my console and here are the log around that time filtered by "backup":

 

default	19:38:15.537085-0700	TimeMachineSettings	[0x10d60ac20] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.537085-0700	SystemUIServer	[0x11e60c610] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.537216-0700	SystemUIServer	[0x11e706ca0] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.537431-0700	SystemUIServer	[0x11e70c900] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.542511-0700	backupd	[0x135fbd820] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135fbd820
default	19:38:15.543309-0700	backupd	[0x135f77ce0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135f77ce0
default	19:38:15.544008-0700	backupd	[0x135eaaee0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135eaaee0
default	19:38:15.545370-0700	backupd	[0x135e989c0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135e989c0
default	19:38:15.560856-0700	backupd	[0x135fbd820] invalidated after getting a no-senders notification - client is gone
default	19:38:15.564254-0700	backupd	[0x135eaaee0] invalidated after getting a no-senders notification - client is gone
default	19:38:15.565289-0700	backupd	[0x135e989c0] invalidated after getting a no-senders notification - client is gone
default	19:38:15.565383-0700	backupd	[0x135f77ce0] invalidated after getting a no-senders notification - client is gone
default	19:38:15.696481-0700	distnoted	register name: com.apple.backup.prefschanged object: com.apple.backupd token: fa000000b7 pid: 563
default	19:38:16.025173-0700	backupd	keychain blob version does not support integrity
default	19:38:16.206166-0700	backupd	-[DICreateParams createDiskImageParamsWithError:]: entry with <private>
default	19:38:16.318962-0700	backupd	SparseBundleBackend::write_info_plists: <322> Updating Info.bckup, disk size: 0
default	19:38:16.685297-0700	backupd	SparseBundleBackend::write_primary_info_plist: <304> Updating Info.plist
default	19:38:17.312078-0700	backupd	-[DIBaseXPCHandler createConnection]: Creating connection with com.apple.diskimagescontroller
default	19:38:17.312187-0700	backupd	[0x135e16b50] activating connection: mach=false listener=false peer=false name=com.apple.diskimagescontroller
default	19:38:17.880223-0700	backupd	SparseBundleBackend::SparseBundleBackend: <93> Mode for new files in bundle: 664
default	19:38:17.906671-0700	backupd	[0x135e16b50] invalidated on xpc_connection_cancel()
default	19:38:17.909643-0700	backupd	DiskImageSparseBundle::DiskImageSparseBundle: <46> Initialized bands array of size 64
default	19:38:17.910875-0700	backupd	SparseBundleBackend::get_existing_bands: <437> Looking for existing bands
default	19:38:17.979022-0700	backupd	SparseBundleBackend::get_existing_bands: <446> Found 0 existing bands
default	19:38:17.979289-0700	backupd	SparseBundleBackend::write_info_plists: <322> Updating Info.bckup, disk size: 16000000000000
default	19:38:18.365968-0700	backupd	SparseBundleBackend::write_primary_info_plist: <304> Updating Info.plist
default	19:38:18.685194-0700	backupd	-[DICreateParams resizeWithNumBlocks:error:]: Disk image resized to 16000000000000 bytes
default	19:38:18.685446-0700	backupd	SparseBundleBackend::write_info_plists: <322> Updating Info.bckup, disk size: 16000000000000
default	19:38:18.956207-0700	backupd	SparseBundleBackend::write_primary_info_plist: <304> Updating Info.plist
default	19:38:19.555655-0700	backupd	DiskImageSparseBundle::~DiskImageSparseBundle: <246> Closing bands
default	19:38:19.753288-0700	backupd	+[BackendXPC newFileBackendWithURL:fileOpenFlags:error:]: Image file stat: dev(0x3600001a), inode(-7740288681637848958), mode(40775), uid(0), gid(0), size(16384), blocks(32)
default	19:38:19.762594-0700	backupd	+[DiskImageParamsXPC newWithURL:fileOpenFlags:error:]: Image file <private> opened with flags 0
default	19:38:19.787096-0700	backupd	-[DIAttachParams newAttachWithError:]: entry: DIAttachParams[DiskImageParamsLocked_XPC[SparseBundleBackendXPC]]
default	19:38:19.787547-0700	backupd	-[DIBaseXPCHandler createConnection]: Creating connection with com.apple.diskimagescontroller
default	19:38:19.787770-0700	backupd	[0x135fec070] activating connection: mach=false listener=false peer=false name=com.apple.diskimagescontroller
default	19:38:19.791054-0700	backupd	+[DIEncryptionFrontend hasGUIaccess]: User session flags: 0x1 (0x1=root, 0x10=graphics, 0x20=hasTTY, 0x1000=IsRemote), secRes=0
default	19:38:19.931834-0700	backupd	-[DIAttachParams reOpenIfWritableWithError:]: isWritableFormat: YES
default	19:38:19.931924-0700	backupd	+[BackendXPC newFileBackendWithURL:fileOpenFlags:error:]: Image file stat: dev(0x3600001a), inode(-7740288681637848958), mode(40775), uid(0), gid(0), size(16384), blocks(32)
default	19:38:19.932107-0700	backupd	-[DIAttachParams reOpenIfWritableWithError:]: Image file <private> re-opened with RW permissions
default	19:38:19.932264-0700	backupd	-[DIStatFS initWithFileDescriptor:error:]: File system is smbfs
default	19:38:19.932451-0700	backupd	-[DIStatFS logWithHeader:]: Input underlying FS: mounted on <private>, 1024 bytes block size, remote mount
default	19:38:20.479228-0700	backupd	-[DIController2ClientDelegate attachCompletedWithHandle:reply:]: Received: DIDeviceHandle[disk12, unmanaged]
default	19:38:20.896728-0700	backupd	[0x135fec070] invalidated on xpc_connection_cancel()
default	19:38:20.921308-0700	backupd	[0x135fd4690] activating connection: mach=true listener=false peer=false name=com.apple.storagekitd.dm
default	19:38:22.456006-0700	backupd	DMLocalizedUserErrorString DMErr=-69879 request for localized end-user error string; CODE: -69879 TECH/UNLOC: Couldn't open disk USER/LOC: Couldn’t open disk.
default	19:38:22.456103-0700	backupd	DMUnlocalizedTechnicalErrorString DMErr=-69879 request for un-localized tech error string; CODE: -69879 STR: Couldn't open disk
error	19:38:22.456358-0700	backupd	Erase failed for disk <DADisk 0x135e37150 [0x1e1897720]>{id = /dev/disk12}, error: Error Domain=com.apple.diskmanagement Code=-69879 "Couldn't open disk" UserInfo={NSDebugDescription=Couldn't open disk, NSLocalizedDescription=Couldn’t open disk.}, dictionary: {
    Dissenter = 0;
    DissenterPID = "-1";
    Error = "-69879";
    MadeBootable = 0;
}
default	19:38:22.911554-0700	TimeMachineSettings	[0x10d609300] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:22.986912-0700	backupd	[0x135e401f0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135e401f0
default	19:38:22.997432-0700	backupd	[0x135fd4690] invalidated on xpc_connection_cancel()
default	19:38:23.170274-0700	backupd	[0x135e401f0] invalidated after getting a no-senders notification - client is gone
default	19:38:23.488440-0700	backupd	[0x135e401f0] activating connection: mach=true listener=false peer=false name=com.apple.storagekitd.dm

 

[jackieyang9]

1 hour ago, jackieyang9 said:

Thanks for the response. Running with custom eth0 does seem better. At least I can connect to the drive. However, I'm getting "The backup disk image could not be created." when backing up on my Mac.

I checked log in my console and here are the log around that time filtered by "backup":

 

default	19:38:15.537085-0700	TimeMachineSettings	[0x10d60ac20] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.537085-0700	SystemUIServer	[0x11e60c610] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.537216-0700	SystemUIServer	[0x11e706ca0] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.537431-0700	SystemUIServer	[0x11e70c900] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:15.542511-0700	backupd	[0x135fbd820] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135fbd820
default	19:38:15.543309-0700	backupd	[0x135f77ce0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135f77ce0
default	19:38:15.544008-0700	backupd	[0x135eaaee0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135eaaee0
default	19:38:15.545370-0700	backupd	[0x135e989c0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135e989c0
default	19:38:15.560856-0700	backupd	[0x135fbd820] invalidated after getting a no-senders notification - client is gone
default	19:38:15.564254-0700	backupd	[0x135eaaee0] invalidated after getting a no-senders notification - client is gone
default	19:38:15.565289-0700	backupd	[0x135e989c0] invalidated after getting a no-senders notification - client is gone
default	19:38:15.565383-0700	backupd	[0x135f77ce0] invalidated after getting a no-senders notification - client is gone
default	19:38:15.696481-0700	distnoted	register name: com.apple.backup.prefschanged object: com.apple.backupd token: fa000000b7 pid: 563
default	19:38:16.025173-0700	backupd	keychain blob version does not support integrity
default	19:38:16.206166-0700	backupd	-[DICreateParams createDiskImageParamsWithError:]: entry with <private>
default	19:38:16.318962-0700	backupd	SparseBundleBackend::write_info_plists: <322> Updating Info.bckup, disk size: 0
default	19:38:16.685297-0700	backupd	SparseBundleBackend::write_primary_info_plist: <304> Updating Info.plist
default	19:38:17.312078-0700	backupd	-[DIBaseXPCHandler createConnection]: Creating connection with com.apple.diskimagescontroller
default	19:38:17.312187-0700	backupd	[0x135e16b50] activating connection: mach=false listener=false peer=false name=com.apple.diskimagescontroller
default	19:38:17.880223-0700	backupd	SparseBundleBackend::SparseBundleBackend: <93> Mode for new files in bundle: 664
default	19:38:17.906671-0700	backupd	[0x135e16b50] invalidated on xpc_connection_cancel()
default	19:38:17.909643-0700	backupd	DiskImageSparseBundle::DiskImageSparseBundle: <46> Initialized bands array of size 64
default	19:38:17.910875-0700	backupd	SparseBundleBackend::get_existing_bands: <437> Looking for existing bands
default	19:38:17.979022-0700	backupd	SparseBundleBackend::get_existing_bands: <446> Found 0 existing bands
default	19:38:17.979289-0700	backupd	SparseBundleBackend::write_info_plists: <322> Updating Info.bckup, disk size: 16000000000000
default	19:38:18.365968-0700	backupd	SparseBundleBackend::write_primary_info_plist: <304> Updating Info.plist
default	19:38:18.685194-0700	backupd	-[DICreateParams resizeWithNumBlocks:error:]: Disk image resized to 16000000000000 bytes
default	19:38:18.685446-0700	backupd	SparseBundleBackend::write_info_plists: <322> Updating Info.bckup, disk size: 16000000000000
default	19:38:18.956207-0700	backupd	SparseBundleBackend::write_primary_info_plist: <304> Updating Info.plist
default	19:38:19.555655-0700	backupd	DiskImageSparseBundle::~DiskImageSparseBundle: <246> Closing bands
default	19:38:19.753288-0700	backupd	+[BackendXPC newFileBackendWithURL:fileOpenFlags:error:]: Image file stat: dev(0x3600001a), inode(-7740288681637848958), mode(40775), uid(0), gid(0), size(16384), blocks(32)
default	19:38:19.762594-0700	backupd	+[DiskImageParamsXPC newWithURL:fileOpenFlags:error:]: Image file <private> opened with flags 0
default	19:38:19.787096-0700	backupd	-[DIAttachParams newAttachWithError:]: entry: DIAttachParams[DiskImageParamsLocked_XPC[SparseBundleBackendXPC]]
default	19:38:19.787547-0700	backupd	-[DIBaseXPCHandler createConnection]: Creating connection with com.apple.diskimagescontroller
default	19:38:19.787770-0700	backupd	[0x135fec070] activating connection: mach=false listener=false peer=false name=com.apple.diskimagescontroller
default	19:38:19.791054-0700	backupd	+[DIEncryptionFrontend hasGUIaccess]: User session flags: 0x1 (0x1=root, 0x10=graphics, 0x20=hasTTY, 0x1000=IsRemote), secRes=0
default	19:38:19.931834-0700	backupd	-[DIAttachParams reOpenIfWritableWithError:]: isWritableFormat: YES
default	19:38:19.931924-0700	backupd	+[BackendXPC newFileBackendWithURL:fileOpenFlags:error:]: Image file stat: dev(0x3600001a), inode(-7740288681637848958), mode(40775), uid(0), gid(0), size(16384), blocks(32)
default	19:38:19.932107-0700	backupd	-[DIAttachParams reOpenIfWritableWithError:]: Image file <private> re-opened with RW permissions
default	19:38:19.932264-0700	backupd	-[DIStatFS initWithFileDescriptor:error:]: File system is smbfs
default	19:38:19.932451-0700	backupd	-[DIStatFS logWithHeader:]: Input underlying FS: mounted on <private>, 1024 bytes block size, remote mount
default	19:38:20.479228-0700	backupd	-[DIController2ClientDelegate attachCompletedWithHandle:reply:]: Received: DIDeviceHandle[disk12, unmanaged]
default	19:38:20.896728-0700	backupd	[0x135fec070] invalidated on xpc_connection_cancel()
default	19:38:20.921308-0700	backupd	[0x135fd4690] activating connection: mach=true listener=false peer=false name=com.apple.storagekitd.dm
default	19:38:22.456006-0700	backupd	DMLocalizedUserErrorString DMErr=-69879 request for localized end-user error string; CODE: -69879 TECH/UNLOC: Couldn't open disk USER/LOC: Couldn’t open disk.
default	19:38:22.456103-0700	backupd	DMUnlocalizedTechnicalErrorString DMErr=-69879 request for un-localized tech error string; CODE: -69879 STR: Couldn't open disk
error	19:38:22.456358-0700	backupd	Erase failed for disk <DADisk 0x135e37150 [0x1e1897720]>{id = /dev/disk12}, error: Error Domain=com.apple.diskmanagement Code=-69879 "Couldn't open disk" UserInfo={NSDebugDescription=Couldn't open disk, NSLocalizedDescription=Couldn’t open disk.}, dictionary: {
    Dissenter = 0;
    DissenterPID = "-1";
    Error = "-69879";
    MadeBootable = 0;
}
default	19:38:22.911554-0700	TimeMachineSettings	[0x10d609300] activating connection: mach=true listener=false peer=false name=com.apple.backupd.session.xpc
default	19:38:22.986912-0700	backupd	[0x135e401f0] activating connection: mach=false listener=false peer=true name=com.apple.backupd.session.xpc.peer.0x135e401f0
default	19:38:22.997432-0700	backupd	[0x135fd4690] invalidated on xpc_connection_cancel()
default	19:38:23.170274-0700	backupd	[0x135e401f0] invalidated after getting a no-senders notification - client is gone
default	19:38:23.488440-0700	backupd	[0x135e401f0] activating connection: mach=true listener=false peer=false name=com.apple.storagekitd.dm

 

never mind. it worked after a few tries automatically. super weird.

[Nackophilz]

Hi there! 

First of all, thank you for this very useful container!! 

I was wondering, does anyone manage to make a remote backup? On my mac I have TailScale to connect to my server, but as soon as I'm off the local wifi, it can't find the timemachine disk

 

[defected07]

I have not been able to consistently get Time Machine on unRAID to work. I'm on a M1 MBP, and I've tried Time Machine via Samba Share and via the Docker container. Time Machine on the Mac will either not recognize the volume on unRAID, or it mounts it, and just spins, attempting to create a backup, and then fails. Is there a vanilla Docker config I can try that seems to work for most people? I know there are a few specified in the README, and I'm wondering if it's a problem with my Network configuration. Should I provide a dump of my unRAID settings for review?

 

EDIT: Of course, as soon as I make a post about my failures, I went back through the thread, and tried some different things -- like the Custom 'br0' bridge connection, and changing 'WORKGROUP' to 'TM-WORKGROUP' to separate it from unRAID's Samba 'WORKGROUP', and setting a static IP. Seems to be writing to the TM volume now.

 

However, a few things are weird.

 

Successful TM Endpoint

Failed TM Endpoint:

 

Anyway to get it to not randomly generate a name like in the screenshot? CAFE6D6707F6, etc.?
I was hoping to use 'timemachine-smb', which is what Advertised Hostname is set to. Is that not correct? I'm not able to 'Connect As' for that endpoint, it just eventually times out with this error:

 

Here's the container's logs from startup:
 

chpasswd: password for 'timemachine' changed
dbus-daemon[41]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.8 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Loading service file /etc/avahi/services/smbd.service.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.125.
New relevant interface eth0.IPv4 for mDNS.
Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
New relevant interface lo.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for 192.168.0.125 on eth0.IPv4.
Registering new address record for 127.0.0.1 on lo.IPv4.
Server startup complete. Host name is cafe6d67d7f6.local. Local service cookie is 152858969.
Service "timemachine-smb" (/etc/avahi/services/smbd.service) successfully established.
INFO: CUSTOM_SMB_CONF=false; generating [global] section of /etc/samba/smb.conf...
INFO: Creating /var/log/samba/cores
INFO: Avahi - generating base configuration in /etc/avahi/services/smbd.service...
INFO: Avahi - using timemachine-smb as hostname.
INFO: Avahi - adding the 'dk0', 'TimeMachine' share txt-record to /etc/avahi/services/smbd.service...
INFO: Group timemachine doesn't exist; creating...
INFO: User timemachine doesn't exist; creating...
INFO: Using default password: timemachine
INFO: INFO: CUSTOM_SMB_CONF=false; generating [TimeMachine] section of /etc/samba/smb.conf...
INFO: Samba - Created Added user timemachine.
INFO: Samba - Enabled user timemachine.
INFO: Samba - setting password
INFO: SET_PERMISSIONS=false; not setting ownership and permissions for /opt/timemachine
INFO: Avahi - completing the configuration in /etc/avahi/services/smbd.service...
INFO: running test for xattr support on your time machine persistent storage location...
INFO: xattr test successful - your persistent data store supports xattrs
INFO: Detected filesystem for /opt/timemachine is fuse.shfs
INFO: entrypoint complete; executing 's6-svscan /etc/s6'
dbus socket not yet available; sleeping...
nmbd version 4.18.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd version 4.18.5 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
INFO: Profiling support unavailable in this build.
*****

Samba name server CAFE6D67D7F6 is now a local master browser for workgroup TM-WORKGROUP on subnet 192.168.0.125

*****
fruit_get_bandsize: Didn't find band-size key in [/opt/timemachine/5AB96E66-72A7-5AF2-8CD9-9CED472FCD81_2023-10-06-102340.sparsebundle/Info.plist]
fruit_tmsize_do_dirent: Processing sparsebundle [5AB96E66-72A7-5AF2-8CD9-9CED472FCD81_2023-10-06-102340.sparsebundle] failed

 

 

Edited October 6, 2023 by defected07
Successes, and questions.

[wgstarks]

What happened when you tried it via this docker container?

[defected07]

6 minutes ago, wgstarks said:

What happened when you tried it via this docker container?

Sorry, see my update to the post. Seems I was able to get it to mostly work, just not entirely to my expectations.

[wgstarks]

15 minutes ago, defected07 said:

Sorry, see my update to the post. Seems I was able to get it to mostly work, just not entirely to my expectations.

I think I would have tried the default settings first but if this is working then might as well leave it alone.

[wgstarks]

1 hour ago, defected07 said:

I was hoping to use 'timemachine-smb', which is what Advertised Hostname is set to. Is that not correct? I'm not able to 'Connect As' for that endpoint, it just eventually times out with this error:

You should see TIMEMACHINE.local advertised. I asked a similar question when I first setup this docker but don’t think I ever got an answer. I know it’s TIMEMACHINE.local on my system even though the Advertised Hostname is timemachine-smb.

Edited October 6, 2023 by wgstarks

[defected07]

45 minutes ago, wgstarks said:

I think I would have tried the default settings first but if this is working then might as well leave it alone.

  

Do you mean the default settings that come with the Docker installation? Or one of the `docker run` templates found in the repo's README for Samba or Avahi?

 

What was your configuration?

 

36 minutes ago, wgstarks said:

You should see TIMEMACHINE.local advertised. I asked a similar question when I first setup this docker but don’t think I ever got an answer. I know it’s TIMEMACHINE.local on my system even though the Advertised Hostname is timemachine-smb.

 

Did you input TIMEMACHINE.local anywhere, or did it just magically appear ?

 

Here's my Container settings:

 

Edited October 6, 2023 by defected07
Smaller screenshot

[wgstarks]

16 minutes ago, defected07 said:

Do you mean the default settings that come with the Docker installation?

Yes

 

17 minutes ago, defected07 said:

Did you input TIMEMACHINE.local anywhere, or did it just magically appear ?

It’s been several years but IIRC it just showed up as a share on the network.

 

If your settings are working then maybe just leave them.

[defected07]

2 hours ago, wgstarks said:

Yes

 

It’s been several years but IIRC it just showed up as a share on the network.

 

If your settings are working then maybe just leave them.

Ah I think I figured it out. If you toggle the switch at the top right for 'Advanced View', then you can specify the hostname of the container:


 

And I left "ADVERTISED_HOSTNAME" blank. But then I believe you lose Avahi broadcasting on the host, so I had to manually connect to my unRAID array -- it didn't show up under Network or on the left panel in Finder.

[wgstarks]

36 minutes ago, defected07 said:

Ah I think I figured it out. If you toggle the switch at the top right for 'Advanced View', then you can specify the hostname of the container:


 

And I left "ADVERTISED_HOSTNAME" blank. But then I believe you lose Avahi broadcasting on the host, so I had to manually connect to my unRAID array -- it didn't show up under Network or on the left panel in Finder.

Did you also reset the workgroup to default?

[defected07]

On 10/6/2023 at 3:36 PM, wgstarks said:

Did you also reset the workgroup to default?

Sorry for the late, late response, but yes, SMB Workgroup is back to "WORKGROUP"

 

I set `extra parameters` to `--hostname timemachine` -- and that's how it appears in Finder. 

 

I used `Custom: br0 -- Main Network`, set a fixed IP address, not sure what else, and I dont' remember how I came to this conclusion, think I took some pieces from one config and some from another from this plug-in's GitHub README

[wgstarks]

4 minutes ago, defected07 said:

Sorry for the late, late response, but yes, SMB Workgroup is back to "WORKGROUP"

 

I set `extra parameters` to `--hostname timemachine` -- and that's how it appears in Finder. 

 

I used `Custom: br0 -- Main Network`, set a fixed IP address, not sure what else, and I dont' remember how I came to this conclusion, think I took some pieces from one config and some from another from this plug-in's GitHub README

I think your best bet would be to start over with just the default configuration described in the first post in this thread.

[daNick73]

Hi

The docker container always "used to work" (TM), but after it failed, I reinstalled the container and now I am in a mess.

 

I know it says "network needs to be configured, but I have forgotten how...

I cannot see the timemachine in my network, Timemachine app on Macos (sonoma 14.1.2) doesnt find it.

 

My network uses 192.168.178.x / unraid is 192.168.178.31.

 

From default I only changed network from "none" to "bridge"

 

My command reads 

 

docker run
  -d
  --name='TimeMachine'
  --net='bridge'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="TimeMachine"
  -e 'VOLUME_SIZE_LIMIT'='2 T'
  -e 'TM_USERNAME'='timemachine'
  -e 'PASSWORD'='Z92efVNcokU26x'
  -e 'ADVERTISED_HOSTNAME'='timemachine'
  -e 'CUSTOM_SMB_CONF'='false'
  -e 'CUSTOM_USER'='false'
  -e 'DEBUG_LEVEL'='1'
  -e 'MIMIC_MODEL'='TimeCapsule8,119'
  -e 'EXTERNAL_CONF'=''
  -e 'HIDE_SHARES'='no'
  -e 'TM_GROUPNAME'='timemachine'
  -e 'TM_UID'='1000'
  -e 'SET_PERMISSIONS'='false'
  -e 'SMB_INHERIT_PERMISSIONS'='no'
  -e 'SMB_NFS_ACES'='yes'
  -e 'SMB_METADATA'='stream'
  -e 'SMB_PORT'='445'
  -e 'SMB_VFS_OBJECTS'='acl_xattr fruit streams_xattr'
  -e 'WORKGROUP'='WORKGROUP'
  -e 'TM_GID'='1000'
  -e 'SHARE_NAME'='TimeMachine'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://upload.wikimedia.org/wikipedia/de/f/f4/Time_Machine_%28Apple%29_Logo.png'
  -v '/mnt/user/timemachine/':'/opt/timemachine':'rw'
  --hostname timemachine 'mbentley/timemachine'
a86dcc58cadc4e78ff3433827187c065d099371c1973581e11075563d45873ce

The command finished successfully!

 

My Log reads

 

chpasswd: password for 'timemachine' changed
dbus-daemon[42]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.8 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Loading service file /etc/avahi/services/smbd.service.
Joining mDNS multicast group on interface eth0.IPv4 with address 172.17.0.12.
New relevant interface eth0.IPv4 for mDNS.
Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
New relevant interface lo.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for 172.17.0.12 on eth0.IPv4.
Registering new address record for 127.0.0.1 on lo.IPv4.
Server startup complete. Host name is timemachine.local. Local service cookie is 1058824436.
Service "timemachine" (/etc/avahi/services/smbd.service) successfully established.
INFO: CUSTOM_SMB_CONF=false; generating [global] section of /etc/samba/smb.conf...
INFO: Creating /var/log/samba/cores
INFO: Avahi - generating base configuration in /etc/avahi/services/smbd.service...
INFO: Avahi - using timemachine as hostname.
INFO: Avahi - adding the 'dk0', 'TimeMachine' share txt-record to /etc/avahi/services/smbd.service...
INFO: Group timemachine doesn't exist; creating...
INFO: User timemachine doesn't exist; creating...
INFO: Setting password from environment variable
INFO: INFO: CUSTOM_SMB_CONF=false; generating [TimeMachine] section of /etc/samba/smb.conf...
INFO: Samba - Created Added user timemachine.
INFO: Samba - Enabled user timemachine.
INFO: Samba - setting password
INFO: SET_PERMISSIONS=false; not setting ownership and permissions for /opt/timemachine
INFO: Avahi - completing the configuration in /etc/avahi/services/smbd.service...
INFO: running test for xattr support on your time machine persistent storage location...
INFO: xattr test successful - your persistent data store supports xattrs
INFO: Detected filesystem for /opt/timemachine is fuse.shfs
INFO: entrypoint complete; executing 's6-svscan /etc/s6'
dbus socket not yet available; sleeping...
nmbd version 4.18.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
smbd version 4.18.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
INFO: Profiling support unavailable in this build.
*****

Samba name server TIMEMACHINE is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.12

*****

 

Any support truly appreciated

Edited December 10, 2023 by daNick73

[ScottAS2]

On 12/10/2023 at 1:46 PM, daNick73 said:

From default I only changed network from "none" to "bridge"

 

I believe this is the mistake. You should select the "custom" network that can be created in Unraid's Docker settings. This will allow the Time Machine container to have its own IP in and exchange multicast DNS/DNS Service Discovery messages with devices on your 192.168.178.0/24 network.

 

The "bridge" network will put Docker containers in a 172.17.0.0/16 (by default) internal network that you can think of as NAT-ed behind your Unraid server's IP. In most cases, this is fine and you just forward the appropriate ports through that NAT to a container*, but the mDNS and DNS-SD messages needed for clients to discover and communicate with the Time Machine service won't cross from one network to the other. Even if they did, the Time Machine container on a "bridge" network only knows its 172.17.0.0/16 address, which is no use to the machines on 192.168.178.0/24 that are looking to back up.

 

* In theory, you might be able to set Time Machine up like this - it's "just" an SMB server - but it would be more work to set up the clients and Time Machine is notoriously picky; without the multicast stuff it might decline to accept the server.

Edited January 17 by ScottAS2

[mjeshurun]

37 minutes ago, ScottAS2 said:

 

I believe this is the mistake. You should select the "custom" network that can be created in Unraid's Docker settings.

 

I can confirm this solution. Yesterday I wanted to create a time machine backup, but when I tried to use network type: Host or Bridge my mac couldn't find any time machine device.
Only after I switched the network type to custom br0 I was able to find the time machine device in the mac time machine settings.

Edited January 17 by mjeshurun