SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
From: PMS Witch3/20/2014 5:23:52 PM
6 Recommendations

Recommended By
FJB
goldworldnet
Gottfried
Raptech
shadowman

and 1 more member

  Read Replies (1) of 110631
 
Clone and Image. . .



Drive clones and images share so many characteristics, confusion seems inevitable. Let’s take a closer look at them and explore the differences.



A clone is usually considered to be an exact duplicate of another disk. Not only is the data identical, but so is the underlying architecture. Every disk has areas reserved for supporting roles: Disk Signature, Boot Record, Change Journal, and Partition Table being just a few examples. All these values are reproduced when the clone is made.



Windows will NOT access both a cloned disk and the original if they are both installed in your computer. If you try this, one of the disks will get disabled, and if you investigate using Disk Manager, it will report that you have a Disk Signature Collision.



Most cloning software warns you to remove the cloned disk from your system before attempting to boot Windows. Not all explain why.



Windows XP system usually work correctly when a cloned disk is substituted for the original. Windows Vista, and later Windows versions, check Disk Signatures before booting, and refuse to proceed if a different disk is detected. Early cloning software handled Vista poorly because they skipped the necessary step of updating Vista to work with the clone. Cloning software creators have had a few years now to correct this shortcoming, and most have updated their programs.



Why not use clones exclusively?



Perhaps the biggest reason is disks come in different sizes. Clone a 100GB drive to a 500GB drive and you’ll waste 400GB. (Remember, the clone has the same "size" information as the original.)



Another issue is time. Clone a huge disk and a huge amount of data is copied -- even if the disk is empty! In this case, you’re copying a ton of nothing.



So why not simply use Images.



Images have a number of advantages. Image software often has the smarts to disregard empty space. Images are usually compressed. Images take a fraction of the time to create. Several images can be archived, making them an almost perfect backup solution.



Don’t overlook the speed advantages of using Images. This is a huge factor when working with external drives, especially if they’re connected using USB.



But Images often don’t store critical supporting data like Disk Signatures or Boot Records, although a few do.



As well, Images typically store Volumes. This makes it challenging when working with disks with hidden partitions needed for special purposes like Factory System Restore or Windows special boot partitions. To save or restore these, you need to know about them and take measures to ensure they aren’t overlooked.



Images handle different sized disks with ease. Changing partition sizes and location is profoundly simple when using Images.



What would I do?



If I were replacing a disk in my system, I’d make a clone of the original. If the new disk was larger, I’d start with creating a clone and make size adjustments later.



If I were making a backup of my system, I’d make an image.



If I were altering my disk layout, implementing multiple OS booting, or experimenting, I’d use images.



Hope this helps.



Cheers, PW.





Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext