Re: SATA and Ghost 2002

"Rod Speed" wet his paper bag:
Timothy Daniels wrote:
Rod Speed wrote
Timothy Daniels wrote:
And where is "the imager"?
Anywhere you want it to be.
Yeah. Like on a 2nd hard drive. One hard drive
for the OS. One for the imager.

The usual thing is one on the OS/app drive thats
used for the routine imaging so the image is always
up to date, and a bootable CD in case that drive is
unusuable....


So you have to synchronize the imager in the OS/app
drive and the imager in the bootable CD to keep
track of the incremental updates in case the hard drive
craps out. You must love accounting.


And the image probably came from partition 1 of the
primary drive, and the image files are stored in partition 1
of the archival drive, and so you restore the image to partition 2 -
AND YOUR BOOT.INI ENTRIES ARE NO LONGER VALID
because they point to partition 1. Smart.

It would be terminally stupid to do it that way if you want to be
able to boot off that 'archival drive' without changing any of the
multiboot detail. It would make a hell of a lot more sense to keep
the image files in other than partition 1 of that drive, fuckwit.


Ahhh! So you have to go into the image files and modify
their boot.ini entries so they will be correct when you
"restore" them. Smart. Especially when can have any
of the archived clones boot right where they lie by having
the "parent" boot.ini have a full complement of generic
boot.ini entries that get copied automatically to every
clone of it that's made. That means that although the
"parent" partitions can be partition X, the clone can be
booted right where it was put in partition Y *without* any
boot.ini diddling, without any "restoring", and without
synchronizing 2 versions of the imager to keep track of
the incremental file updates. Cloning is clearly the way to
go unless you want waste your time with record keeping.

*TimDaniels*








You clearly need that seeing eye dog and white cane bad.

You waste FAR more time working out how
to boot the clone you want to boot instead.

Yeah. See above and your screwed up boot.ini file.

See above on your terminal stupidity exposed
for the entire world to laugh at, as always.


.

Loading