How big is your swap file? For speed, I'd keep that on the SSD if you can possibly spare the room.
It should have been a clone, then you use recovery software on the cloned copy, not original.
Reason being is, xcopy can and will fail, and what is worse is that it can have silent errors as well.
Right, clone is basically sector by sector copy, and you would use ddrescue to overcome sectors that are too badly corrupted to have valid data anymore.I'm new to this whole paradigm of 'clone' and 'recovery software used on the clone' on the PC, adding a level of discomfort over the tried and true copying.
To me, clone means sector-by-sector copy of a drive, not something you use recovery software on.
Right, clone is basically sector by sector copy, and you would use ddrescue to overcome sectors that are too badly corrupted to have valid data anymore.
Once that clone is done, you basically have all files around, but, the structure could be damaged, that is why you run recovery software on the cloned copy, to get as much files back as possible.
You don't do this on the original, since you don't want to cause more bad blocks by repeatedly writing to that HD/device again & again.
This is what all professional services do, they immediately clone everything over, and try to recover as much as possible. If they can't clone, then they start operating on said device to get it to read data again, and then clone ASAP.
Sharing violation is why I always clone using a boot drive other than Windows.
I don't have a boot drive other than Windows, but got around the error.