I felt like this is a twist of the other thread so I am starting fresh. I have used Macrium Pro recovery environment for many years. Using HDDs that are fully LVM on LUKS 100% encrypted - I simply launch the Macrium recovery environment in RAM and create forensic backups. When restores are needed I simply reverse the process and have NEVER had anything go wrong. Lucky I guess but Macrium is good! I am going to use these backups to image my new SSD's after I get them partitioned and ready. Now --- the decision for how to backup the continuing use of my LVM on LUKS systems, because this will be happening on SSD's which move things around on the space. I know the software on the actual SSDs (Crucials) move/remap when sectors get used for awhile. Since things move around how can I restore using images that snapshot the space exactly as when the image was created? Will the Crucial software see the location on my image and then "know" where the new write location is during a restore? Hope that question makes sense. Trying to visualize how a changing SSD space is supposed to be restored from an image taken say 2 months earlier! I have always relied upon Macrium from recovery in RAM and never had issues. LVM on LUKS is a tricky animal to handle with lots of moving parts, but when its closed its easy to forensically snapshot. Will this method still work on SSD's?
@Palancar - the Crucial "move/remap" operations are strictly internal to the SSD (they all do this as part of the "garbage collection" operation of the controller), they do not represent any LBA assignment changes to the OS... as far as the OS is concerned, nothing has changed, not even the unallocated space that hasn't been used yet. SSD restorations will be exactly the same as HDD restorations... there should be no reason to worry. Yes.
Thank you! That is what I was hoping to hear. My stuff is quite private. I don't want to rely on Crucial SED over hardened LUKS for protecting against unauthorized access!
