Scale to Fit -vs- Scale to Target?

[a1pcfixer]

I'm curretly running a 256GB-SSD as my boot drive, and planning on
swapping it out to a bigger 512GB-SSD drive.

Current 256GB-SSD has a 102MB (System|Active| Primary) partition and
the remainder is for the boot drive C:\ (Boot|Page File|Crash Dump|
Primary) partition.

Which should I use in my situation for IFD whole drive Restore?
Scale to Fit?
-Or-
Scale to Target?

I was thinking of using these settings;
1) Align to Target
2) Write Standard MBR code
3) Scale to Target

Win 7 Pro 64-bit w/SP1

Anything I'm missing?
Any suggestions for a better approach?
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 and Windows 7 Service Pack 1 build 7601

[TeraByte Support]

if it's already aligned on the source, no need to use align to target (you
typically use that when changing alignment). Do an entire drive copy (or
restore), scale to fit is typically what I use, but scale to target can be
used (believe the manual details the difference). Don't need write standard
mbr unless you want to ensure the mbr is a standard one. Don't leave both
drives attached during a boot, if you plan on that, use the option to change
disk guid/id's.


"a1pcfixer" wrote in message news:6692@public.image...

I'm curretly running a 256GB-SSD as my boot drive, and planning on
swapping it out to a bigger 512GB-SSD drive.

Current 256GB-SSD has a 102MB (System|Active| Primary) partition and
the remainder is for the boot drive C:\ (Boot|Page File|Crash Dump|
Primary) partition.

Which should I use in my situation for IFD whole drive Restore?
Scale to Fit?
-Or-
Scale to Target?

I was thinking of using these settings;
1) Align to Target
2) Write Standard MBR code
3) Scale to Target

Win 7 Pro 64-bit w/SP1

Anything I'm missing?
Any suggestions for a better approach?
--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 and Windows 7 Service Pack 1 build 7601

[a1pcfixer]

TeraByte,

So all I need is; Scale to Target and nothing else?

I'll be doing a Restore via IFD/IFL with only the new SSD connected, not the
old one.


> if it's already aligned on the source, no need to use align to target (you
> typically use that when changing alignment). Do an entire drive copy (or
> restore), scale to fit is typically what I use, but scale to target can be
> used (believe the manual details the difference). Don't need write standard
> mbr unless you want to ensure the mbr is a standard one. Don't leave both
> drives attached during a boot, if you plan on that, use the option to change
> disk guid/id's.


--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 and Windows 7 Service Pack 1 build 7601

[Brian K]

TeraByte Support wrote:

> scale to fit is typically what I use, but scale to target can be
> used (believe the manual details the difference).



Quoting above message.

[TeraByte Support]

yes, if already aligned and you don't want to change it, and you don't plan
on having both attached at the same time while in windows.

"a1pcfixer" wrote in message news:6699@public.image...

TeraByte,

So all I need is; Scale to Target and nothing else?

I'll be doing a Restore via IFD/IFL with only the new SSD connected, not the
old one.


> if it's already aligned on the source, no need to use align to target (you
> typically use that when changing alignment). Do an entire drive copy (or
> restore), scale to fit is typically what I use, but scale to target can be
> used (believe the manual details the difference). Don't need write
> standard
> mbr unless you want to ensure the mbr is a standard one. Don't leave both
> drives attached during a boot, if you plan on that, use the option to
> change
> disk guid/id's.


--

Jim L.
Using - Virtual Access(OLR)
http://www.virtual-access.org
6.3.0.5 and Windows 7 Service Pack 1 build 7601

[giulia]

TeraByte Support wrote:
> and you don't plan
>
> on having both attached at the same time while in windows.


hi
may i ask a question about the same procedure but without unplug the source drive?
in case i don't want to use the option Change Disk ID and GUIDs , can i use BIBM after the copy/restore ?
what should i do with bibm ? is enough Format the source drive or it's better Delete the 2 partitions (standard windows 7 installation) ?

[TeraByte Support(PP)]

I assume you're just replacing the system drive and want to leave the original (source) drive in the computer for data use.

You could delete the partitions before booting into Windows on the new drive the first time (Windows will usually change the disk signature/ID automatically). Or you could just change the signature (assuming MBR type). It's usually recommended to disconnect it instead so that it remains intact until you know the new drive is booting and working properly. Note that Windows may set the "duplicate" drive offline instead of changing the signature/ID.

[giulia]

TeraByte Support(PP) wrote:

> It's usually recommended to disconnect it instead so that it remains intact
> until you know the new drive is booting and working properly. Note that
> Windows may set the "duplicate" drive offline instead of changing
> the signature/ID.

thanks
may i ask 2 questions?
1)
should i disconnect the source drive only for the first boot ?
after the first boot i can re-connect without issue ?
2)
coping a drive without Change Disk ID and GUIDs ,will preserve windows 7 activation and programs like photoshop cs6?

thanks
best regards

[TeraByte Support(PP)]

1) That's the normal procedure. When you connect the original/source drive later Windows should change the signature so there's not a conflict. If it doesn't it will place the drive offline (you can change it back to online using Disk Management).

2) Possibly. It usually stands a better chance of not causing deactivations because there are fewer changes. However, it's still a different drive.

[userX]

Here is the answer to the same question I had along these lines:

" 'Scale to Fit' will ignore unallocated space at the end of the source drive and scale the partitions to fill the destination drive. 'Scale to Target' will retain unallocated space at the end of the source drive and scale it along with the partitions."
Paul Purviance
TeraByte Support