New posts

Reply to thread

Message: <blockquote data-quote="MacInWin" data-source="post: 1826012" data-attributes="member: 396914">From my work on it, I think it can be a real data hog if you leave it running. Even if Mail is not backed up, there are things they show on that page as definitely being backed up that change frequently (Reminders, Calendar, Messages, Notes, Applications and Photos). For a better example than Mail, if you have, like I do, 9000 images in Photos and take one picture to add to it, that entire database is now copied as a new backup, duplicated in the next TM Snapshot and if it syncs to another iDevice (like my iPad, where I do also sync), then you end up with FOUR copies of the photos database.Now I don't know exactly what is being backed up, but my iPhone says it has 143.4GB used and my iPad has 113.6GB used. In the backup for both of them iMazing has taken up 152GB in the backup folders on the external drive as reported by running du -h in that folder. So some things are not being backed up, and iMazing is compressing pretty well, but still, if you have a large storage device (or two) and use that storage for volatile things like pictures/messages/calendars, etc, then iMazing will start to consume a large amount of space. Now add in TM and CCC snapshots and things start to multiply pretty quickly, as I found out.But it's a free country, so you do whatever you think is best for you. For me, I've recovered a LOT of space just by moving the backups to an external drive and not letting iMazing run all the time. I'm not saying iMazing isn't a good product, or that it should not be used, I'm just trying to say that if you use it, keep an eye on it.- - - Updated - - -For TM, the issue is not so much the backup as it is the snapshots TM makes. My TM backup is to a different external drive, one with tons of storage, so I don't care how many times TM duplicates data there. But I do care about taking my internal drive space in snapshots.</blockquote>

Verification: Name this item. 🍎