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. 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). The differential this morning failed with this error:īackup definition file: \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. But did a differential yesterday (unscheduled, following one done earlier that morning), and it ran without issue. Had some problems with that enclosure recently, but chkdsk finds no errors. 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)īackup sets on a disk in a USB multidisk enclosure. What is happening is, apparently, Reflect is getting confused on what Differential it is trying to do. Usually a full image backup gets things back on track. 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.
0 kommentar(er)
