+x

 

BobUlius - 10 April 2021 12:46 AM

PROBLEM: Looking at the scheduled, the time for the one running is correct as the path. But  time and path are wrong for the other one changed that has not yet run.

I changed what I mentioned above in the Backup definition files. Did I need to do something else? Perhaps to the scheduler?

I'm not sure what "the other one" means in this context.  If you only edited schedules, then the path shouldn't have changed.  And you can't have different paths for different schedule types (Full/Diff/Inc) within the same definition file.

Got it. Clicking one of the backups in the Image changes the referenced file. Its ok there. Whew

+x

 

BobUlius - 10 April 2021 12:49 AM

MORE:

The top pane for the scheduler on that backup is correct.

Below that it says referenced File and the Image Options there are for the other backup - times and path.

So maybe it is ok. What is the Referenced File?

Screenshots might help at this point....

No that is settled now, thanks. Did not know what Referenced File was or how it changed and it was showing a different set while I selected the name of the set. Changed to proper when Full or Incremental Or Differential was selected. All sorted.

So the  only surprise is that instant full backup. Art least for now. If that completes and I get my incremental to both at the new times tonight, should be good.

Ok, but you still may have stumbled on a bug there.  If the schedule changes somehow caused Reflect to conclude that scheduled backups had been missed, then it would have run the "highest order" missed backup, which in this case would have been a Full.  That would explain a Full starting right after you made the changes. But since that shouldn't really happen in your scenario, I thought it might be worth trying to reproduce in a test environment.  That's why I asked what time it was where you were when you made the change, and also which scheduling engine you're using.  That might make it more likely I can make it happen on my end.

+x

 

jphughan - 10 April 2021 1:07 AM

Ok, but you still may have stumbled on a bug there.  If the schedule changes somehow caused Reflect to conclude that scheduled backups had been missed, then it would have run the "highest order" missed backup, which in this case would have been a Full.  That would explain a Full starting right after you made the changes. But since that shouldn't really happen in your scenario, I thought it might be worth trying to reproduce in a test environment.  That's why I asked what time it was where you were when you made the change, and also which scheduling engine you're using.  That might make it more likely I can make it happen on my end.

OK. I changed from 1:00 AM to 4:00 AM and it was 4:52 PM when the full started.

As far as I know I am using the Macrium scheduler??? I know I had issues of 2 fulls after a daylight savings and I thought there was a change to your scheduler to avoid that. How would I check?

And agreed, seems like a small bug.

Found it. Macrium.

Check Edit Defaults > Schedule to see which scheduler you're running.  EDIT: Saw your new post.  Ok, I'll see if I can trigger it myself.

+x

 

jphughan - 10 April 2021 1:23 AM

Check Edit Defaults > Schedule to see which scheduler you're running.  EDIT: Saw your new post.  Ok, I'll see if I can trigger it myself.

Cool. Again, I changhed retention for 3 to 2 and time to a different run time 3 hours later  for all types of backup. I think the retention change was the culprit.