I have just uogrades to Ghost 10 from many years of using Ghost 8.

I always boot Ghost from a floppy disk an run in shatnd alone mode.

I hav a problem that I do not understand.  Previously when I made partition or disk images, they existed on the target drive as ne single file unless I told it not to.  With Ghost 10 I always seem to get multiple files created.  

This is a nuisance.  Can some kind soul please tell me which command line switches I need to invoke in order to make this happen.  Yes, I have read the user manual and I cannot find what I'm looking for.

Thanks.

The main image backup file image is the .v2i file.

http://radified.com/cgi-bin/YaBB/YaBB.cgi?board=ghost9_10;action=display;num=1166532191;start=1#1
.v2i is the image file
.iv2i is an incremental image file.  
.sv2i is an index file and for practical purposes can be ignored.  

RedErik,

How large are these files? What file type extensions? Are you using NTFS?

Thanks for your replies.

I Ghost-ed a half full 80Gb drive that is NTFS to a 200Gb drive that is NTFS.  The files I got are:
name.GHO      2'097'132 Kb
name001.GHS 2'097'132 Kb
  .
  .
name008.GHS 2'097'132 Kb
name009.GHS 1'024,010

I created the diskette with the Ghost Wizard and it is a simple DOS boot disk with no options.

Thanks - Pete

RedErik wrote on Jan 25^th, 2007 at 3:34am:

I Ghost-ed a half full 80Gb drive that is NTFS to a 200Gb drive that is NTFS.  The files I got are: name.GHO      2'097'132 Kb name001.GHS 2'097'132 Kb   .   . I created the diskette with the Ghost Wizard and it is a simple DOS boot disk with no options.

.GHO file extensions are from Ghost 2003 or some other older version, not Ghost 10.  Ghost 10 only runs from within Windows XP (or Windows 2000 Pro).

There is no Ghost 10 DOS.

Ghost4me


Quote:

There is no Ghost 10 DOS.

I would agree, but....currently the corporate version of one flavor of Ghost has recently been boosted to v11.xx--it uses the DOS file format of *.gho* and *.ghs* (Latest Ghost v11.0.0.1502 Corporate Edition)--and someone recently posted that corporate v12.xx is coming in spring sometime.

The previous corporate version I was aware of was 8.xx that uses  *.gho* and *.ghs* image files.   Does anyone know if there were corporate v9.xx and v10.xx in between the 8.xx and 11.xx?

RedErik made the following statement in his first post:


Quote:

I have just uogrades to Ghost 10 from many years of using Ghost 8.

(Symantec's naming and version numbers are really becoming more and more confusing--what versions do what and how,  and ...........???????)

************************************************

RedErik

Where did your copy of Ghost come from--is it a retail version you installed, or from a corporate environment--why are you calling it Ghost 10?

Ghost 11.0 creates just a single .gho file during a disk to image operation.  By default, it no longer splits into several smaller .gho files.

re Ghost versions, several posts in this thread are interesting.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PageIndex=2&SiteID=17&PostID=1109842

Thank you all for pointing out several erros in my posts.  Duh!

I own a CD of Ghost 10.  I bought it from my usual supplier.  It has a serial number and I have now installed this on one of my PCs.

The version I have been using is Ghost 2003 (unbknown to me) on a customer machine.  I saw Ghost 10 on my box and assumed (yes Ass - U & me) that I had the same version on the customer machine.

So, I am, in fact using Ghost 2003 - in DOS and, I am having this problem with multiple files of about 2Gb each.  Can anyone help please.

I shall now try and source a copy of Ghost 2003 for myself since there is NO WAY that I am going to try and clone partitions and disks from within Windows.

Thanks for your understanding (what an idiot...)

RedErik wrote on Jan 26^th, 2007 at 1:38am:

since there is NO WAY that I am going to try and clone partitions and disks from within Windows.

RedErik, I guess it's a fear of the dark thing. You are not alone. That's how Ghost 10 does imaging and cloning. From Windows. And it works well.

RedErik

The max file size in Ghost 2003 will be approx. 2 GB--a DOS file size limitation--as somms pointed out up above, corporate Ghost 8.3 and above apparently has been engineered to work around that DOS limitation.

I believe Ghost 9 and 10 do not have that limitation.

NightOwl,
Thanks for your reply.  I have previously used Ghost 8 and it backed up a 40Gb drive to an NTFS partition in one single file with no problem.  Ghost 2003 does not seem to have this option.

I shall try my new version of Ghost 10 to see if it allys my fears of making partition and disk images under Windows.  If not I shall resurect my old copy of Disk-Image.

I would still like to find the switch that allows me to make a single file image of an NTFS partition to another NTFS partition.  So if anyone knows the magic -nospan switch then PLEASE would they be kind enought to post it here in an ijit proof manner for me.

Thanks to one and all for yor help.

RedErik,

Just a few points that aren't obvious at first with Ghost 10. It makes Partition images but not Whole Disk images. It clones (Copy My Hard Drive) partitions and not the whole disk.

From the Ghost 10 Recovery Environment you can use the "legacy" Ghost 8.2 to do all the things that you have been used to playing with.


Quote:

allows me to make a single file image of an NTFS partition to another NTFS partition.

Ghost 8.2 will do this without a switch.

Correction, Ghost 8.2 (ghost32.exe) from the Ghost 10 RE splits the backup image into 2 GB files. NTFS to NTFS.

RedErik

I have never had problems with spanned Ghost image files!

Hello,

I'm new here and having a problem...I've imaged a monster drive...770GB, that was originally partitioned as C: (20G), D: (20G), E: (1.05TB).  

The image process worked just fine.

When I try to restore the image to a different machine with the same hardware configuration, Ghost is displaying a negative drive size, and because of that, it won't let me create the partition sizes correctly on the new box.  Has anyone run into this before?

Thank you for your help.  I've been working on this for the past 8 hours.

Thanks,
Jason

drazzst,

I'm a little confused but certainly impressed with your HD size. Ghost 10 doesn't work in DOS. How did you create the image(s)? How are you restoring the image(s) to the other computer?

Sorry, like i said, i've been doing this for the past 8 hours :)

I used BartPE and ghost 8.2 to create the image.  It was just a typical:

Local -> Disk -> To Image

I then selected the source (1TB drive) then the destination, 500G drive.  The total data that I had was approx. 770GB...using high compression it fit on the 500G drive.

Now, i'm trying to do the reverse:
Local -> Disk -> From Image

When I do this, it allows me to select the image file on the 500G drive, the destination drive (1TB drive shows)...but then I get to the screen where you set the partition sizes (Destination Drive Details).  It lists the 3 partitions that were on the old machine, and even has the correct data sizes.   However, ther place for the new size is incorrect.  

Basically, there is this

Part  Type     ID      Desc      Label    New Size   Old Size   Data Siz
1      Primary 07  NTFS Diskload 20002       20002        6694
2      Primary 07  NTFS Diskload X              20002        3565
3      Primary 07  NTFS Diskload X             -992769     770125

The problem is, I can't fill out the new size field properly because the size of the drive is reporting as -992769 (I would imagine because it's too big).  Is there any way around this limitation?

(Note:  I did try accepting the defaults but that failed with not being able to access a cluster -9993823937 (number is not exact, it was a cluster location .... also, sorry the columns aren't lining up)

I'm with you now. I failed to notice this was page 2 of a thread and that's why I was confused.

No clever answers but why don't you try restoring the image from DOS instead of BartPE and see if the negative drive size is fixed. If you don't have ghost.exe then I'm stumped.

No luck there, either, i'm afraid.  I have the same problem.

I hope the DOS men will be along shortly.

A thought. Why not put both HDs in the same computer and do a Disk to Disk clone with Ghost.

Because it's a 500G External USB Hard Drive :)

As for the disk to disk clone, we can't get the other array into the other machine, so there is no way to do a direct link between the drives.

drazzst


Quote:

The image process worked just fine.

Well, not until you run the image *Integrity* check and it passes--did you do that?


Quote:

I used BartPE and ghost 8.2 to create the image.

As in all things computer--you have to be anally specific and correct--computers do not accept *almost* accurate input!  You are using *ghost32 v8.2*!  *ghost 8.2* is the DOS only version of Ghost--only the 32-bit version of Ghost (ghost32) will work in BartPE!

Why are you not using Ghost 10 to perform the image creation to the USB HDD, and then use the Ghost 10 Recovery Disk to restore the image from the USB HDD on the other system?


Quote:

As for the disk to disk clone, we can't get the other array into the other machine, so there is no way to do a direct link between the drives.

What is the problem here--you disconnect items you do not need that are preventing you from hooking up the HDD's you need for the immediate process, you hook things up long enough to do the operation, disconnect what is no longer needed, reconnect what you need--and re-boot once you're ready.

What *other array*?


Quote:

I've imaged a monster drive...770GB, Because it's a 500G External USB Hard Drive

Maybe the 500 G external can not function properly with that much data being stored to it--might require some *free space* for breathing room!  But ...


Quote:

but then I get to the screen where you set the partition sizes (Destination Drive Details).  It lists the 3 partitions that were on the old machine, and even has the correct data sizes.   However, ther place for the new size is incorrect

That strongly suggests that there is a compatibility issue if Ghost32 is listing the sizes incorrectly--maybe Ghost32 just is not compatible with HDD's of that size--anybody know if there are *size* limitations for Ghost32?!

Well, not until you run the image *Integrity* check and it passes--did you do that?

After I read these forums, that was the first thing I did, and yes, it passed.  :)

As in all things computer--you have to be anally specific and correct--computers do not accept *almost* accurate input!  You are using *ghost32 v8.2*!  *ghost 8.2* is the DOS only version of Ghost--only the 32-bit version of Ghost (ghost32) will work in BartPE!

Actually, i didn't realize that, but the DOS version did the same thing.

Why are you not using Ghost 10 to perform the image creation to the USB HDD, and then use the Ghost 10 Recovery Disk to restore the image from the USB HDD on the other system?


Hmm...good question, and quite possibly the answer.  The last research that I did said something about this.  I'm not a ghost expert, so I never thought about a ghost 10 recovery disk.  I will look into this.

What is the problem here--you disconnect items you do not need that are preventing you from hooking up the HDD's you need for the immediate process, you hook things up long enough to do the operation, disconnect what is no longer needed, reconnect what you need--and re-boot once you're ready.


Unfortunately, I can't go into details, but with the type of setup we have, I can't do it this way.  

What *other array*?
Destination of the image


Maybe the 500 G external can not function properly with that much data being stored to it--might require some *free space* for breathing room!  But ...


This could be, but there is actually somewhere around 50G of free space still on the 500G.  I haven't seen any performance issues in any web documentation or google search for this.

That strongly suggests that there is a compatibility issue if Ghost32 is listing the sizes incorrectly--maybe Ghost32 just is not compatible with HDD's of that size--anybody know if there are *size* limitations for Ghost32?!


This is what I am worried about...but, Ghost does actually see the drive size correctly, and I've read that GSSv1.1 may actually help to address this...and by chance I think we have that in a different department (fingers crossed)

All, thank you for the help so far.  I'm putting this on hold until Monday.  Any further thoughts are greatly appreciated and I will try these suggestions on Monday.

Thanks for being here.

Jason