Backing up multiple volumes or multiple Macs to a single hard drive can be a messy proposition. If you back up each source volume to the same destination volume without some pre-planning, data from each source volume will be merged in a heap on the backup volume. Additionally, your tasks will archive or delete each other's backed up content. Carbon Copy Cloner can solve this problem! We lay out a few different scenarios and solutions below.
Última actualización por 30 March 2021
Note: The topics in this article are not relevant to APFS-formatted destination volumes that have CCC snapshot support enabled. For those volumes, CCC leverages snapshots to implement the SafetyNet functionality, and the snapshots aren't affected by any of the shortcomings described here.
Última actualización por 22 January 2021
Reminder: Recovery HD volume cloning is not applicable to APFS-formatted destination volumes (i.e. Catalina and later)
Carbon Copy Cloner offers complete support for archiving, cloning, and recreating Apple's Recovery HD partition. See the Cloning Apple's Recovery HD partition section of CCC's Disk Center documentation for instructions to create a Recovery HD volume on your backup disk.
Última actualización por 4 January 2021
Generally, yes. Performance will be affected during the backup task (especially the first one) as CCC reads the entire source volume and writes to the destination volume. If your work is "disk bound" — that is your applications are reading or writing to either the source or destination, then you'll notice a performance hit. If you're just reading email or writing a document, then you probably won't notice the performance hit.
Última actualización por 24 April 2018
CCC always examines the files on the destination to determine if they already match those on the source. If you have a volume that is virtually identical to your source, CCC will copy only the items that are different between the two volumes.
Última actualización por 14 July 2017
CCC offers hourly, daily, weekly, and monthly scheduling options, which suits the needs of most users. Some usage scenarios, however, demand higher frequency backups. For example, photographers might prefer to have their SD cards offloaded to a tethered computer every 5-15 minutes during a photo shoot. When the shoot is complete, though, the backup task should not run at all. Special cases like these demand more flexible execution options, which can be achieved by leveraging CCC's built-in command-line utility.
Última actualización por 14 June 2017
Última actualización por 11 October 2019
La respuesta suele ser probablemente sí. Sin embargo, hay algunos peros.
Última actualización por 8 June 2017