Crast

I want to add a datapoint for @testdasi - I am -not- having the corruption issue and never did but I use basically all the same containers (plex, sonarr, deluge.) Maybe something different in my config will help isolate what's different. What CPU? How much RAM? Array config? i5-760, P55 motherboard, 8GB ram. Array is 3 drives, all XFS+LUKS encrypted, 8+8+4TB, + 256GB xfs cache. in addition, one 4TB unassigned device used mostly for deluge scratch disk, the partition is btrfs+LUKS encrypted. All five devices connected to motherboard P55 SATA controller. Roughly how large is your collection? I think file count, even a rough estimate, is more important here. movies = 158GB / 288 files tv = 1.7 TB / 8202 files Have you set your appdata to /mnt/cache (or for those without cache, /mnt/disk1)? If you haven't, we'll ignore you. I am using /mnt/user/appdata/<app> for -all- my containers, without corruption issue. I thought about changing it when reading the first four pages but now I won't, because I want to see if I ever do get corrupted. I don't mind rebuilding my library from scratch if it happens. Do you have a link between Sonarr and Plex? If yes, have you disable it? If you haven't, we'll ignore you. No, it's not linked. I wanted to, I couldn't get it to auth properly. Sonarr is linked to Deluge though. Do you have automatic library update on change / partial change? If yes, have you set it to hourly? If you haven't we'll ignore you. No, I manually update to avoid spinning disks up needlessly. ---- I repeat, I do not have the issue, I just wanted to put my info in so maybe we could see if there was any significant difference between my config and other people's configs.

No probs, actually I have had a lot of experience with using and recovering time machine even before using unraid, using airport extremes and time capsules as well. I just translated some of the same tricks. Time Machine is very slow at handling lots of super-tiny files, which is unfortunate since OSX uses a lot of super-tiny files. The biggest culprits in my experience are your Mail folder if you use Apple Mail, but also your /Applications folder, as each app contains resources for every supported language, over a hundred languages * at least four resources in the case of Apple's own apps. Apple Mail aside, your Applications folder doesn't change nearly as often, so after the initial backup, your backups should go much faster. Other commonly changing files like Caches you should exclude (see the second half of my previous post)

Something to add, from my own personal experience, which may help those of you who had issues locating the share. Mac OS, when you browse your time machine share, will not normally authenticate, if your share is browseable. So a way to force it to do it with a username is to connect to it via the "connect to server" window. Open Finder (any finder window is fine) use CMD+K hotkey (CMD is also known as apple key) to open the connect dialogue. Type in smb://yourusername@yourserver/sharename Example: smb://[email protected]/timemachine It is worth noting that OSX being a Unix-based OS does weird things with spaces in names, so I would recommend making your share name not have spaces in it, just to be safe. After telling it to connect, you will then be prompted for the password that goes along with that username. You may want to tell MacOS to add that password to your keychain. Make sure the share is writeable with that user; drag a random small file into the time machine share window. (This was one of my mistakes, my new user though configured to write was not able to). You can delete that file after, it's just a validation. Now, you should be able to open up the Time Machine preference pane and your share will be visible as a backup source. ---- For those of you who got the share to recognize, but struggling to get your first backup to complete, consider excluding as many folders as you can avoid backing up, especially things you don't normally need to back up. Open the Time Machine Preference pane, go to Options, and you can add folders to exclude. (n.b. Many folders may not be browse-able, but you can do a trick, open a finder window and then use CMD+shift+G to open a finder window to a given special or hidden folder, then drag the tiny folder icon from the top of that window into the exclude list.) Here's some of the ones I exclude: /var/vm (contains your hibernation file and swap file) ~/Downloads ~/Library/Caches ~/Library/Containers/com.docker.docker (if you use Docker for Mac) ~/Library/Mail (if you use Mail app, exclude this initially as it has hundreds of thousands of small files) I would also recommend for your first backup, if they are -still- failing, to exclude anything else you can easily exclude. Your music library, photo library, etc, anything with a large data size, just to get that first backup to succeed. You can then remove the excludes on those later, and those files will be added to subsequent backups.