Yes, I was a little confused. I did understand the difference between an image and a clone. The former being compressed and requiring some program to install in a working condition. The latter is "plug and play." (You may need to change bios settings, though.)
My biggest confusion was over cloning and booting from a cloned USB. Somewhere in the recesses of my memory I recalled that Win7 could not be booted from a USB -- CD's, floppys, hard drive on the same connection (e.g, SATA) would be OK. But, I went and searched Google to be sure. One of the hits was from Intel and several others were from PC "gurus." Here is the Intel quote:
How to enable USB boot in BIOS Windows 7?
- Restart the system into the BIOS.
- Ensure the Boot Mode is set to EFI (or UEFI). This is found in the Boot Options menu.
- Make sure that the USB Boot Priority is enabled.
- Save the changes and exit.
https://www.intel.com › server-products › server-boards
To add confusion, Acronis warns about cloning the System and leaving that disk attached. It claims that can cause a conflict on boot. That part I didn't understand, since the clone should be on a different port/location (e.g., Z) and the boot routine should see C first. But, I am not one to disagree with a real expert.
A potential problem with leaving a clone attached to SATA and the bootablity from USB are the two things I am most uncertain about. Background to that concern:
Disconnecting a drive repeatedly is not something I look forward to doing as I have found that while SATA is fine, sometimes the connection is fragile. That means, I have four Samsung SSD in my PC. One of the RAID 1 pair is "fragile." Out of the blue, it failed a few years ago. I tried it several times and wiggled both plugs, and it wouldn't be recognized (Intel RAID controller). It was under warranty, so I sent it to Samsung. Its service center reported the disk was fine and updated its firmware. About once a year since, that connection fails. I wiggle everything and learned that one has to tell the Intel RAID manager to ignore the problem and mark disk as "good." It is still working about 3 years after that first failure. Its most recent "pseudo-failure" was a few weeks ago, and I installed a new cable for it. It was that event that convinced me of my need to seriously address backups or clones.