I was having issues with Time Machine rapidly claiming "out of space" on a 512GB portable SSD (for an internal MacBook Pro 500GB SSD with only about 200GB of data on it). It didn't want to delete previous backups to make space for new ones...or do incremental backup.
So I now have a 2TB SSD for it - but I really don't want to dedicate all that for a TM.
I'd like to use the other space for other (portable) data.
I've read using Volumes vs Partitioning is something TM doesn't like - true?
There's also the new option to limit the disk usage. (1TB for the TM is my goal)
If it's limited - can I just write other data into a folder on the SSD and leave the TM folder alone to do its thing?
Or do I *have to* use 2 Volumes or the option of Partitioning - which is how I might have done it under Mac OS Extended HFS.
This would of course limit and divide the disk space.
Which way to go?
I'm not concerned about "all eggs on one basket" SSD failure. The non-TM data will be for copy/moving data bi-directionally from a MacBook Pro to Mac Studio - which has it's own TM drive, redundant external 16TB drives and Backblaze.
Thoughts?
So I now have a 2TB SSD for it - but I really don't want to dedicate all that for a TM.
I'd like to use the other space for other (portable) data.
I've read using Volumes vs Partitioning is something TM doesn't like - true?
There's also the new option to limit the disk usage. (1TB for the TM is my goal)
If it's limited - can I just write other data into a folder on the SSD and leave the TM folder alone to do its thing?
Or do I *have to* use 2 Volumes or the option of Partitioning - which is how I might have done it under Mac OS Extended HFS.
This would of course limit and divide the disk space.
Which way to go?
I'm not concerned about "all eggs on one basket" SSD failure. The non-TM data will be for copy/moving data bi-directionally from a MacBook Pro to Mac Studio - which has it's own TM drive, redundant external 16TB drives and Backblaze.
Thoughts?
