backup error -- no log file


Author
Message
Frank Esposito
Frank Esposito
Proficient Member
Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)
Group: Forum Members
Posts: 258, Visits: 650
Hello -- If a scheduled back  is canceled via that  pop-up that its about to start, will a log file get created? 
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)
Group: Forum Members
Posts: 12K, Visits: 72K
No, because in that case the job itself never started. That’s a quick test to run.
Frank Esposito
Frank Esposito
Proficient Member
Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)Proficient Member (365 reputation)
Group: Forum Members
Posts: 258, Visits: 650
jphughan - 19 June 2021 4:38 PM
No, because in that case the job itself never started. That’s a quick test to run.


thx for the info

Patrick O'Keefe
Patrick O'Keefe
Advanced Member
Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)
Group: Forum Members
Posts: 428, Visits: 2.4K
Having a Scheduler log (in addition to the backup / restore logs) would be a good idea, though.  Something that mentions backups backups canceled via the popup, things that cause 0x103 errors (which can happen prior to the backup task starting), etc. would be very useful.

I'll put that request in the Wish List if the feature does not already exist.

jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)
Group: Forum Members
Posts: 12K, Visits: 72K
Macrium Task Scheduler does have a log file, but I don’t know of a way to view it from within Reflect.
L. W. "Dan" Danz
L. W. "Dan" Danz
Guru
Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)Guru (1.3K reputation)
Group: Forum Members
Posts: 579, Visits: 6.2K
Is this what you're looking for:




 L W "Dan" Danz, Overland Park KS 
MR v8.0.6786+    Win10.21H2-19044.1889+    Win11.21H2-22000.856+




Patrick O'Keefe
Patrick O'Keefe
Advanced Member
Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)Advanced Member (586 reputation)
Group: Forum Members
Posts: 428, Visits: 2.4K
Sorry for my previous incomplete posting.  I believe I was trying to make 2 point.
  1. If the scheduled task is a Powsershell script (and probably other scripts, too) not entry appears in that history log.
  2. If a scheduled task has been queued but not yet run at time of reboot the Status field in the Scheduler log is set to 0x103 but there is no other indication that the task was not run.  And after the next run of the task - successful or otherwise - all indications of the missed execution are lost.
I believe that any task given the 0x103 status should be requeued rather than flagged as an error, but there should be a permanent entry in a log in either case.


Edited 1 July 2021 4:22 PM by Patrick O'Keefe
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