Scheduled backup did not trigger

Questions about Cobian Reflector
User avatar
cobian
Site Admin
Posts: 460
Joined: 31 Oct 2020, 01:25
Location: Sweden
Contact:

Re: Scheduled backup did not trigger

Post by cobian »

Hmm...interesting. Could you try to create 4 new tasks (the same ones, by cloning), and delete the 10 min event and see if it works as intended? I still think this is the problem.
--
Luis Cobian
Cobian Backup's creator
przemhb
Posts: 16
Joined: 23 Sep 2021, 10:50

Re: Scheduled backup did not trigger

Post by przemhb »

Would it be ok just to decrease those 10m to 10 seconds in the task I already have? Or you prefer I clone those tasks and change the value in the cloned one?
If the delay is indeed causing the issue, than I assume it is safe to reschedule the tasks for today (to not to wait for Monday), isn't it?
przemhb
Posts: 16
Joined: 23 Sep 2021, 10:50

Re: Scheduled backup did not trigger

Post by przemhb »

On the 14th Reflector noticed backups of original tasks, which were scheduled to Monday the 11th, were missed and triggered all of them.

Later I've cloned original tasks and removed the 624 second wait time from the first clone's pre-backup events. After several attempts I've eventually managed to change schedule of those cloned tasks (later more about this).

Later the day Reflector triggered clones 1 & 2 as scheduled and they were processed just fine. Notably backup type of the 1st one was changed to a full, as it was the first time this task was to be run. Tasks 3 & 4 were not triggered.
The next day I have rescheduled the set of clones for a later hour the day. All of them were triggered. The 3rd type was changed to full.

This Monday none of the original tasks triggered as scheduled.
Today I have rescheduled the set of clones a few times, but they weren't fired. No idea why. Nothing in the verbose log.

I've noticed that if you reschedule time and day of a task and move to editing a next task immediately the change is not saved. I've discovered I need to wait until the rescheduled task's properties show new time. Only then I can move to editing an other task.

There's one more thing. I've found in the log a line as follows: "ERR 2021-10-18 18:32:11 An error occurred while creating the monolithic archive: File "E:\work\HPN-1\FW\.git\config\" not found". This is strange as "config" is a file and not a folder. And it was like this for years, as I have not modified the "E:\work\HPN-1\" since September 2020.
User avatar
cobian
Site Admin
Posts: 460
Joined: 31 Oct 2020, 01:25
Location: Sweden
Contact:

Re: Scheduled backup did not trigger

Post by cobian »

I've noticed that if you reschedule time and day of a task and move to editing a next task immediately the change is not saved. I've discovered I need to wait until the rescheduled task's properties show new time. Only then I can move to editing an other task.
Yes, the changes need to be "approved" by the engine and send back.
There's one more thing. I've found in the log a line as follows: "ERR 2021-10-18 18:32:11 An error occurred while creating the monolithic archive: File "E:\work\HPN-1\FW\.git\config\" not found". This is strange as "config" is a file and not a folder. And it was like this for years, as I have not modified the "E:\work\HPN-1\" since September 2020.
Will take a look at that.
--
Luis Cobian
Cobian Backup's creator
przemhb
Posts: 16
Joined: 23 Sep 2021, 10:50

Re: Scheduled backup did not trigger

Post by przemhb »

Yes, the changes need to be "approved" by the engine and send back.
But is it ok for Reflector to drop changes, which were in the process of approving, if user modifies another task in meantime? Shouldn't user been informed to hold with any further modifications or even blocked until previous ones get approved?

What about those cloned tasks, which I rescheduled a few times, but they didn't fired? Am I missing something here?
Post Reply