nlinecomputers
Well-Known Member
- Reaction score
- 8,600
- Location
- Midland TX
Did you follow the instructions on my link? It is NOT obvious from a screenshot how to do this. This is very much an "RTFM and follow the directions exactly" procedure.
Did you follow the instructions on my link? It is NOT obvious from a screenshot how to do this. This is very much an "RTFM and follow the directions exactly" procedure.
That'll be due to that last partition. Reflect doesn't know which partition to resize; it will only resize the last partition which, in this case, can't be resized. If the last partition isn't needed, just unselect it and try again.
IIRC, what you need to do if the last partition is needed is to unselect it, click 'copy selected partitions' then click 'Restored partition properties' and resize the second partition, just enough to make room for the last partition. You should then be able to copy (drag) the last partition over.
14 steps? I can RTFM as well as the next but that seems excessive and I was looking for something that handled the job a bit more streamlined.
What you ask for really isn't possible as it takes human judgment to decide which partitions are going to be cut down.Even I don't know if I need the past partition and if I have to start manually sizing, fitting and moving partitions then this isn't the software I'm looking for.
I'm familiar with 4-5 imaging/cloning software programs but haven't found one that will clone down from an image.
What you ask for really isn't possible as it takes human judgment to decide which partitions are going to be cut down.
I'm not sure you'll find what you're looking for in that case. When there's multiple partitions involved, at the very least the software will need to prompt you to decide which partition(s) you'd like to reduce.Even I don't know if I need the past partition and if I have to start manually sizing, fitting and moving partitions then this isn't the software I'm looking for.
Acronis does this but yes you need to get your hands dirty and manually select which partition and to what size.
The logical choice for cloning would be true image.we can even start with the free one available from your favorite hard drive manufacturers support section.
Just a WAG, but a disk is random access storage – empty space can be easily skipped over; an image is a 'serial read' thing – start at the beginning, decompress and keep going to the end. A compressed image won't have easily identifiable empty spaces.Disk downsize cloning is a couple of clicks and handles the partition resizing automatically. Not sure why it should be so tough with an image.
FSArchiver is a system tool that allows you to save the contents of a file-system to a compressed archive file. The file-system can be restored on a partition which has a different size and it can be restored on a different file-system. Unlike tar/dar, FSArchiver also creates the file-system when it extracts the data to partitions.
Just a WAG, but a disk is random access storage – empty space can be easily skipped over; an image is a 'serial read' thing – start at the beginning, decompress and keep going to the end. A compressed image won't have easily identifiable empty spaces.
That's reasonable, but it's a choice that must be made at the time of making the image.Depends on the image type; Reflect can do either
Just a WAG, but a disk is random access storage – empty space can be easily skipped over; an image is a 'serial read' thing – start at the beginning, decompress and keep going to the end. A compressed image won't have easily identifiable empty spaces.
If you are grabbing just an image and not a full-on clone, this is an excellent program to use. Recently I've loaded some units and then grabbed "just" the images for backup (off site) if needed. I love Clonezilla.Clonezilla has an expert option to ignore the disk size IF you resize the file system down to a smaller size before cloning:
What you ask for really isn't possible as it takes human judgment to decide which partitions are going to be cut down.
NOTE:
A common misconception on this message is the amount of space that is needed to restore. The space that is looked at is not the "Used space" in the backup but the actual "Volume size" that was backed up. This is a screen shot of the image being restored before the shrink it would need a 2 TB volume to restore even though only 14 GB is used. Once the Volume is shrunk with the above steps the Volume Size should change to reflect the volume size now needed to restore.
![]()
Limitations:
This section discusses limitations that can affect the amount of space that you will be able to clear out using the shrink volume process.
Limitations: The Shrink Process itself.
This shrink option we supply is performed using the Microsoft shrink utility, and thus has the same performance characteristics. See Microsoft website for further details: TechNet - Shrink A Basic Volume
Microsoft advises that:
"When you shrink a partition, unmovable files (for example, the paging file or the shadow copy storage area) are not automatically relocated and you cannot decrease the allocated space beyond the point where the unmovable files are located. If you need to shrink the partition further, move the paging file to another disk, delete the stored shadow copies, shrink the volume, and then move the paging file back to the disk."
Limitations: Disk Fragmentation.
The volume can only be shrunk to the last track where data exists on the volume (See directly above). If your disk is highly fragmented, the ability to shrink your free space will be restricted. If at all possible, it is highly recommended that you perform an extensive defragmentation of the volume to be shrunk BEFORE you take the ShadowProtect backup. Please note that in order for a defrag to be successful, it requires 15% free space on the disk.
Limitations: Mirror Master File Table.
A backup copy of the Master File Table (MFT) is normally located at about the mid-point of the volume. This will therefore limit the amount of the shrink to half of the disk size (if you have less than 50% data on your volume). For example, a freshly de-fragmented 300GB volume that contained 7GB of data, when shrunk by this process achieved a new volume size of 146GB (approximately 50%).