Question about Hoster back-up

[gduns - with the Lord]

I keep a small C: (system drive) with an operating system , and the nessicary programs only on it (less than 30 gigs). I use norton ghost to make an Image (1 file that contains the entire c: drive), on my D: drive. It takes up about 7gigs.

I use a usb external hard drive for the music files, or you could use the internal D: drive for this, as you have plenty of room.

When you reimage the hard drive from the file on the D: drive, it rebuilds the C: drive to the way it was when you made the image. No reloading software, windows ect.

This is the Best way I have found to do it. Ghost will also copy one hard drive to another, But that is a waste of space as far as I am concerned.

[tymzend]

Maybe I need to try your approach

[DJYale]

Having never used Ghost to create a drive image, just curious as to how long it takes to restore a Ghosted image?

Personally, I cheated when I built my rack-mount and bought dual hot-swapable drive bays.

[mindonstrike]

For those of us without ghosting capabilities you can try "restore" (assuming your HD didn't die).
Before any upgrades or making any changes to my computer(s) I set a restore point just in case. Rarely used but when I have needed it, it's saved my backside.

Sam

[gduns - with the Lord]

GHost takes 5-15 minutes to rebuild if you have the image on another hard drive. If you have it on dvd or cd's it takes a little longer.

[MTUSUPPORT]

Powerquest Drive Image is the NEW Ghost 9.0. Norton bought out Drive Image, and now the newest version of Ghost is now Drive Image, and the old Ghost was scrapped.

Drive image has always been far Superior to Ghost in my Opinion, and obviously Norton also thought so, and this is why they bought it, and renamed it as Ghost 9.0.

When you do a backup, it is exactly what was on your Hard at the time you did the backup. I am not sure why yours caused a problem. Do you have the exact Error that it gave you, I know that this happened at a show and you probably didn't keep it, just because it was critical. This will always help me though, about the only thing to give me something to go on.

[Flipeoke]

I'm just guessing here, but when you did the uninstall of Hoster, and realized you couldn't install, are you sure you booted from the "back-up" D: drive? or did you boot from C: and try to use the Hoster from D:

Perhaps, if you booted from C: some of the files needed for Hoster were missing (since you uninstalled) and it would not run properly. To my knowledge, (Which I admit is somewhat limited) if you have an exact replica of a drive you should be able to do anything you want to the first w/o messing up the second...(unless you are using a RAID configuration) This being said, either you mistakenly booted from drive C, or the drives were not identical...when was the last time you booted from D: and tested it out...?
Did you do any updates of Hoster after making your backup drive? If you did, and you were booted from "C:" and updated hoster on both drives, it is quite possible new files were saved in the c:\windows\system on your C drive, and not updated on your D:\windows\system or something to that effect... If this were the case, you either would have to backup again after updating Hoster, or boot from C:, update Hoster, then boot from D: and update again...

Again, not really sure, but just some possibilities I had thought of...

Flip