On 2/19/2024 6:17 PM, sticks wrote:
I've got three systems now set up to do weekly backups in the middle
of the night. All Win 10, and all using Macrium version 8.0.7783.
The two that belong to other people have been waking up and doing the
full backups just fine. In the morning the computer is back in sleep
mode, and the new backup is in the desired location.
Mine, no such luck. All three had new internal spinners that are the
backup destination drives. All can do manual backups "now", and work
fine in windows explorer. On mine, I checked last week and sure
enough, the "Wake the computer to run this task" button was checked.
Last week it tried to begin right after I woke it up in the
afternoon. Today, same darn thing, and button is still checked.
I'll have to check later to see if there are any Macrium or Windows
log files that might show something, but anybody have any ideas what
might be causing this system to not wake up and do the backup imaging?
I may have figured this one out.
I ran the command powercfg -waketimers, and yes it was there and looked good. I then remembered the Windows power setting on allowing wake
timers and went into the advanced setting under sleep/allow wake timers
and sure enough it was set to "disabled". I enabled it, applied changes
and clicked OK. I'm not going to change the schedule in macrium, but
will just wait till next Monday and see if the overnight backup worked
with the change. Fingers crossed.
sticks <wolverine01@charter.net> wrote:or run Macrium with a batch and the run that batch by the Task Scheduler.
On mine, I checked last week and sure enough,
the "Wake the computer to run this task" button was checked.
That sounds like an attribute in an event defined in Task Scheduler.
Macrium doesn't use Task Scheduler. It uses its own schedular service.
Run services.msc, and check for the:
Macrium Service
"Provides scheduling and communication services for Macrium Reflect and associated products. This is a required service that should not be
disabled or turned off."
What is the Startup state of this service? Should be Automatic.
Macrium creates the backup definition files (<name>.xml). You can use
the CLI (command-line interface) to Macrium Reflect to run the backup
job with an event in Task Scheduler, but why? When using Task
Scheduler, the event must be configured to run under the SYSTEM Windows account to ensure it has the privileges it needs, and eliminates pausing
at a prompt for a password. If you don't run under the SYSTEM account,
you have to save the login credentials in the Task Scheduler event;
however, if you're using a Microsoft account in Windows instead of an
offline account, Task Scheduler doesn't yet understand how to apply
those login credentials to an MS Windows account. That means you have
to run under your MS account while it is active (you've logged in, and
left your MS Windows account running).
I remember long ago running the XML script files from the command line specified in Task Scheduler, because Macrium's scheduler was missing
many options available for events in Task Scheduler. Macrium improved
the option set in their scheduler service, so I stopped using Task
Scheduler. Also, there was something about editing the event in Task Scheduler (which, in effect, creates a new event) would prevent Reflect
from running that script. I had to edit the event in Refect, and have
it create the Task Scheduler event. Was easier to use the Macrium
scheduler service while eliminating stepping over my feet trying to
manage the backup job events in Task Scheduler.
In the toolbar, click on Defaults, and look under the Schedule Settings
tab of Defaults and Settings dialog. Which scheduler is selected?
Macrium or Task Scheduler?
Under there, which account is selected under which to run the backup
job? If username and password are specified, you must use a local
(offline) account to run the backup job. If you specify an MS account,
Task Scheduler doesn't know how to handle the login credentials for an
MS account, only for local accounts. As I recall, in the event in Task Scheduler, when you try to enter the login credentials for an MS
account, Task Scheduler will puke with an error. You can specify an MS account in the event, but that MS account has to be currently logged in
when that event runs, so login credentials are not asked for. If
Reflect's default scheduler settings has "Use the Windows SYSTEM account
to run scheduling tasks" then you need to supply login credentials.
However, you do need to run Reflect under a Windows account with admin privileges to select SYSTEM as the account under which backup jobs run.
When you right-click on an XML script you created for a backup job on
the main screen -> Create Backups tab -> Definition Files sub-tab, and
select select Advanced Options from the context menu, the categories for per-job advanced settings is less than you see by going to Defaults in
navbar in the main screen. There are more default settings used for
every backup job versus a smaller subset of advanced settings for each
backup job. You can override just some of the default settings with the per-job advanced settings.
Last week it tried to begin right after I woke it up in the afternoon.
Today, same darn thing, and button is still checked.
I'll have to check later to see if there are any Macrium or Windows
log files that might show something, but anybody have any ideas what
might be causing this system to not wake up and do the backup
imaging?
Yes, Reflect has logs, plus the job status will tell you if the job ran
or not. For a quick summary, you can select Create Backups at the main screen, and select the Scheduled Backups tab. There you see the job
types you defined. I have 3 there, because I defined a GFS (Grandfather Father Son) scheme of full monthly, differential weekly, and incremental daily job types. The display there will show the backup job's name, and underneath are the backup types defined for it. Pick on (for me, I see
Full, Differential, and Incremental). You then see job status in the
History pane. It's one way to filter which job types you want to view
for that backup script.
On the Create Backups tab at the main screen, right-click on a
Definition File to show its context menu, hover over View Backup Logs in
the context menu, and select what to view. Or, more simply, back at the
main window in the "Create Backups / Existing Backups / Logs" tab bar,
just click on the Logs tab. ALL will show them all, but maybe it's just
a particular backup type that is failing. Logs showing a successfully completed backup job will have a green circled checkmark icon. I
haven't had a failed backup job in so long that none are shown with a different icon, so my guess is a red X is shown. You can double-
click on any log to see more details.
sticks <wolverine01@charter.net> wrote:
On mine, I checked last week and sure enough,
the "Wake the computer to run this task" button was checked.
That sounds like an attribute in an event defined in Task Scheduler.
Macrium doesn't use Task Scheduler. It uses its own schedular service.
Run services.msc, and check for the:
On 2/19/2024 9:07 PM, sticks wrote:
On 2/19/2024 6:17 PM, sticks wrote:As long as the images are inside your PC they are not backups but copies.
I've got three systems now set up to do weekly backups in the middle
of the night. All Win 10, and all using Macrium version 8.0.7783.
The two that belong to other people have been waking up and doing the
full backups just fine. In the morning the computer is back in sleep
mode, and the new backup is in the desired location.
Mine, no such luck. All three had new internal spinners that are the
backup destination drives. All can do manual backups "now", and work
fine in windows explorer. On mine, I checked last week and sure
enough, the "Wake the computer to run this task" button was checked.
Last week it tried to begin right after I woke it up in the
afternoon. Today, same darn thing, and button is still checked.
I'll have to check later to see if there are any Macrium or Windows
log files that might show something, but anybody have any ideas what
might be causing this system to not wake up and do the backup imaging?
I may have figured this one out.
I ran the command powercfg -waketimers, and yes it was there and
looked good. I then remembered the Windows power setting on allowing
wake timers and went into the advanced setting under sleep/allow wake
timers and sure enough it was set to "disabled". I enabled it,
applied changes and clicked OK. I'm not going to change the schedule
in macrium, but will just wait till next Monday and see if the
overnight backup worked with the change. Fingers crossed.
Use external destinations and disconnect when not being used.
Move the spinner to external USB docking station
On mine, I checked last week and sure enough,
the "Wake the computer to run this task" button was checked.
Last week it tried to begin right after I woke it up in the afternoon.
Today, same darn thing, and button is still checked.
I'll have to check later to see if there are any Macrium or Windows
log files that might show something, but anybody have any ideas what
might be causing this system to not wake up and do the backup
imaging?
I've got three systems now set up to do weekly backups in the middle of
the night. All Win 10, and all using Macrium version 8.0.7783. The two that belong to other people have been waking up and doing the full
backups just fine. In the morning the computer is back in sleep mode,
and the new backup is in the desired location.
Mine, no such luck. All three had new internal spinners that are the
backup destination drives. All can do manual backups "now", and work
fine in windows explorer. On mine, I checked last week and sure enough,
the "Wake the computer to run this task" button was checked. Last week
it tried to begin right after I woke it up in the afternoon. Today,
same darn thing, and button is still checked.
I'll have to check later to see if there are any Macrium or Windows log
files that might show something, but anybody have any ideas what might
be causing this system to not wake up and do the backup imaging?
or run Macrium with a batch and the run that batch by the Task Scheduler.
On 2/19/2024 8:50 PM, Zaidy036 wrote:
On 2/19/2024 9:07 PM, sticks wrote:
On 2/19/2024 6:17 PM, sticks wrote:As long as the images are inside your PC they are not backups but copies.
I've got three systems now set up to do weekly backups in the middle
of the night. All Win 10, and all using Macrium version 8.0.7783.
The two that belong to other people have been waking up and doing
the full backups just fine. In the morning the computer is back in
sleep mode, and the new backup is in the desired location.
Mine, no such luck. All three had new internal spinners that are
the backup destination drives. All can do manual backups "now", and
work fine in windows explorer. On mine, I checked last week and
sure enough, the "Wake the computer to run this task" button was
checked. Last week it tried to begin right after I woke it up in the
afternoon. Today, same darn thing, and button is still checked.
I'll have to check later to see if there are any Macrium or Windows
log files that might show something, but anybody have any ideas what
might be causing this system to not wake up and do the backup imaging?
I may have figured this one out.
I ran the command powercfg -waketimers, and yes it was there and
looked good. I then remembered the Windows power setting on allowing
wake timers and went into the advanced setting under sleep/allow wake
timers and sure enough it was set to "disabled". I enabled it,
applied changes and clicked OK. I'm not going to change the schedule
in macrium, but will just wait till next Monday and see if the
overnight backup worked with the change. Fingers crossed.
They are full disk images of the boot drive stored on a separate spinner
in the case something gets corrupted, deleted, lost, or the drive fails.
 I am failing to see the difference in terminology that matters?
Use external destinations and disconnect when not being used.
Macrium is loaded on the boot drive, and has to write to something. I
don't see where it makes any difference if that drive is is internal or
a USB device. However, I have told the kid he should also be copying
the backup images to an external drive when he can. That's what I do, 1 working and two backups. Of course since he has to buy that one so it
might be a while. ;-)
Move the spinner to external USB docking station
I used to use two USB storage drive for my backups, but the speed is so
much better on the internal drive I choose to change mine to that too. I still back that up on a USB drive, but see no reason to eliminate the internal spinner. You've just suggested doing it, but haven't really
given a reason for doing so.
---snip---
On 2/19/2024 10:52 PM, sticks wrote:
On 2/19/2024 8:50 PM, Zaidy036 wrote:
On 2/19/2024 9:07 PM, sticks wrote:They are full disk images of the boot drive stored on a separate spinner
On 2/19/2024 6:17 PM, sticks wrote:As long as the images are inside your PC they are not backups but copies. >>
I've got three systems now set up to do weekly backups in the middle >>>>> of the night. All Win 10, and all using Macrium version 8.0.7783.I may have figured this one out.
The two that belong to other people have been waking up and doing
the full backups just fine. In the morning the computer is back in
sleep mode, and the new backup is in the desired location.
Mine, no such luck. All three had new internal spinners that are
the backup destination drives. All can do manual backups "now", and >>>>> work fine in windows explorer. On mine, I checked last week and
sure enough, the "Wake the computer to run this task" button was
checked. Last week it tried to begin right after I woke it up in the >>>>> afternoon. Today, same darn thing, and button is still checked.
I'll have to check later to see if there are any Macrium or Windows
log files that might show something, but anybody have any ideas what >>>>> might be causing this system to not wake up and do the backup imaging? >>>>
I ran the command powercfg -waketimers, and yes it was there and
looked good. I then remembered the Windows power setting on allowing
wake timers and went into the advanced setting under sleep/allow wake
timers and sure enough it was set to "disabled". I enabled it,
applied changes and clicked OK. I'm not going to change the schedule
in macrium, but will just wait till next Monday and see if the
overnight backup worked with the change. Fingers crossed.
in the case something gets corrupted, deleted, lost, or the drive fails.
I am failing to see the difference in terminology that matters?
Use external destinations and disconnect when not being used.
Macrium is loaded on the boot drive, and has to write to something. I
don't see where it makes any difference if that drive is is internal or
a USB device. However, I have told the kid he should also be copying
the backup images to an external drive when he can. That's what I do, 1
working and two backups. Of course since he has to buy that one so it
might be a while. ;-)
Move the spinner to external USB docking station
I used to use two USB storage drive for my backups, but the speed is so
much better on the internal drive I choose to change mine to that too. I
still back that up on a USB drive, but see no reason to eliminate the
internal spinner. You've just suggested doing it, but haven't really
given a reason for doing so.
---snip---
If you do not copy the image externally how would you feel if your PC
was flashed by lightning or stolen or destroyed by fire or locked up by
a ransom demand?
What you call a backup is an internal copy until it is further copied externally and disconnected and stored safely.
The time it takes to make an external image is immaterial if done using
a unattended batch while you are sleeping. Mine runs once a week using Macrium to an external HDD and full partition images(SSD C: 212GB, HDD
D: 131GB & F: 191GB used) take a total less than 100 minutes using a USB
3 port.
Edit the script (XML file)
that Reflect creates to define a backup job. At the end of the script,
add commands to copy the backup files to another location, ...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 418 |
Nodes: | 16 (3 / 13) |
Uptime: | 33:00:08 |
Calls: | 8,807 |
Calls today: | 3 |
Files: | 13,304 |
Messages: | 5,971,143 |