![]() |
Backing up to a disk image |
||
Sometimes backing up your data to a single external hard drive is just too messy and difficult to organize. Suppose, for example, that you have three computers in your household, and everyone backs up to the same external hard drive. Where do you put each person's backup? The single hard drive can't maintain multiple operating systems, Mac OS X does not support that. You could split the drive into three partitions, but that isn't very flexible at all. You could clone each person's drive to a folder on the drive, but that's a little difficult to restore from.
A good solution in a scenario such as this is to use disk images as the medium of your backup. A disk image is a single file residing on your hard drive that contains the entire contents of another hard drive (except for the free space). When you want to access the contents of that filesystem, you double-click on the disk image to mount the disk image as if it were an external drive attached to the machine. Carbon Copy Cloner 3 leverages disk images to provide you the flexibility of storing several complete, bootable* backups on a single shared external hard drive. (* Disk images themselves are not bootable, but you can mount them and restore their content to a physical hard drive to produce a bootable, exact replica of the original).
After choosing a source volume from the Source Disk popup menu, choose "New disk image..." from the Target Disk popup menu. Provide a name and choose a location to save your disk image. If you plan to back up to this disk image again in the future, select the option to "Create a read/write sparse disk image". If you want a read-only disk image for archival purposes, choose the option to "Create a read-only disk image". Note that if you schedule a task in which you create a new image, CCC will recreate the image every time the task runs. See the Backing up to an existing (read/write) disk image section below for a more appropriate choice for scheduling backups to a disk image.
Read/write "sparse" disk images
A sparse disk image is a type of read/write disk image that grows as you copy files to it. In general, sparse disk images only consume as much space as the files they contain consume on disk, making this an ideal format for storing backups.
Read-only disk images
When creating a read-only disk image, you have two additional options. If your target disk is short on space, you can compress the disk image. Compression rates vary on the content of your source, but you can typically expect to reduce the size of your disk image by about half when using compression. There is a subtle behavior that you should take note of when considering this option as a space-saving measure: When using the "Incremental backup of selected items" cloning method, CCC will first create a read/write disk image, copy the selected items to it, then convert the disk image to read-only compressed. In this case, you will actually need twice the space on your target as the items to be copied consume on the source. When using the "Backup everything" cloning method, this limitation does not apply, CCC will create a read-only compressed disk image in one step.
The second option allows you to segment the disk image. This option is ideal if, for example, you intend to burn the segments to optical media.* Like with the compression option, CCC will also create a temporary read-write disk image -- not segmented -- when using the "Incremental backup of selected items" cloning method.
* To mount a segmented disk image, all segments must be present on the same media. Burning disk image segments to optical media is a great archival practice, just keep in mind that should you ever need to restore from that backup, you will first need to copy all segments onto a volume with adequate capacity.
Encrypting disk images
If any of the data that you are backing up is sensitive, and if your backup device may be in an insecure location, it is a good idea to enable encryption when backing up to a disk image. CCC uses 128 bit AES encryption to encrypt disk images. Note: CCC does not currently support encryption during scheduled tasks. If you require disk image encryption and are willing to accept a small amount of manual intervention, you can manually mount your disk image, then choose the mounted volume in CCC's interface prior to creating a scheduled task. The setting to run the scheduled task when the target disk reappears is an ideal setting for this scenario, the backup will run whenever you remount the encrypted disk image.
Backing up to an existing (read/write) disk image
If you regularly make backups to a disk image, this is the option you will want to choose when choosing a target disk. After choosing a source volume from the Source Disk popup menu, choose "Choose disk image..." from the Target Disk popup menu. In the Open dialog box, navigate to and select your disk image and click the OK button. After clicking on the Clone button, CCC will mount the disk image and backup your data as if it were any other backup device.
When backing up to an existing disk image, be sure to choose a disk image that is writable. If you choose a sparse disk image that CCC created in a previous backup, CCC can be configured to copy everything again, overwriting data on the disk image, or to copy only the items that have changed. A sparse image will grow as data is copied to it.
Learn more about performing basic clones with Carbon Copy Cloner
Learn more about backing up your data with Carbon Copy Cloner
Considerations for scheduling a backup task to a disk image
While CCC allows you to back up to a disk image located on your startup disk for ad hoc backup tasks, this is not a configuration supported for scheduled backup tasks. If the startup disk runs out of space, Mac OS X will become unstable. If you would like to automate a backup to this disk image, please store the disk image on a volume other than the startup disk.
"CCC refused to mount the sparsebundle disk image because doing so would put its contents at risk of data loss"
Starting in CCC 3.3.5, CCC will refuse to mount a sparse bundle disk image if the underlying filesystem that the disk image file resides upon does not support the F_FULLFSYNC file control. Here's a little background to understand why:
When your computer writes a file out to the hard drive, the data usually goes to a "write buffer" — a small portion of RAM that is installed on the circuit board of the hard drive. By accumulating smaller write operations onto this RAM chip, the hard drive can increase overall write performance by writing large blocks of cached data to the physical media all at once. While this write buffer improves performance, it also carries a risk. If the power fails or the disk's connection to the computer is suddenly broken between the time that data was written to the buffer and when the buffer is flushed to the disk, your filesystem will have an inconsistency. Filesystem journaling typically mitigates this risk, however it doesn't offer enough protection for Apple's sparsebundle disk image type, a new kind of disk image introduced in Mac OS 10.5.
In Mac OS 10.5, Apple implemented the F_FULLFSYNC file control for network servers and clients. The F_FULLFSYNC file control is a command that is sent to the hard drive after some (or all) write operations that tells the disk to immediately flush its cache to permanent storage. To provide better protection for data on sparsebundle disk images, Apple disabled support on Mac OS 10.6 for using sparsebundle disk images that reside on filesystems that do not support the F_FULLSYNC file control. CCC extends and improves this protection by refusing to mount a sparsebundle disk image if that disk image resides on a filesystem that does not support the F_FULLSYNC file control, regardless of the current OS that you are running.
You are likely to encounter this error condition if your sparse bundle disk image is hosted on a pre-Mac OS 10.5 Macintosh or various Network Attached Storage (NAS) devices. When you encounter this error, copy the sparsebundle disk image to another network sharepoint, or ask CCC to create a new sparse disk image file (sparse disk images are not the same as sparsebundle disk images).