Hi...thanks for being here. I'm in the Macrium Reflect Free stage and will likely purchase this week from them. However after creating my emergency disk USB Flash, being flipped to Macrium 6 and then imaging to a different external hard drive, my first differential failed. I don't know how to massage the program to trigger manually a fresh differential backup?...or is that even possible? So in the few days since it failed, I see no further attempt on the part of the program to try to run the differential backups again and of course none of my daily changes are being saved. I'm really new at this but I'm literally stuck. Do I need to initiate a new Image and let the program take me thru the steps of selecting the Differential Plan (template) again? Or, do I need to just cool it and make the purchase of the licensed program and proceed with their help? Thanks for your reply!
The LOG should describe the failure... what might it have been? ...and if you have a successful FULL, even without a defined definition, you should be able to take another DIFF without incident. The FULL should show up under the RESTORE TAB... SELECT it then select "Other actions/Create Differential." PS- I would never BUY a program that hasn't worked successfully for me in a TRIAL/FREE mode. Let's fix it first.
Terrific! I ran it as of today and bingo...there it was. Don't know why it failed on the first try. Does this forum make provision to add snapshots (M/S Snippets)? Kudos!
Hi, I'm having a similar problem, and run into it on occasion and have never known what causes it or how to remedy it. Usually a full image backup gets things back on track. What is happening is, apparently, Reflect is getting confused on what Differential it is trying to do. First, the details: Win 7 Ult x64 Reflect v5 (latest build) (can't use V6 because it doesn't support XP Pro SP2 and I still have two biz machines running it) Backup sets on a disk in a USB multidisk enclosure. Had some problems with that enclosure recently, but chkdsk finds no errors. But did a differential yesterday (unscheduled, following one done earlier that morning), and it ran without issue. The differential this morning failed with this error: Image ID = DAFD683EBA35FB5D Backup definition file: {the usual thing here} Backup Aborted! - Error reading Image file Now, every Diff I run on this set gives the same error, but with a different Image ID every time. What happens when this occurs is that the Image ID doesn't match any of the image sets I have on disk, and I keep a set of 10 weekly fulls with associated daily Diffs. Every time I run the Diff scheduled task, I get the same error, but a different Image ID, never one that matches any on disk, or the latest, which I've been told by Nick is what Reflect does (i.e., it searches the list of files in the set and builds on the most recent one). That is not happening here. To make matters worse, the Diff I did midday yesterday now shows corrupt when I try to mount it (which had a rather odd file name like 'IMAGEID1-04-04.mrimg'; note the '1' at the end of the IMAGEID and that the 04-04 backup already existed - it should have been 06-06), along with the one two days earlier which completed fine. So, I can believe that perhaps the files got corrupted with the enclosure problems, but after deleting the corrupted Diffs, that doesn't really explain why Reflect won't created a new Diff using the latest Image ID and and next increment number. Has anybody experienced this sort of 'confusion' within Reflect before? There is a Registry entry at HKU\{SID}\Volatile Environment which lists many Reflect parameters of jobs recently run, which shows the correct Filecount for the most recent set, along with the correct path/filenames in the set (even excluding the two files that I deleted which were corrupt), but in that same dataset, the IMAGEID listed is completely random, unrelated to the latest set, or any of the IMAGEIDs in the filenames listed just prior, or any other set on disk. I tried changing the IMAGEID key value, but apparently this is log type data that is written by Reflect after the job has run (i.e., the latest data isn't used by the current running job). I really would like to know how to 'reset' Reflect to correctly create a new Diff for an existing set once this confusion (and repeatedly failed backup attempts) begins. BTW, the File Diffs for a differe set of disks and backups worked fine this morning, to a different disk in the same enclosure. Any ideas would be appreciated. Cheers, Griz
