- #APPLE CARBON COPY CLONER MAC OS#
- #APPLE CARBON COPY CLONER INSTALL#
- #APPLE CARBON COPY CLONER MAC#
Click “Clone” in the lower right-hand corner.Do not schedule this task to run automatically, otherwise your Clean Snapshot could be overwritten or pruned. Drag the destination folder onto CCC’s Destination selector.Drag the source folder onto CCC’s Source selector.Open CCC and click the New Task button in the toolbar.Create two empty folders somewhere on the prepped Mac’s startup volume, named “source” and “destination”.
#APPLE CARBON COPY CLONER INSTALL#
install any and all necessary software packages to the machine as if you were going to hand that machine out in its current state. Build out your machine as you would have built out your “image”.Getting started instructions can be found here.
#APPLE CARBON COPY CLONER MAC#
Ensure Mac has had High Sierra or Mojave previously installed and that the main hard drive is formatted APFS. #APPLE CARBON COPY CLONER MAC OS#
In theory, this method should also support standard hard drives alongside SSDs with Mac OS Mojave, as Mojave has migrated all hard drives to APFS, but I have not personally tested this. Once a machine has had High Sierra or Mojave installed, you can also use Carbon Copy Cloner to restore a new machine using the snapshot of an existing machine via Target Disk Mode. NOTE: Using APFS Snapshots to prep Macs for redeployment requires that High Sierra or Mojave have been installed using the installer from the App Store at least once, to ensure that the necessary APFS supporting firmware is installed, and that your SSD/Flash drive is properly converted from HFS+ to APFS.
OPTIONAL MDM Solution such as Profile Manger or Jamf. Bootable USB Flash drive or another Mac that can boot with Target Disk Mode with Carbon Copy Installed. Carbon Copy Cloner from Bombich version 5 (CCC). Mac with High Sierra or Mojave Preinstalled (tested with version 10.13.4 – 10.14.4). When your backup tasks run, CCC will automatically create a snapshot and use that snapshot as the source for the backup task. 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. 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.
0 kommentar(er)
