NVMe (M.2) Drive Support (system disk)?
My support just ran out, so I can't ask Acronis directly....
Does anyone know if Acronis is planning support support for NVMe SSD drives? Mine is in the M.2 slot of my motherboard. I typically clone my system disk to a spare SSD in my system as a fail-safe backup.
Just curious if anyone else has some info on this...


- Log in to post comments

Thanks Bobbo_3C0X1,
I had a feeling this would be the process, but was really hoping that True Image would support NVMe natively.
I'm actually just running a complete drive backup to another drive at the moment, accomplishes the same thing but just takes a bit more work to get the backup back on the system drive is something blows up on me...
Thanks again. I may try WinPE in the meantime!
- Log in to post comments

Yeah, for now, WinPE is the only option with Acronis - it's easy though, once the ADK has been downloaded and installed - just be sure it's the ADK 6.0 (Windows 10) and drivers are natively supported. Otherwise, you'll have to use ADK DISM commands to later slip drivers into earlier versions of the WindowsPE. It's easier to just use the Windows 10 ADK though and let Acronis do its thing.
- Log in to post comments

Bobbo_3C0X1,
Can I pick your brain for a moment. I am fairly techie, but new to WinPE and ADK. I am currently downloading the Win 10 ADK and installing it using the defaults. Once it is finished, can you describe the process from there to accomplish a clone using my M.2 NVMe Samsung 950 Pro. (ie. cloning the NVMe drive to another SSD in my system). Just as I would had it been two SATA based drives instead. If you don't have the time or availability, I surely understand! But any help/pointers would be appreciated.
Regards,
bobbl (short for Robert Black)
- Log in to post comments

Bobbl. It should clone the same way. Main thing is to be sure that the bios boot order allows for booting to the ssd if switching drives since each bios has different settings and options. It's also not recommended to leave a cloned drive in the machine after the process is finished, as both drives will then have the same hardware I.d. and can cause issues at boot. To test the clone, you would normally remove the original and place the clone in the same spot before booting. Not possible in this case, so you'd just remove the pcie drive and it should hopefully pick the clone or you'll need to adjust the boot order in the bios if it doesn't.
Personally, I don't clone. I prefer to take a full disk image with all partitions so I have the backup for posterity. I then restore the image to the new drive and remove the old one before booting. It's essentially the same result, but with the added benefit of having the backup to fall back on, just in case. The documentation recommends taking an image before cloning as well. That way, if you accidentally switch the source and destination drives in the clone process... resulting in 2 blank drives... you can restore with your image.
- Log in to post comments

Thanks for this info!
I will give it a shot tomorrow when I have some time to play with it.
Once I clone my system drive, I typically will remove any newly assigned drive letters, and then literally disconnect the SATA cable to the clone. The drive does stay in the system, but does not get hooked up until "all hell breaks loose". As you said, I have just started doing a full backup up the NVMe drive as a regular practice, and have the luxury of leaving it/them on yet another drive in my system - disk space is NOT an issue for me, as I have 5 total drives in my system and 3 of those are 2-4TB each.
The MSI BIOS for boot order has proven to be a bit finiky for me in the past, but have always managed to make things work.
I know a lot of people don't prefer cloning, but I have had great luck with them thus far, and they have saved my bacon more than once in the past couple of years. Very quick recovery time (I start to hyperventilate any time my system is down for long :))!
Once again, thanks for taking the time to soothe this noobs nerves!!
Regards,
bobbl
- Log in to post comments