![]()
[<<]Message[>>] [<<]Author[>>] Subject [<<]Thread
Number : 5468 Date : 2003-09-04 Author : Kan Yabumoto Subject : XXCLONE: backup operations Size(KB) : 5
Freedog1978 wrote: > Hi... I was just wondering if the target volume needed > to be totally blank and any existing partitions removed > from it before cloning. XXCLONE works whether or not there are files in the target volume. However, the treatment of the existing directories and files depends on which of the backup options and also on what directories the files resides. Garry responded: > Xxclone needs one Primary partition available on the > target drive although you can use either a primary or > extended partition as the destination. I've only tested > with a primary partition as the destination. XXCLONE allows the target volume to be pretty much in any volume. It does not even distinguish NTFS or FAT. That is, you may clone a FAT source to an NTFS target, or vice versa. It also allows pretty much any partition (Primary or in extended partition) to be the target. ============================================== We should have provided detailed explanation about the behavior of the program with the different options. 1. (Full backup) 2. (Incremental backup) 3. (Incremental backup on Windows essential files only) Note the above options come with the transfer of the system registry files. 4. (No backup) Transfer of the system registry files. 5. (No backup, and no system registry transfer). Note the all of the above options come with "bootification" (the volume will be initialized to become bootable). Furthermore, whether the existing files will be deleted or left untouched will depend on which of the first 3 options that you choose. Both Option 1 (Full backup) and Option 2 (Incremental backup) will affect the entire volume (the root directory). Option 3 (Windows Essential files) will affect the windows directory (represented by %SystemRoot% in NT/2K/XP) and the "Profile" directory (typically it is C:\documents and Settings\ in 2K/XP and C:\winnt\profile\ in NT4). If the existing files reside in the directory mentioned in this paragraph, they will be either zapped, overwritten or left-alone, depending on the settings. It is easier to see them using XXCOPY's jargon, 1. xxcopy c:\ d:\ /KS/H/E/R/ZY (/CLONE/BO) 2. xxcopy c:\ d:\ /KS/H/E/R/BI/ZY (/CLONE) 3. the following two directories are cloned (/CLONE) C:\windows\ C:\Documents and Settings\ In case 1, the pre-existing files will always be either deleted or overwritten (but will not be left alone). In case 2, the pre-existing files will be left untouched only if there is the counterpart file/directory in the source volume that has the same file size and timestamp, otherwise, they will be either deleted or overwritten. In case 3, the pre-existing files will be totally untouched if they reside in a directory which is not in c:\windows\ or c:\Documents and Settings\. Otherwise, the treatment is the same as in Case 2. ========================================================== In the case of XXCOPY, the /ZY operation takes place as each directories are processed. In the case of XXCLONE, the /ZY operation will be processed at the beginning before the file copying takes place. This ordering makes sure that the maximum amount of space will be fully utilized (the XXCOPY scheme may encounter a "disk-full" condition in a rare circumstance where a large file to be deleted won't be tested near the end). ========================================================== BTW, I may have to explain the relationship between the two products, XXCLONE and XXCOPY. Although XXCLONE is now introduced as a new product, it does not include all the features that XXCOPY provides. They are more or less complimentary in their role in the file management operation. XXCLONE's emphasis is to make the target volume bootable under any conditions. As a matter of fact, our original goal in XXCLONE design was to handle only the bootability issue which was lacking in XXCOPY. So, the first three options provided in the setting up page are really a "bonus" step for user convenience. That is, experienced XXCOPY users will find nothing new in XXCLONE in the bonus step (except that now, XXCLONE supports Unicode-named files/directories). Kan Yabumoto ========================================================= >--- In xxcopy@yahoogroups.com, "freedog1978" wrote: > > I have a 120 gig that I bought and have in now as a slave > > and have it partitioned into 4 seperate 30 gig partitions. > > All of which have some data on them, but not too much that > > moving is a problem. > >Although I have tested Xxclone, I'm not totally familiar >with all the ins and outs. Certainly the full backup option >will delete extra files on the destination. I'm fairly sure >the incremental backup option leaves existing files on the >destination partition intact but I suggest you play it safe >and move anything you want to keep onto a partition other than >the target. Although I haven't had any critical failures in >testing on an NT system, you'd do well to heed Kan's warning >that the destination drive may become unreadable. If you've >got data that you absolutely cannot afford to lose, make a >backup first. > >Xxclone needs one Primary partition available on the target >drive although you can use either a primary or extended >partition as the destination. I've only tested with a primary >partition as the destination. > >Garry
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.