Thanks. I think I'm understanding it now.
Basically, a cloned drive becomes an exact duplicate of the source drive.
In fact, if my source drive is say 30gig and I have a 60 gig external hd, if
I clone to that hd I believe it turns into a 30gig hard drive. I'm not sure
how one would regain that additional 30 gig. I assume formatting might do
it, but then of course you've destroyed the cloned information.
Does that sound correct??
Mel
"Barry Watzman" <> wrote in message
news:4589b158$0$17193$...
> No, cloning a drive [let's call it a "direct clone"] and creating an image
> are not the same thing.
>
> When you clone a drive [directly], both drives are connected to the
> computer at the same time and the software makes the destination drive a
> "clone" of the source drive in real time. No files are created (or, if
> there are some temporary work files created, they are incidental and
> transparent to the process).
>
> When you create an image, on the other hand, the source is a drive
> (actually a drive partition) and the destination is a file that will be
> written to some media other than the partition being imaged (it can be on
> another partition of the same drive, on a different physical drive
> (internal or external), on a network store, or on optical media). But the
> destination is a file (possibly broken into multiple files, if you tell
> the program to break up the destination file up into pieces (normally for
> later writing to some kind of removable media)). The destination file is
> just a normal disk file, although it's typically large (hundreds of
> megabytes to gigabytes). You can copy it, delete it, rename it, move it,
> etc.
>
> The Image program can be used to write the image file back to a drive
> (either the same drive that was originally made from or a different
> drive), and if you do that the result would then be the same as if you had
> cloned the drive. Separately, for restoring individual files or folders,
> the Image file can also be accessed directly, without first restoring it
> to any drive. For such access, in some cases the image file is literally
> "mounted" and give a drive letter, after which it behaves like a read-only
> drive; in other cases, only a program that comes with the Image program
> can access it to copy folders and/or files "out of it", but either way you
> can view and get to it's contents without actually restoring the entire
> image back to a hard drive partition.
>
>
> MZB wrote:
>> Colin:
>>
>> OK thanks, but perhaps the terminology is confusing me.
>>
>> I thought cloning a drive and creating an image was the same thing. Is
>> that NOT the case? I'm trying to avoid EXACTLY what you described!
>>
>> Mel
>>
>>
>>
>> "Colin Wilson" <> wrote in message
>> news: t...
>>>> My question: Can I create my image saved to the D partition and still
>>>> retain
>>>> the files/folders I had there and also still have use of that partition
>>>> for
>>>> adding other files?
>>> Shouldn't be a problem - something else that might be worth doing is set
>>> the backup size to 4.7Gb and you can burn them to DVD as well - it'll
>>> just create as many 4.7Gb files as it needs
>>>
>>>> In other words, when I create a B/U image, is it just a file that would
>>>> reside on my external drive or does it turn that drive itself into the
>>>> image
>>>> (and hence lose what was already on there?).
>>> Yes, it just creates files, it doesn't try to clone the existing drive
>>> on top of another *unless* you ask it to !
>>>
>>> ...in which case, if it offers to let it resize for you, let it - I
>>> managed to f*ck a 10Gb partition on an 80Gb drive by cloning a 4Gb
>>> partition to it - it wrote the data in such a way that nothing has been
>>> able to retrieve the missing 6Gb since... a standard backup does NOT do
>>> this, so don't worry about it !
>>
|