[SOLVED] Cloning my SSD as backup for transfer.

chancemitchell

Reputable
Aug 9, 2016
93
9
4,645
I just bought a 1TB WD_Black SN750 NVMe SSD to take on my primary drive for my current 500gb SATA Samsung PRO. The SATA drive was almost full and I wanted to jump up to a larger drive and use the SATA for like COD or something. I am going to use Macrium reflect and a list of instructions I found from this forum but before I do that I would like to verify I have my OS and files backed up correctly. Is it appropriate to use Macrium Reflect and just clone my drive over to my 8TB HDD as a backup for future need or will that mess with me later when booting from my new drive? My 8TB HDD is literally just empty space that I don't use for much so I figured having a cloned version of my OS and whatnot would be useful if I ever have an issue.
 
Solution
Don't clone to the 8TB drive
Make an image file on the 8TB drive.
An image file has everything in it to make a clone....but it's just a file.
This way it can't "mess with me later when booting from my new drive? " because it won't be bootable.
As above...not clone, but rather Image.
That encapsulates the whole current drive in a single file. xxxxx.mrimage.

Later, if you need it, you boot from a Macrium Rescue USB that you've already created (hint hint) and tell it where that image is, and what drive to apply it to.
That concept is the whole basis for my backup routine.

My 'Images" get updated every night. One series per physical drive.
 
As above...not clone, but rather Image.
That encapsulates the whole current drive in a single file. xxxxx.mrimage.

Later, if you need it, you boot from a Macrium Rescue USB that you've already created (hint hint) and tell it where that image is, and what drive to apply it to.
That concept is the whole basis for my backup routine.

My 'Images" get updated every night. One series per physical drive.
I am following your post from someone else's thread. The only difference in my scenario is that I'm transferring from SATA to m.2. So essentially the last point about swapping the SATA cables position at the end is null?
 
I unplugged my SATA SSD alongside the already unplugged HDD and booted. My OS came up quickly and I logged in. Everything was as normal aside from a Wallpaper App now prompting that I never use anymore. I went to (C:) Properties and it says 125 GB Free of 465... The Hardware says WD now yet it isn't showing the 1TB capacity that it did when I chose it in Macrium?
 
Please show us a screencap of your Disk Management window.

You were probably using an older version of my steps.
I've recently revised, and you can manipulate the size of the resulting partition on the target drive, directly in Macrium.

If OK, redo it the clone. Pay attention to the middle part here:
-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive

If you are going from a smaller drive to a larger, by default, the target partition size will be the same as the Source. You probably don't want that
You can manipulate the size of the partitions on the target (larger)drive
Click on "Cloned Partition Properties", and you can specify the resulting partition size, to even include the whole thing

Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------