Glad you like it man!

So TM snapshots I setup as a ransomeware preventative. Having only a couple will take up a very small amount of space

Time Machine will just delete old versions once its out of space, but before that it will keep everything. I don’t think MacOS will tell you

@@SpaceRexWill it does tell you it’s running low on space, also it tells you if it hasn’t backed up to that disk in x days or hours etc.

I am highly considering leaving behind my DS920+. For the second time in 6 months I lose my connection to my Mac and I can't back up. Such a weird thing because I still can connect to the other volumes but not the TM one. Contacting Synology is a headache and they usually can't solve the issue. If you someday can create a video with troubleshooting , that would be awesome. Great channel! @@SpaceRexWill

Those are built into safari! Called pined tabs. Really easy you just drag a tab to the left and it uses it

@@SpaceRexWill great thx for reply. Love to see your videos

ive just updated my mac to sonoma and had to upgrade my CCC too. Currently doing a bit of research on best practices for using ccc on a nas. Just got the DS224+ after using DS212 and hoping to do all my cloning and TM backups straight to the NAS. How's CCC on nas working for you so far? Any gotcha's i should take note of?

It is supported, but as of right now I still recommend Time Machine

You can, but I wouldn’t recommend it. It tends to work better with just one to one because of folder limitations

@@SpaceRexWill The limitations you're referring to are the size limitations you set during the folder creation?

This is why you buy yourself a Layer 3 switch to enable LCAP bonding. The bond will enable to NAS to spread the network load across the 2, 3 or 4 network port you assign to it. Just adding 2 network ports into a bond will halve your congestion. That or/and upgrade to 10GbE. I don't see how Active Backup changes anything other than allowing you to reduce the frequency else throttling the bandwidth use. I'm not a big fan of the latter as throttles only slows the process down and you'll be congested just the same. In newer versions of macOS there is the option to change backup frequency. In older versions you can use Terminal to edit a preference file. A simple web search should give it to you. As for the space errors… most likely its a configuration error at the NAS end where you didn't to the permissions and/or quotas correctly. If you are in fact running out of space there's only one fix for that no matter what software you're using to backup and that is to go with larger storage. You need to be mindful that TM is pretty dumb in a lot of way. The clever use of exclusions goes a long way.

@@IntoxicatedVortex Thank you for your explanation. But it is way too complicated for me. As far as I can tell, Active Business Backup works just fine.

So just to check, that second password is likely the encryption key you setup when making the first Time Machine backup. Without that password you will not be able to decrypt the backup. This was a password you set in MacOS

Thanks so much Will I tried a few of my favourites; but that’s what I was afraid of. Nothing to do with Synology@@SpaceRexWill

The reason why Synology suggests quotas on the user account (I personally do it via quotas set on groups) is because the assumption is that you might have 100 people making backups and you're not going to make 100 shared folders. Nor do you want to be seeing 100 options in TM system preferences when you're trying to select the right destination. If you are setting the quota via the shared folder quota then each user will create a TM backup disk image the size of the shared folder. At some point they'll all run into each other. By doing it via a user you can set each user to have a smaller than the folder size… and you don't have to set the folder size. Its also a lot less management. For instance, the way I do it is to create a single TM shared folder. Then create groups like TM-256G/TM-512G/TM-1T. Each user will be in one of those groups that matches the SSD size of their computer. Each of those groups then gets a 1.5x multiple (or other) TM size set via their group. So users in the TM-256 groups will each get a 768GB TM size. If you have multiple NAS in multiple locations, its then really simple to set it in a single place via an LDAP group. From my perspective the choice is an ease of management question more than functionality question. So long as your Mac is given the right size of what the TM disk image should be you'll get the right thing. PS You can refine the size of network TM backups quite a bit if you think a little bit about the method you would typically recover data. That is, will you use TM or will you use a snaphot (or other)? If you would never do a bare metal recovery and your mail server is Synology MailPlus Server/Synology Mail Server are you going to use TM or a snapshot to rover mail? If you're going to use the snapshot, why would you care to backup ~/Library/Mail? No bare metal recovery… when you only need to worry about /Users from the outset. Once you're reducing the TM size requirements like this you can happily have a 1x multiple on the quota size and it will also minimise network traffic.

@@IntoxicatedVortex thanks this is really helpful. One question though: if multiple users are using the same shared folder, will they be able to read or write the backups of another user? I can potentially see a problem of a user clobbering over the backups of another user.

@@mmdday No… each will be distinct. If you look into your TM destination folder in File Station when using multiple computers to backup to it you will see computer01.sparsebundle, computer02.sparsebundle, computer03.sparsebundle etc etc. Each of these will be distinct to the computer name and the disk image itself will be tied to the UUID of the computer. This Apple does because they know to keep network backups unique and separate. And if someone tried to restore from someone else's backup (which is possible when selecting a source for a recovery) you would still need the password for that TM backup.

@@IntoxicatedVortexThis was very helpful and makes a lot of sense to keep a single top level directory for all Time Machine back ups on the local network, then control the user quota based on group permissions. I mirrored your implementation. Thanks!

Hello, I have same problem. Time Machine doesn't show any disk to use it for backup. Can someone help with it?

kzfaq.info/get/bejne/ebmGqLKcrdqwknk.html

Wow! Thank you so much!

He has a separate video explaining all that bud if you still wondering

Think of a snapshot as a “version” of the backup. For example, if there is 1 backup per week for the past 3 weeks, that means there are 3 snapshots backed up.

I have been doing this for years and have never had a corruption across a ton of machines