June 4, 20224 yr @wgstarks thanks for the write up!Just for my understanding, these steps are only needed if you want each Mac/user to have its own independent backup share, right?If I’m happy for all users to see each others backup I could just let them share the one user/password/share combo?Sent from my iPhone using Tapatalk
June 4, 20224 yr 7 hours ago, Jorgen said: @wgstarks thanks for the write up! Just for my understanding, these steps are only needed if you want each Mac/user to have its own independent backup share, right? If I’m happy for all users to see each others backup I could just let them share the one user/password/share combo? Sent from my iPhone using Tapatalk Yes. Or you could encrypt the backups and only someone with the proper password could access them. The main reason I wanted to use multiple users was that I have one machine that gets used most of the time and has a lot of data being backed up. It would possibly hog all the space on the backup destination. With multiple users each machine has its own space.
June 8, 20224 yr I cannot figure out what I'm doing wrong... I leave everything default (so the container creates the share required) and run the chown command, but timemachine still is writing to the docker image. I believe I've read everything in these two pages but haven't found anything I'm forgetting to do.
June 8, 20224 yr 4 minutes ago, joshbgosh10592 said: I cannot figure out what I'm doing wrong... I leave everything default (so the container creates the share required) and run the chown command, but timemachine still is writing to the docker image. I believe I've read everything in these two pages but haven't found anything I'm forgetting to do. This usually means you’ve got a path configured wrong. Did you use the default user? If you changed it you must also change the container path for the backup location. If that’s not it post your docker run command in your next post. Be sure to redact passwords.
June 15, 20224 yr My Unraid box updated to 6.10.3. Now I am unable to connect to the "time machine" that was working yesterday... I have kept all of the basic settings I even reissued the chown command on the directory that i am using (/mnt/user/timemachine) but I am not able to find the time machine on my mac now. Like others have stated I didn't get it to work in the beginning either. I had to keep messing with it for my mac to discover it. Unfortunately, I didn't keep track of the changes I made that finally got it to show up. I can't mount the smb path to it either. I think it was done by IP in the past (based on the time machine backup app saying it couldn't find it). but I've also tried timemachine.local, timemachine, ip/timemachine.local, ip/timemachine, etc. nothing seems to be working for me. Any thoughts?
June 22, 20224 yr I'm not lucky too. I tried this docker because my MacMini stopped "finding" my native unraid TM share. First I set up a share - see first screenshot - honestly 100% like @moritzf After that I installed the docker and left everything as default. See second screenshot. Than I run the command as adviced: sudo chown -R 1000:1000 /mnt/user/timemachine/ Due to the fact that I got no error message this should worked Than - to make sure - I just restarted the docker. But the Time Machine preferences still dont find a correct volume do choose for backup. I also attached the docker_run. Hopefully someone can help me out here. Thanks in advance
June 25, 20224 yr On 6/8/2022 at 6:06 PM, wgstarks said: This usually means you’ve got a path configured wrong. Did you use the default user? If you changed it you must also change the container path for the backup location. If that’s not it post your docker run command in your next post. Be sure to redact passwords. Yup, that was my problem... I was trying to change the username and thought that was all I'd need, thank you! However... I had very high hopes of this! Setting up TM was super simple. However, I still cannot get it to sync after the first time.. I don't understand why it's throwing "Operation not supported by device"... 2022-06-25 01:02:02 Running for notifyd event com.apple.system.powersources.source 2022-06-25 01:02:32 TMPowerState: 2 2022-06-25 01:02:32 Not prioritizing backups with priority errors. lockState=0 2022-06-25 01:02:32 Starting automatic backup 2022-06-25 01:02:32 Attempting to mount 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' 2022-06-25 01:02:34 Mounted 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' at '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine' (212.63 GB of 536.87 GB available) 2022-06-25 01:02:34 Initial network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C} 2022-06-25 01:02:34 Configured network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 1, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C} 2022-06-25 01:02:35 Skipping periodic backup verification: not needed for an APFS sparsebundle 2022-06-25 01:02:36 'MacBook Pro.sparsebundle' does not need resizing - current logical size is 510.03 GB (510,027,366,400 bytes), size limit is 510.03 GB (510,027,366,400 bytes) 2022-06-25 01:02:36 Mountpoint '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine' is still valid 2022-06-25 01:02:36 Checking for runtime corruption on '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F3869E31C2/TimeMachine/MacBook Pro.sparsebundle' 2022-06-25 01:03:15 Failed to attach using DiskImages2 to url '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine/MacBook Pro.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} 2022-06-25 01:03:15 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine/"; 2022-06-25 01:03:15 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-25 01:03:15 Waiting 60 seconds and trying again. 2022-06-25 01:03:15 Cancelling backup because volume '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine' was unmounted. 2022-06-25 01:03:15 Requested backup cancellation or termination 2022-06-25 01:03:16 Backup cancelled (22: BACKUP_CANCELED) 2022-06-25 01:03:16 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine/"; 2022-06-25 01:03:16 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-25 01:03:16 Cleared pending cancellation request Edited June 25, 20224 yr by joshbgosh10592
June 25, 20224 yr On my primary max I re-installed macOS to fix issues with TM backups but I noticed on one of the other machines that I had configured that the backups failed at first but just started working after several hours. You might just try waiting a bit.
June 25, 20224 yr 6 hours ago, wgstarks said: On my primary max I re-installed macOS to fix issues with TM backups but I noticed on one of the other machines that I had configured that the backups failed at first but just started working after several hours. You might just try waiting a bit. I figured I'd give it some time, but the initial backup was June 14th and multiple times a day, I've tried to kick off a manual backup to no avail..
June 25, 20224 yr Have you also tried reinstalling macOS? That’s what fixed the problem on my primary desktop (an M1 mini).
June 26, 20224 yr 6 hours ago, wgstarks said: Have you also tried reinstalling macOS? That’s what fixed the problem on my primary desktop (an M1 mini). I have not, but actually, I'd rather not have time machine working than reinstall macOS and have to set everything up again lol
June 26, 20224 yr 26 minutes ago, joshbgosh10592 said: I have not, but actually, I'd rather not have time machine working than reinstall macOS and have to set everything up again lol You shouldn’t need to set anything up again. It’s really the same process as updating the OS. Just re-installs the entire OS rather than just the latest update. Same as the combo installs used to be. You shouldn’t see anything changed after the process is complete.
June 28, 20224 yr On 6/25/2022 at 9:05 PM, wgstarks said: You shouldn’t need to set anything up again. It’s really the same process as updating the OS. Just re-installs the entire OS rather than just the latest update. Same as the combo installs used to be. You shouldn’t see anything changed after the process is complete. Can you please elaborate a little? Do you simply boot into install mode and go through the normal install process?
June 28, 20224 yr 38 minutes ago, dereitz said: Can you please elaborate a little? Do you simply boot into install mode and go through the normal install process? I think this will help you- https://support.apple.com/en-us/HT204904
June 28, 20224 yr It’s fairly straight forward took about 20 minutes for me. Might be a little longer if you’re on wifi.
June 29, 20224 yr On 6/25/2022 at 9:05 PM, wgstarks said: You shouldn’t need to set anything up again. It’s really the same process as updating the OS. Just re-installs the entire OS rather than just the latest update. Same as the combo installs used to be. You shouldn’t see anything changed after the process is complete. Didn't know that, thank you! I performed that, removed the existing disk from TM, and erased the .sparcebundle and allowed TimeMachine to create a new one and successfully creates the first backup. However, anything after, still the same thing for some reason... This is driving me nuts.. Attempting to mount 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' 2022-06-28 23:16:43 Mounted 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' at '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine' (208.91 GB of 536.87 GB available) 2022-06-28 23:16:43 Initial network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C} 2022-06-28 23:16:44 Configured network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 1, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C} 2022-06-28 23:16:44 Skipping periodic backup verification: not needed for an APFS sparsebundle 2022-06-28 23:16:45 'Josh’s MacBook Pro.sparsebundle' does not need resizing - current logical size is 510.03 GB (510,027,366,400 bytes), size limit is 510.03 GB (510,027,366,400 bytes) 2022-06-28 23:16:45 Mountpoint '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine' is still valid 2022-06-28 23:16:45 Checking for runtime corruption on '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/MacBook Pro.sparsebundle' 2022-06-28 23:17:22 Failed to attach using DiskImages2 to url '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/MacBook Pro.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} 2022-06-28 23:17:22 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/"; 2022-06-28 23:17:22 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-2DDB7F096A54/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-28 23:17:22 Waiting 60 seconds and trying again. 2022-06-28 23:17:22 Cancelling backup because volume '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine' was unmounted. 2022-06-28 23:17:22 Requested backup cancellation or termination 2022-06-28 23:17:23 Backup cancelled (22: BACKUP_CANCELED) 2022-06-28 23:17:23 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/"; 2022-06-28 23:17:23 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-28 23:17:23 Cleared pending cancellation request Edited June 29, 20224 yr by joshbgosh10592
July 28, 20223 yr On 6/4/2022 at 2:11 AM, wgstarks said: 3. Create the user configuration files mentioned above. These files must be named <username>.conf and each must have a unique TM_UID number. m1_mini.conf TM_USERNAME=m1_mini TM_GROUPNAME=timemachine PASSWORD=**************** SHARE_NAME=m1_miniSMB VOLUME_SIZE_LIMIT=”1 T” TM_UID=1001 TM_GID=1000 jasper.conf TM_USERNAME=jasper TM_GROUPNAME=timemachine PASSWORD=****************** SHARE_NAME=jasperSMB VOLUME_SIZE_LIMIT=”1 T” TM_UID=1002 TM_GID=1000 Thank you for the writeup! I still have some questions regarding using multiple users. The way it is described above it looks like the users will be created inside the container. Correct? Do we put the passwords in cleartext into the conf files? The container will transform them into the hash-salted form then when creating the users? Do we also need to create the same user on the unraid host side, using the same UID and GID? If not, do we need to avoid collisions with UID and GID on the unraid host side when choosing values for TM_UID and TM_GID? Do encrypted backups now work for you? Edited July 28, 20223 yr by b0m541
July 28, 20223 yr 2 hours ago, b0m541 said: The way it is described above it looks like the users will be created inside the container. Correct? Do we put the passwords in cleartext into the conf files? The container will transform them into the hash-salted form then when creating the users? Yes to all of these. You create the users when you create the configuration file(s). 2 hours ago, b0m541 said: Do we also need to create the same user on the unraid host side, using the same UID and GID? No. They only exist within the container. 2 hours ago, b0m541 said: If not, do we need to avoid collisions with UID and GID on the unraid host side when choosing values for TM_UID and TM_GID? I haven’t tested this but I suspect that it wouldn’t be necessary. If you want an informed answer you should probably post this question on the GitHub project page linked in the first post. 2 hours ago, b0m541 said: Do encrypted backups now work for you? Yes. All my machines use encrypted backups without any issues.
July 28, 20223 yr INFO: running test for xattr support on your time machine persistent storage location... INFO: xattr test successful - your persistent data store supports xattrs INFO: entrypoint complete; executing 's6-svscan /etc/s6' nmbd version 4.15.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2021 smbd version 4.15.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2021 INFO: Profiling support unavailable in this build. Failed to fetch record! ***** Samba name server TIMEMACHINE is now a local master browser for workgroup WORKGROUP on subnet REDACTED Thank you, I set it up and the SAMBA is running, although some things are weird in the logs: What does this mean?: Failed to fetch record! I can see in your writeup that you put in a full IP address for the container instance, not just a subnet address. And so did I. In the log it says it is running now on subnet... and there is the IP of the timemachine instance, not the subnet address (i.e. the host octett is not all zero). Is that a problem or is the text "subnet" just plain wrong and should say "IP address"? Then after configuring the backup under macOS and starting it, during preparation phase the timemachine container log would say: error in mds_init_ctx for: /opt/mymac _mdssvc_open: Couldn't create policy handle for mymac Is that a problem? Ideas how to fix it? current status: Timemachine full backup is running on the mac and it will take many hours to complete. So If all this currently works I will be able to say tomorrow when the full backup hopefully has completed and I was able to see whether incremental backups do work. Edited July 28, 20223 yr by b0m541
July 28, 20223 yr I’m not an expert on TimeMachine under the hood. I would suggest posting those questions on the GitHub page.
July 28, 20223 yr 1 hour ago, wgstarks said: I’m not an expert on TimeMachine under the hood. I would suggest posting those questions on the GitHub page. I see. Have you seen these in your logs before? I see like 50-60 of them currently: scavenger_timer: Failed to cleanup share modes and byte range locks for file 56:18303754804867892465:0 open 2233142994
July 28, 20223 yr 2 hours ago, wgstarks said: No. Is that from the docker log? yes. and now two of this: vfs_default_durable_reconnect (mbp15r (1032).backupbundle/bands/28c): stat_ex.st_ex_blocks differs: cookie:65408 != stat:38216, denying durable reconnect and more of the former. it seems the backup stopped and then started anew while I was AFK. Now in preparation phase. doesn't look too good to me.
July 31, 20223 yr Thanks for the fine TimeMachine docker container!! My iMac had not been backed up for a while and now Time Machine is working again! Under "Size Limit" I used 512 GB, which I don't think is being enforced. Probably because my Time Machine backup was close to 900 GB. So is there a way to shrink the size of an existing TM backup? Perhaps deleting the files in reverse chronological order?
August 5, 20223 yr I tried to set this up after reading that it works (and 6.10 does not). I get the following errors: Failed to fetch record! error in mds_init_ctx for: /opt/timemachine _mdssvc_open: Couldn't create policy handle for TimeMachine error in mds_init_ctx for: /opt/timemachine _mdssvc_open: Couldn't create policy handle for TimeMachine talloc: access after free error - first free may be at ../../tevent_req.c:291 Bad talloc magic value - access after free =============================================================== INTERNAL ERROR: Bad talloc magic value - access after free in pid 48 (4.15.7) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting =============================================================== PANIC (pid 48): Bad talloc magic value - access after free in 4.15.7 unable to produce a stack trace on this platform dumping core in /var/log/samba/cores/smbd Does anyone have any advise as to how to resolve? Edited August 5, 20223 yr by 54lzy formatting
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.