Configuration details:
Dell Latitude 5520 laptop with 11th Generation I7, 16G memory
System only supports S0 low power idle (S1, S2 & S3 sleep modes not supported) see uploaded powercfg image
W10 Pro 20H2, Macrium Reflect 7.3.5758
Backup Source: 512G NVMe
Backup Destination: 1TB microSD card (using build in card reader)
Bitlocker used on both source & destination

Typical I/O performance for manually invoked backups is Read 3+ Gb/s & Write 580+ Mb/s.
Typical times to complete a full backup ~10-12 Minutes, incremental backup ~3-5 Minutes
Implemented a schedule using the Macrium Task Scheduler to perform an incremental every Saturday  6:00am. The job ran when scheduled, but took almost 6 hours to complete. Note that the laptop was on plugged in power during the entire time.

Here is a section from the Macrium Scheduler log...

10/04/2021-06:00:55] RunBackupServiceRoutine: Starting
[10/04/2021-06:00:55] RunBackupServiceRoutine: Job is a scheduled job
[10/04/2021-06:00:55] RunBackupServiceRoutine: IPC CreateProcess:
    NetBIOS: localhost
    Backup Definition: Macrium-Backup-{C8F4050B-B1AA-4388-8CA0-675116AF0FA5}
[10/04/2021-06:00:55] StartNewJob: Launching process '"C:\Program Files\Macrium\Reflect\Reflect.exe" -e -w "C:\Users\JnS_Admin\Documents\Reflect\Backup_to_microSD_on_D.xml" -inc -g {C8F4050B-B1AA-4388-8CA0-675116AF0FA5}' as SYSTEM
[10/04/2021-11:48:36] StartNewJob: executable returned 0
[10/04/2021-11:48:36] StartNewJob: Process complete
[10/04/2021-11:48:36]     Plan update success
[10/04/2021-11:48:36] UpdateBackupJobFinishedStatus: Updating job status
    PlanId: {4B8464DB-000A-4FF4-A597-70C54462C239}
    NetBIOS: localhost
    Status: success
    Description:
[10/04/2021-11:48:36] ServiceQueue: CurrentJobCompletion event received
[10/04/2021-11:48:36] ServiceQueue: Query IQueueManager for next backup job run time
[10/04/2021-11:48:36]

Started  6:00  completed successfully at 11:48 (5 Hours & 48 Minutes!)

A section from the VSS log:

Querying all shadow copies with the SnapshotSetID {47699273-1ff5-472e-b6ce-db24e1ad0072} ...

* SNAPSHOT ID = {49e2db24-1e0e-4ee3-bbcf-fa7195150ef0} ...
 - Shadow copy Set: {47699273-1ff5-472e-b6ce-db24e1ad0072}
 - Original count of shadow copies = 1
 - Original Volume name: \\?\Volume{9ff6f68e-3950-4b91-a0d6-791006748149}\ [C:\]
 - Creation Time: 4/10/2021 9:52:17 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy59
 - Originating machine: Lat-5520-PC
 - Service machine: Lat-5520-PC
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential

indicates that the VSS snapshot creation completed at 9:52 am

I've uploaded the Macrium log file which indicates Image Completed Successfully in 01:56:25 and the I/O performance was Read 263.8 Mb/s - Write 9.5 Mb/s. 

Is this an issue with coming out of low power idle or is there another explanation?  I've changed the default to use the WTS, but the scheduled job has not yet run.

+x

 

zgrayfox - 12 April 2021 4:27 PM

Configuration details:
Dell Latitude 5520 laptop with 11th Generation I7, 16G memory
System only supports S0 low power idle (S1, S2 & S3 sleep modes not supported) see uploaded powercfg image
W10 Pro 20H2, Macrium Reflect 7.3.5758
Backup Source: 512G NVMe
Backup Destination: 1TB microSD card (using build in card reader)
Bitlocker used on both source & destination

Typical I/O performance for manually invoked backups is Read 3+ Gb/s & Write 580+ Mb/s.
Typical times to complete a full backup ~10-12 Minutes, incremental backup ~3-5 Minutes
Implemented a schedule using the Macrium Task Scheduler to perform an incremental every Saturday  6:00am. The job ran when scheduled, but took almost 6 hours to complete. Note that the laptop was on plugged in power during the entire time.

Here is a section from the Macrium Scheduler log...

10/04/2021-06:00:55] RunBackupServiceRoutine: Starting
[10/04/2021-06:00:55] RunBackupServiceRoutine: Job is a scheduled job
[10/04/2021-06:00:55] RunBackupServiceRoutine: IPC CreateProcess:
    NetBIOS: localhost
    Backup Definition: Macrium-Backup-{C8F4050B-B1AA-4388-8CA0-675116AF0FA5}
[10/04/2021-06:00:55] StartNewJob: Launching process '"C:\Program Files\Macrium\Reflect\Reflect.exe" -e -w "C:\Users\JnS_Admin\Documents\Reflect\Backup_to_microSD_on_D.xml" -inc -g {C8F4050B-B1AA-4388-8CA0-675116AF0FA5}' as SYSTEM
[10/04/2021-11:48:36] StartNewJob: executable returned 0
[10/04/2021-11:48:36] StartNewJob: Process complete
[10/04/2021-11:48:36]     Plan update success
[10/04/2021-11:48:36] UpdateBackupJobFinishedStatus: Updating job status
    PlanId: {4B8464DB-000A-4FF4-A597-70C54462C239}
    NetBIOS: localhost
    Status: success
    Description:
[10/04/2021-11:48:36] ServiceQueue: CurrentJobCompletion event received
[10/04/2021-11:48:36] ServiceQueue: Query IQueueManager for next backup job run time
[10/04/2021-11:48:36]

Started  6:00  completed successfully at 11:48 (5 Hours & 48 Minutes!)

A section from the VSS log:

Querying all shadow copies with the SnapshotSetID {47699273-1ff5-472e-b6ce-db24e1ad0072} ...

* SNAPSHOT ID = {49e2db24-1e0e-4ee3-bbcf-fa7195150ef0} ...
 - Shadow copy Set: {47699273-1ff5-472e-b6ce-db24e1ad0072}
 - Original count of shadow copies = 1
 - Original Volume name: \\?\Volume{9ff6f68e-3950-4b91-a0d6-791006748149}\ [C:\]
 - Creation Time: 4/10/2021 9:52:17 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy59
 - Originating machine: Lat-5520-PC
 - Service machine: Lat-5520-PC
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential

indicates that the VSS snapshot creation completed at 9:52 am

I've uploaded the Macrium log file which indicates Image Completed Successfully in 01:56:25 and the I/O performance was Read 263.8 Mb/s - Write 9.5 Mb/s. 

Is this an issue with coming out of low power idle or is there another explanation?  I've changed the default to use the WTS, but the scheduled job has not yet run.

Well, after a diversion related to disabling of the postponement of a scheduled backup dialog (See this Thread ) I've completed additional testing which seems to indicate that whether using MTS or WTS on this system running on AC power, the scheduled backup fails to elevate the system from the S0 low power idle state. The scheduled incremental backup takes 4-5+ hours rather than  normal 2-5 minutes. After setting the sleep options for the system running on AC power to do nothing on closing the lid and the sleep after idle time to never.  Using either MTS/WTS scheduler, the lid open or closed and with a logged in user locked, scheduled backups ran as expected (started at the scheduled times and completed in 2-3 minutes).

Her is a link to a Microsoft document which casts some doubt whether a scheduled backup will/should bring the system out of low power idle.

I have one suggestion to make
- but I'm nowhere near as experienced as the OP, and I'm surprised there aren't a whole string of replies

I have just rebuilt to factory settings a Lenovo Desktop A540-24ICB (PC is NOT my property)
I then updated it to current Win Update state and installed Reflect so that the owner could do a restore if ever needed.
Of course I set Reflect to run overnight - and it did NOT run as expected
Powercfg on this PC reported sleep states were S0 connected, Hibernate, and Fast Startup

EDIT: Since posting this earlier today, I now find that my suggested Hibernate work around does NOT work
if your system is built with Modern Standby with power S0 Connected Standby

Please read the post by MrSaxobeat on 24th March 2019 reporting a definitive statement by $M$S

     "Modern Standby" Energy management. Wake-Up is only possible by pressing the ON-key or by an external server which pushes software updates.
    Wake-Up by the Task scheduler (wake timer): Not possible
    Wake-Up by Wake-On-LAN: Not possible
    Wake-Up by something on the USB-Port: Not possible
    Wake-Up by disconnecting/connecting power: Not possible
    Disable Modern Standby: Not possible

In brief, Modern Standby systems do not support power on by a scheduled application.
Any visible Power options about wake timers are ineffective (and better hidden - my conclusion)

I can't do full checks, as I will no longer have the PC

Spilly