![]() The windows8 2. Ive searching the web for an answer, havent found one that works. Finally have it and cannot access the aes-imac.sparsebundle, image not recognized. The only thing I miss from the 2012 is the optical audio output that was built into the 3.5 mm jack. Took a snapshot of the Time Capsule backup on BackBlaze. And heat is much lower when running at max CPU, which means the fan is quieter too. At least now it is backup up to the imac/imac dataset, but this is still. ![]() Im no longer able to mount the sparsebundle file as I get an error stating that there are no mountable filesystems. sparsebundle volume on a per-mac basis in case it gets corrupted. *the M1 still knocks the socks off the 2012 MM (both have 16GB RAM and 1TB SSD). 39 I messed up my Time Machine backup in some way. ![]() My wife's MM-M1 is now only using ABB for the Time Machine-like backup. I probably should have just wiped the sparsebundle folder on the NAS, but it's not hurting anyone. Movies, Music, Pictures, etc) for backup point before the migration. One thing I see is my Mac user's home folders have a locked icon (e.g. My TM archive goes back to April 2022, it's the most stable/reliable TM archive I have, and I can go into the backup before the migration. The problem simply is that Windows does not understand how to handle sparsebundles, let alone Time Machine backups, even Linux doesnt by default (youd need FUSE, sparsebundlefs and TMFS)If you were to open the sparsebundle on a Mac you would see a Backups. I had isolated the MM-2012 from WiFi and wired LAN, so afterwards I stopped any chance of it doing another backup before allowing it back on the network. I hadn't stopped the TM schedule on the MM-2012 before doing this and I now have the MM-M1 backing up to the same sparsebundle on the old NAS. Connected the two with Thunderbolt 3-to-2 adapter and a TB1/2 cable and it was fairly quick. After a long and somewhat adversarial discussion -he did not see the reason why I would not just start a new TM- he looked up an internal Apple memo that said the the TimeMachine files are no longer copyable or movable from OS 13 onwards.I did a macOS Migration Assistant from Mac Mini 2012 to M1 (there was absolutely no online noise about the M2, and I tracked that for ages, grr!*). The next level tech first tried to talk me out of moving the old time machine files, later seemed surprised that TimeMachine file structure has changed in OS 13 (the snapshots are no longer in the backups.backupdb folder but located “naked” at root level). You cannot copy or paste those newer -TimeMachine files by any of the previously available means. Look in Finder and you will see a sparse bundle with the partial Backups.backupdb file there. Now attach the drive to the Mac over USB. Give it a couple minutes to get started, then stop it and disconnect. The 1st level customer care tried everything I have -unsuccessfully. Attach the drive to the router (assuming it supports Time Machine) then start a backup to the disk using Time Machine. ![]() After 2 days of trying (unsuccessfully) we called Apple support (her machine is still under apple care). I refreshed my memory via several posted articles (e.g., Transfer your Time Machine backups to a new drive with this guide - AppleToolBox) and attempted to move my wife’s ™ -currently on a 2T WD magnetic drive- to the ScanDisk SSD. The idea was to copy over the “history” from the old TimeMachine to the new SSD a process I have last done about 3 years ago when my previous HD ran out of space. At the same time my Seagate 4T drive that hosted my TimeMachine developed problems, so we decided to get 4T SSD’s (SunDisk) and mover our backups to a safer, more spacious place. Even more scary when I went to the Xserve & looked at the TM Sparsebundle file it was not. The most common format for a Time Machine backup disk is Mac OS Extended format (Journaled) format, but Time Machine also supports Mac OS Extended (Case-sensitive, Journaled) and Xsan formats. We recently bought a MacBook Air (M2) for my wife with a more generous internal SSD (1T). Disk Utility was completely unable to fix anything.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |