Backup waiting timer, reboot, no backup starts...


Author
Message
gorillale
gorillale
Junior Member
Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)
Group: Forum Members
Posts: 32, Visits: 80
I stopped the backup that was supposed to start for 30 minutes because a Windows update was just started.

After the restart (2x) the backup no longer started, even after the pauses.

under "Create backup" tab "scheduled backups" says:
Status: "An unexpected error has occurred"
last result: "0x103 error"

In my opinion, if the backup is aborted or suspended, it would have to be run again later without having to start it manually. I couldn't find a setting for it.

Or am I doing something wrong?
Greetings
Andrew
capair45
capair45
Macrium Hero
Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)
Group: Forum Members
Posts: 1.9K, Visits: 18K
Had the scheduled backup actually started and you manually cancelled it or did you delay it for 30 minutes before it started?  I would think that if a scheduled backup has started correctly and subsequently cancelled for whatever reason, it would not start again until the next scheduled time. 

There is an option to run a scheduled backup if it has been missed for some reason (e.g. computer was shutdown).  You can find this option by editing the backup schedule > Conditions and check the box "Run the task as soon as possible after a scheduled start is missed"


Windows 10 Home (22H2)  Build 19045.4046 (Desktop)
Windows 11 Home (22H2)  Build 22621.1992  (Laptop)
Macrium Reflect 8.1.7847



gorillale
gorillale
Junior Member
Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)
Group: Forum Members
Posts: 32, Visits: 80
[Zitat]
capair45 – 27. Oktober 2023 9:32 Uhr
Wurde die geplante Sicherung tatsächlich gestartet und Sie haben sie manuell abgebrochen oder haben Sie sie vor dem Start um 30 Minuten verzögert? Ich denke, wenn ein geplantes Backup ordnungsgemäß gestartet und anschließend aus irgendeinem Grund abgebrochen wurde, würde es erst zum nächsten geplanten Zeitpunkt erneut gestartet. 

Es besteht die Möglichkeit, eine geplante Sicherung durchzuführen, wenn diese aus irgendeinem Grund versäumt wurde (z. B. wurde der Computer heruntergefahren). Sie finden diese Option, indem Sie den Backup-Zeitplan > Bedingungen bearbeiten und das Kontrollkästchen „Führen Sie die Aufgabe so schnell wie möglich aus, nachdem ein geplanter Start verpasst wurde“ aktivieren.
[/Zitat]

win11 update has restarted, Backup (timer 30 min. are not down),
After reboot Backup never starts. i wait 1 hour, an must be start manual.

This checkbox is activated on each backupjob. but not work...

Edited 27 October 2023 10:37 AM by gorillale
Patrick O'Keefe
Patrick O'Keefe
Expert
Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)Expert (876 reputation)
Group: Forum Members
Posts: 601, Visits: 4.1K
Similar problem / different circumstances:  When backups are queued by "Run as soon as ..."  and a reboot happens before they run, their status shows "0x103 error".  I was told by Macrium support that this was the expected behavior.  Perhaps this behavior also applies to the delay timer.  Expected perhaps, but very counterintuitive. 

I think I submitted a Wish List request that this behavior be changed.  Wouldn't hurt to submit another.

BTW, for a delayed execution there's likely no way for Reflect to know how much of the delay had expired when the reboot happened.  If the behavior is changed, the delayed backup would probably have to be queued for "as soon as possible" execution.

gorillale
gorillale
Junior Member
Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)Junior Member (86 reputation)
Group: Forum Members
Posts: 32, Visits: 80
Hi
Thanks for the detailed description.
can I get around this if I use windows sheduler and a script?

regards
andrew
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search