Hi Overthere,
I'd like to take a backup when my machine is starting up, which isn't necessarily every day. Is ther a way to schedule it on an event like startup?

Thx a lot in advance
Ralf

If you schedule it from Windows task scheduler, "when the computer starts" is one of the options for a trigger in the second step creating a basic task,

Or have Macrium create it, any schedule you like, but using the Windows scheduler.. then edit the task in task scheduler & change the trigger to that.

How you'd do it with the Macrium scheduler I'm unsure, doubtless someone will chime in with how, I've never switched from using the Windows one.

You don't even need to resort to Windows Task Scheduler.  You can do this right from Reflect:

@jphughan you're right. I've been blind, 'cause it's running in German and I just overlooked. Thx a lot :-)
@Beardy thx a lot too for your input.

+x

 

jphughan - 17 May 2022 4:20 PM

You don't even need to resort to Windows Task Scheduler.  You can do this right from Reflect:

I tried "When my computer starts" , but MR doesn't do anything. When choosing "At logon" it works. Any idea what's causing this?

And one additional thing which you may also know: How does MR handle jobs which are interrupted? Often times I just open the notebook for a quick check of sth and the backup job won't finish in this short period. Does MR recognize these attempts on the next startup, delete the files and log it as failed?

I believe “system start” is defined as the OS kernel starting up, such as after a restart, not waking up from sleep or hibernation and therefore possibly not even starting from full shutdown if you have Fast Start enabled, which causes shutdowns to hibernate the kernel. So are you testing that function using an actual restart?

If that doesn’t explain what you’re seeing, are you still using the SYSTEM account for background tasks or did you specify some other user account? Are you certain no background backup has already started from system startup after you log in? Did you check ReflectMonitor to determine that?

Interrupted jobs fail, and failed jobs are not restarted.

I can't say I have really, but the first thing I'd suspect would be fast-startup interfering & would try with it disabled, just to see what happened.

As to your second question, I'd imagine they'd get logged as failed jobs, it's easy to go check the logs on your machine though & then you'd have a definitive answer.
You might try hibernating the machine if you know a backup started, that ought to cause it to simply resume the next time you woke it.