Cloning a Mavericks, Mountain Lion, or Lion Volume with
Phoenix or Disk Utility
What is Disk Cloning?
Disk cloning is the process of making an exact copy of the contents of one volume on a drive and putting them onto another drive. This process is very easily done using Disk Utility or our product Phoenix for Mac OS X. This document will describe how to perform cloning using both applications.
In this document we will refer to the volume being used as the source of the cloning procedure as the source, and the volume that will receive the copy of the source will be the target.
Why Clone a Volume?
Many people make the mistake of thinking that a cloned drive is the same thing as a backup. It isn't. A backup typically does what it says, it backs up the contents of a volume or drive to another volume or drive, but there are considerable differences between the two as follows:
1. A cloned volume is an exact copy of the original target drive. Backups may, depending on configuration, only copy partial contents and will not typically include the Recovery volume. Phoenix will not create the Recovery volume, but Disk Utility will. Phoenix can, however, create a Phoenix Boot Volume, which is essentially a recovery volume with one critical difference: instead of having a few tools, the entire core operating system is present.
2. A cloned volume verifies the integrity of the target volume ensuring the data is copied properly, some backup utilities don't.
3. The cloned volume is bootable whereas a typical backup isn't unless the backup has multiple volumes with at least one being a bootable volume.
4. Backup software sometimes, once again depending on the type and the settings, can make incremental backups, thus allowing the user to retrieve an earlier version of something, such as a program, document, illustration, etc. that a user might be working on. A cloned volume will only store what is on the source volume at the time the clone was made.
So why clone a volume? Most often to make a bootable drive or volume that can be put into use in the event that the main drive on a system fails. Many people do daily backups, and then, less frequently, clone a bootable (primary) volume less frequently. Some people simply use the cloning process as the backup. It's really up to the user.
When Shouldn’t You Clone a Volume?
The Disk Utility method should not be used to clone a volume if any of the following conditions exist:
• The hard drive is failing and has bad sectors
• The hard drive has been rendered read-only due to indexing problems
• Files are missing or corrupt
Cloning a volume using the Disk Utility method will not fix a volume with problems. In fact, all you will be doing is wasting your time duplicating the same problems by copying them onto another drive. The Disk Utility method uses block copying, and instead of generating a new volume index as files are copied it will replicate the old index. If this index is corrupt, the cloned volume will have the exact same problems as the original volume. Additionally, if bad sectors exist on the drive, even if they don’t contain data, the Disk Utility method will fail to complete, possibly wasting a considerable amount of time.
Phoenix for Mac OS X uses file copies instead of block copies. File copies have the benefit of generating a new volume index as the files are copied, while also effectively defragmenting the drive. If a volume has indexing problems and has been rendered read-only, Phoenix may (note emphasis - may) be able to recover the drive in its entirety. Additionally, a Phoenix clone doesn’t require that the target volume be at least as big as the source volume, only that the target volume has enough free space on it to store the contents of the source volume.
What's Required to Clone a Volume?
Prior to cloning a volume, and depending on whether or not you wish to do this using Disk Utility or Phoenix, the following requirements need to be met:
1. Recovery Volume Requirements
Disk Utility: The source volume, which should be your primary Lion or Mountain Lion volume must have the Recovery volume installed on it. Unless there was some oddity that occurred during installation, it should be there.
Phoenix: Phoenix can clone a working volume without the need for install media or a Recovery volume. However, during the cloning process the user shouldn’t be using the system for anything. Phoenix will not create or copy a Recovery volume (a Phoenix Boot Volume if you decide to create one, is a recovery volume, but with much greater capability).
2. Target Volume Size Requirements
Disk Utility: The target volume must be at least as big as the source volume. This is critical. If the target volume isn't as big as the source volume, even if it's only off by a few kilobytes, the cloning process won't be allowed to start using Disk Utility.
Phoenix: The only requirement is that the target volume has enough free space to store the contents of the source volume. Remember, if using the Disk Utility method, and you transfer to a target volume that’s bigger than your source volume, you won’t be able to clone it back to the original volume unless you resize the partition so it’s smaller or the exact same size as the recipient. This problem doesn’t exist with Phoenix.
3. Partition Format Requirements
Disk Utility: Cloning with Disk Utility will completely over write the entire drive and there will be nothing left of the original contents of the target drive after cloning is complete. Cloning with Disk Utility is not a backup or copy procedure, it's an overwriting procedure. When using Disk Utility, it will essentially duplicate the format of the source volume.
Phoenix: Cloning with Phoenix is a copy procedure and the contents of the drive will not be overwritten unless they’re redundant. However, the format of the source and target volumes must be the same.
4. Partition Scheme Requirements
This applies to both Disk Utility and Phoenix: The target volume should be in the same partition scheme as the source volume, which generally means it should be a GUID partition scheme since we're focussing on Intel based Mac's.
5. Time Requirements
Disk Utility: Disk Utility is going to duplicate each and every block on a volume, even if the block doesn’t contain data. It will generally take as long using Disk Utility to clone a volume that’s 30% full as it will to clone a volume that’s 90% full. For standard hard drives, expect the process to take about 1minute per gigabyte.
Phoenix: Phoenix only copies existing files from the source volume, thus the amount of time it will take will vary on how full the source volume is. Generally, expect it to take about 1 minute per gigabyte of used space on the source volume.
Naming Convention Note: We strongly advise against using names for the target volume that are identical to the source volume but separated by a space followed by a number (for example, “Lion” and “Lion 1”.) The reason this can be problematic is because the OS can automatically append a digit to an existing volume with an identical name even though the volumes may have completely different content. Several applications can become confused by this. We recommend using a descriptive name for the clone or, if you insist on using numbers, put no spaces between the original name and the numeric identifier.
If you use Disk Utility instead of Phoenix to perform cloning operations, at the end of the cloning process, Disk Utility will exhibit this exact behavior - your cloned volume will have the exact same name as the source volume. After the system boots up, we recommend changing the name of either the source or target volume as soon as possible.
For the remainder of this article, we'll be using Phoenix to clone a Lion (MacOS 10.7) based volume, and Disk Utility to clone a Mountain Lion (MacOS 10.8) based volume. The procedures will be identical in each case regardless of the operating system being used. Additionally, Phoenix may be used to clone volumes and operating systems from OS X 10.5 (Leopard) through 10.8 (Mountain Lion.)