![]() Version 5 also happens to be an APFS Snapshot management tool for MacOS, allowing you to create, view, delete, and restore from APFS snapshots under High Sierra.Īs detailed on Bombitch’s Blog, when you select an APFS volume as a source to a CCC backup task, CCC will automatically enable snapshot support on that volume and set a default Snapshot Retention Policy for that volume. Sourceįor those of you who are not familiar with Carbon Copy Cloner, it is a low-cost backup app for Macs that can easily create bootable backup copies of your Startup Disks and manage Recovery Partitions. Apple also requires a specific developer entitlement for any third-party application that would create APFS Snapshots, and only after strict review. Unfortunately, it does not appear that Apple has a built-in way to permanently store snapshots or stop Local Time Machine Snapshots from being pruned. Apple itself notes that Local Time Machine Snapshots will be automatically pruned after 24 hours. The problem with the APFS snapshot method is that if you use the tmutil command to create AFPS Local Time Machine Snapshots as noted by James Otander, the system will automatically remove your Local Time Machine Snapshot after a 24 hour period. The Problem With Local Time Machine Snapshots: This will give you a fully prepared machine much faster than using the startosinstall option with the High Sierra Installer to do an “install in place” wipe of the machine, which took about 45 minutes in my tests. In my tests, this reverts a machine back to the snapshot state in about 5-10 minutes. One of the suggestions that came up was to use APFS snapshots to create a “snapshot” of the prepared drive, and then revert to the snapshot and install any necessary updates with Munki when a machine comes back in for redeployment. While DEP works great for newer machines, if your organization has existing Macs that are not enrolled in DEP, it is not an option for you. $99 US with code.A few weeks ago I posted on reddit asking how Mac admins are currently deploying/redeploying older Macs with APFS partitions now that imaging with DeployStudio is near its death. PS: as a treat to myself for all that work I purchased the Shadow Hills Mastering Compressor plugin from Plugin Alliance. ![]() Upshot is if you're having slow boot issues try zapping you NVRAM and see if that doesn't help you out. Googling this I came up with the thing of zapping the NVRAM which I did using this: and that did the trick. Rebooted into the normal internal HS and still slow. ![]() Ran OSX disk utilitity's repair and it couldn't unmount the drive so I restarted from the external HS clone and ran disk utility to fix things. I then rebooted and it took almost two minutes to get to a working desktop after the startup chime. Once I was happy I deleted the old HS partition leaving me with one primary partition with HS on it. The reboot took a while but then using the option key to boot into other than the usual partition takes a while so I paid no attention. For safety's sake so I didn't lose my machine authorizations for my Waves stuff I moved the licenses to an old dslr memory card. Rebooted into the new HS partition and tried a whole bunch of stuff to make sure everything worked. So once I reformatted the partition I used Carbon Copy Cloner to clone over the High Sierra partition. To be safe before I started all this I made up to date clones of both partitions. As any Mac user knows you cant' delete the primary partition so I reformatted it to APFS thereby wiping everything that was on there. That partition was the primary with the HS partition secondary. I run a 1 TB Samsung 850 SSD on a pcie card in the slot next to the video card in my 2012 cheesegrater. Had some downtime over the weekend and with the nasty weather rolling in here in the US Northeast I figured I'd wipe out the OSX 10.10.5 partition. ![]() I hadn't run either in a while, finally succumbing to NI's Vintage Organs and the B3 from Arturia and Arturia's Prophet 5/VS emulations. The reason being I had NI's B4II and Pro53 running there that wouldn't run anywheres else. As some might know I run a dual-boot system with OSX10.13.6 and OSX 10.10.5. Just wanted to pass on a little saga I went through in case someone else might be having a slow boot up in OSX High Sierra.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |