B
Bill in Co.
I don't think an hour of waiting around for it to complete is "completely
insignificant".
insignificant".
John said:Bill, I did a re-image of my hard drive yesterday from my removable backup
drive and, as you stated, the 'increase' in time to perform the task is
noticeable.
Of course the first 'time' deficiency is that, when using a
removable drive, Acronis has to re-boot to the pre-windows environment
prior
to starting the copying of files.
Right.
Another annoying problem with Acronis is
that it doesn't seem capable of keeping an accurate time.
As an example,
when I first entered the pre-windows environment and the Acronis
interface
appeared the copying interface stated that the re-image would take 50
minutes. The next time I looked (probably 5 minutes or so later) the time
had dropped to 26 minutes. You only have to wait until the time counter
has
reached the 1 minutes 55 second region to see that, for some unknown
reason,
the Acronis clock allocated 3 to 5 seconds or more for every 'real time'
second, so when it states that the re-image has 1 minute 50 seconds before
completion you could be sitting there for 5 minutes or more before the job
actually completes.
Under normal circumstances one usually leaves Acronis to get on with the
job
but, on this occasion, I was writing at my desk and it was only when
periodically looking at the progress that I noticed this idiosyncrasy.
Frog said:Bill,
You were a part of the discussion when Anne recommended Casper to me
back in February. I have found this software package to be very simple
to use. When I have my USB hard drive connected, I can go to drive G or
H, and it looks and acts just like my C and E on my internal drive. I
have restored files, while in normal windows, from this external hard
drive back to the internal hard drive with no problem. I generally find
that it takes me about 2 minutes to back up my internal drive to the
external drive.
The CD used to start the system, when/if the normal
start-up procedures stop working, requires about 3-4 minutes to load
from a CD. Once loaded, it would be a simple process to restore either
my C, E or both drives from the external hard drive.
I think the only
thing I would add to my backup system would be a second USB 500 GB hard
drive, so that I would have two backups made at two different dates.
Frog said:Bill,
You were a part of the discussion when Anne recommended Casper to me back
in February. I have found this software package to be very simple to use.
When I have my USB hard drive connected, I can go to drive G or H, and it
looks and acts just like my C and E on my internal drive. I have restored
files, while in normal windows, from this external hard drive back to the
internal hard drive with no problem. I generally find that it takes me
about 2 minutes to back up my internal drive to the external drive. The
CD used to start the system, when/if the normal start-up procedures stop
working, requires about 3-4 minutes to load from a CD. Once loaded, it
would be a simple process to restore either my C, E or both drives from
the external hard drive. I think the only thing I would add to my backup
system would be a second USB 500 GB hard drive, so that I would have two
backups made at two different dates.
Frog
Anna said:Frog:
Glad you've found Casper disk-cloning program to your liking. As you have
pointed out, the latest version is Casper 5. In general it doesn't seem
too
different from version 4. They've changed the user interface a bit -
designing it a bit more "modern" I would guess. Also, corrected a bug or
two. But essentially the program "feels" the same as the earlier version.
Needless to say I'm not too surprised about your favorable review. We've
been using the program for about two years now and have been quite
impressed
with it. It has become the disk-cloning program of choice for virtually
every user who has experienced the program.
A couple of points...
1. The CD you mention "to start the system" is, of course, the Casper
"Startup Disk", a bootable CD that contains the Casper program. It is
generally used only in those situations where the Casper program is not
accessible on the HDD on which the program is installed because that HDD
has
become defective or the system so dysfunctional that it's unbootable. So
the
Startup Disk would ordinarily be used to access the drive (internal or
external) on which the clone resides and clone those contents back to the
internal (original "source") HDD - should that HDD be non-defective - or
to
a new HDD should that be necessary - in order to restore the system.
Routine backups of the system would, of course, be effected through the
use
of the Casper program installed on the source HDD.
2. As you point out, a significant advantage (if not *the significant
advantage*) of the Casper program in comparison with every other
disk-cloning program we've worked with over the years is its rather
extroardinary speed in backing up one's day-to-day working HDD through its
disk-cloning process. When used on a routine basis - say every day or
every
other day or once a week, etc., the program takes a fraction of the time
to
complete the disk-cloning process because of its "SmartClone" capability.
This is an enormous incentive for users to comprehensively back up their
systems on a frequent basis, knowing that the operation will take a few
short minutes, just as you have experienced.
3. You mention the possible need for another large external HDD in order
to
create "generational" clones, i.e., clones of the system at different
points
in time. I assume you're aware that you could multi-partition your present
500 GB HDD and clone the contents of your internal HDD to each partition
at
different points in time. Obviously the amount of data you would be
cloning
would determine whether this is feasible. Let's say for example that as a
general proposition you have about 50 GB of data on your source HDD. You
could then create a fair number of partitions on your external HDD to act
as
recipients of the cloned data at various points in time. As I'm sure you
know, the Casper program easily allows one to clone the contents of the
disk
(or individual partition) on the "source" drive to any partition on the
"destination" drive (and vice versa). And the restoration process is as
simple as the backup process. You would simply choose which partition on
the
destination drive you wish to clone the contents back to the internal HDD.
(I see where "Bill in Co.") has posted a response to your latest post. I
have apparently been simply unable to explain to Bill Casper's
disk-cloning
process in a way that he truly understands that process. With respect to
cloning the contents of one's internal HDD to this or that partition on an
external HDD Bill somehow sees this as some negative implication because
the
various partitions containing each clone will bear different drive
letters.
I can't seem to make him understand that this is of no consequence since
the
drive letter assignment for each partition on the destination drive has
absolutely no relevance should the contents of that partition be
"re:cloned"
back to the internal HDD for "restoration" purposes.)
Anna
Bill in Co. said:Because some of the multimedia trial software applications that I try out
to see if I want to purchase them are quite extensive, and often change
lots of things on my system, some of which are sometimes not reversible by
a simple uninstall.
I'm talking about some relatively large audio and video apps - multimedia
apps, for example. And just uninstalling the program is often not
enough. To explain:
For example, if you install something (e.g.) like a trial version of Adobe
Audition, it makes some pretty extensive changes to your system, and since
I do a fair amount of audio restoration work (for myself), with various
audio and sometimes video applications, the last thing I need is any added
hiccups to my system (such as with codec modifications, codec or DLL
removals or replacements, or anything that affects any of my other related
multimedia software).
(BTDT, on several occasions, so, thanks but no thanks)
As I said, I've been around the block on this one. (One has to have
really walked the walk, to know the talk, here.
And the ONLY sure and safe way to get it back *perfectly as it was* is to
do a restore operation, should you wish (I mean, a guaranteed clean
"uninstall" of the app AND whatever collateral system, codec, DLLs, etc,
"damage" it had the potential to do, and sometimes has, in the past. As
I said, BTDT.
(But does this mean I never just use uninstall? Of course not. It all
depends, and experience is the best lesson, to really know this one).
Unknown said:The original point Bill was trying to make was the amount of time needed
to
restore his system.
Is it earth shattering if it takes 20 minutes instead of 18 minutes? I
think
not.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.