9/11/2023 0 Comments Imazing backup![]() So, my recommendation is that you decide where you want backups before you install iMazing, set that in Preferences before you attach any device. And, to me more importantly, if you start with the default and switch to an external later, as I did, it won't erase/release that internal space when you do that. So, the lesson seems to be that if you install iMazing and just go with defaults, you could find that it will take a lot of disk space as it builds backups on backups. Finder thinks that's 323GB, which is consistent with what DigiDNA said about space being double counted in macOS and Windows. The target drive where the backups are now shows 240GB using "du -h" in Terminal. Now for the results: The iMazin folder in ~/Library is 88MB, down from 200+ GB. So that took 3 hours to do two backups totaling 250GB. Started the backup, as I said in the post #13 at 7:10 today, just a few minutes after 6 pm. I'm watching both the target drive, which is being written to, and the internal drive, which so far is not. No error messages, it just stops and cycles back to the beginning. I've now changed cables and am trying again. It keeps getting to about 20% done and then restarting. ![]() It's been about 1.5 hours and it isn't done. I've now reinstalled and re-registered iMazing and am in the process of making the first backup. So it may have had links, but despite being deleted, it didn't delete when iMazing was told to delete it. At one point the tech from DigiDNA said that to get the true space taken, you navigate in Terminal to the backup location and do a du -h command to get the real disk used. But the issue I had was that after telling iMazing to use a different location for backups, making a backup to that location and deleting all other backups through iMazing, it did NOT release the 200GB of space it was taking. So you need to delete backups through iMazing. Yes, they use links to files that are unchanged, much like TM does. Do I have to uninstall it and then reinstall, reconfigure and start all over to get that space back? I looked at the iMazing website and didn't see anything on how to recover that space. So, braintrust, how do I make iMazing stop stealing 194GB of drive space? I am thisclose to just getting rid of iMazing even though it's otherwise a great product. Look in Activity Monitor, don't see anything related to iMazing running. Stop that, repeat the delete, repeat Daisy Disk. Maybe it's because iMazing mini is running in the top bar. Run Daisy Disk and WTH? They both have reappeared in ~/Library/Application Support/iMazing/Versions! Getting more aggressive now, use Finder to locate the Versions folders, drag both to the trash and empty the trash. Enter iMazing, turn off archiving on both devices. Daisy Disk reports that iMazing was taking up 194GB, this time in a subfolder named "Versions" in ~/Library/Application Support/iMazing.Īh, that must be the "archiving" location. Oops, Get info on the drive says exactly the same. So let's see how much space I've recovered. Delete the prior backups through iMazing, get back all happy-happy results. So I go to iMazing preferences and set the default backup location to my external drive and do new backups on both the iPhone and iPad. ![]() ![]() Ah, that sort of makes sense in that I have an iPhone with 143GB used and an iPad with 110GB used and I've backed them up using iMazing. Investigating it showed that the space was in ~/Library/Application Support/iMazing/Backups. Daisy Disk informed me that iMazing was taking up just under 200GB of the drive, about 194GB. I've been trying to cull what I can and move what I can off the internal to a external drive. The free space on my internal SSD had declined a bit ago. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |