wgstarks

Members
  • Posts

    4204
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by wgstarks

  1. Just wanted to point out a newly added docker Time Machine based on a project whose goal is to provide stable Time Machine backups in a constantly changing environment (I'm paraphrasing). I hesitate to recommend it since I just started using it about an hour ago but it was fairly easy to get it installed and working. You might want to check it out.
  2. Got it working I think. I had mounted the backup location on the mac via the IP (10.0.1.21/TimeMachineSMB) and added that location to Time Machine. After my previous post I realized that TIMEMACHINE.local is also listed as an available destination and that one seems to be working although it's only at 1.1% right now. Not sure why its TIMEMACHINE.local though. ADVERTISED_HOSTNAME is set to TimeMachineSMB. Shouldn't it be TimeMachineSMB.local?
  3. Got the docker installed easily enough but Time Machine backups don't complete. run command- Time Machine log from mac- I made 3 or 4 attempts to backup but could only find one entry in the log related to this destination.
  4. Might not be a bad idea to put that info in the original post and/or GitHub. Some users might read it.😁
  5. It's the popup window when you click install.
  6. When attempting to install I see in the instructions that I need to run this command on the share- sudo chown -R񎗨:1000 /mnt/user/timemachine/ I’m guessing that I need to replace /timemachine/ with the actual share I have configured? What is the symbol after -R?
  7. Got it. The unRAID share is only accessed from the docker.
  8. If no users have access to the TM share how do you mount that share on the Mac in order to set Time Machine to use that destination? Edit: maybe mounting the destination first to be able to select it for backups is no longer necessary with mDNS advertising?
  9. Updated without issue. I just have some APs (4) and it took a couple of minutes for them to reconnect.
  10. I run the CA backup. How do I set one up in the app? Unifi has tons of settings but I don’t think I’ve seen one for a backup? Sounds like a great idea though.
  11. Just curious what error TM showed on the failed backup? log show --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999
  12. You need to set multi channel to “off”.
  13. In my case the problem started when I installed macOS 12.3.1 and was resolved by re-installing macOS. This allowed backups to complete and stopped all the kernel panics that had previously required a reboot of macOS. My suspicion is that Apple has made some change to their SMB implementation but since they don’t provide any specific details with their updates it’s hard to say for sure. It’s also possible that not everyone posting here has the same issue since they haven’t provided any logs. Everyone is free to re-open this issue though if you find that you truly do have the same issue (matching errors in the logs) or open a new bug report if you find that your issue is somehow different.
  14. Got this while updating to 6.10.1. Guessing it’s still wrong but posting it as requested.
  15. That error looks similar to mine. In my case it was fixed by re-installing monterey from the recovery menu. Deleting the existing backup and starting a new one. I also deleted all smb extras settings related to macOS in settings>SMB on unraid and set smb multi channel to off.
  16. Here's a slightly different command- log show --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999
  17. What do you have set for SMB and SMB extras?
  18. What error are you getting? Run this command on macOS- printf '\e[3J' && log show --predicate 'subsystem == "com.apple.TimeMachine"' --info --last 6h | grep -F 'eMac' | grep -Fv 'etat' | awk -F']' '{print substr($0,1,19), $NF}' This will show the TM log for the past 6 hours.
  19. I was able to resolve this issue by re-installing macOS 12.4, deleting the existing TM backup and creating a new one. It appears that the problem wasn't related to unRAID.