Win7 clone to be used on Win10 in a vmware environment I basically have 14 images to select from. Rebuilding the system from the Macrium image takes maybe 1/2 hour.Īlso, I can rebuild the system from the state it was on any specific day in the last 14 days. With the OS in the state it was on the day he cloned it several months previous.īut the second drive with the bootable OS led to the initial confusion. He booted up, and the system simply skipped the SSD (due to the bad cable) and booted up from the secondary drive. And left the fully bootable OS on the HDD. He had cloned from HDD to SSD a few months previous. Virus? Windows updates screwing with things?Īfter a couple of days investigation, we discovered that it was simply a bad SATA cable. Desktop wallpaper, files gone, old applications reappearing. My backups are never more than 24 hours out of date.Īnd.I've seen instances where a fully bootable second drive is a bad thing.Ī user here last year had an issue.start the system up, and it looked exactly like it did 6 months ago. I can live with the 20 minutes it would take to resurrect that nightly image off to a new drive. Repeat as time goes on.Īnd yes, you can use a Macrium Full, or Full + Incremental.to restore the whole system as it existed at the moment the image was created.Ī fully bootable second drive serves little purpose, for me. Keep for 2 weeks, and then roll into a FUll image. My main system does an Incremental backup every night. all backed up to a single drive (of sufficient size). I have 3 different PC's.8 different drives. Can you create bootable via incremental schedule?Ī full clone sucks up an entire second drive.įull + Incremental or Differential simply exists in folders on a different drive. I want a fully bootable Solid state drive, not backups per se. What are the pros/cons of incremental versus a full clone of the drive?
0 kommentar(er)
