"Execution Stopped by User"

[Brabian]

I have a number of scripts to ensure my data is consistently backed up but I have recently noticed that one keeps failing with an "execution stopped by user" error - even though it is an automatic script that is supposed to run over night!

I'm (still) running v16.6 and I've just realised that this has been going on for some months - although if I run the script it completes without error!

A sample log file would be:

+    Normal backup using Backup Set A2021 at 20/05/2022 23:59 (Execution unit 1)
        20/05/2022 23:59:22: Finished scanning backup set data files
    To Backup Set Backup Set A2021...

-    20/05/2022 23:59:20: Copying Ace Surgical on share on WDMyCloud
        21/05/2022 00:00:08: Found: 5,296 files, 572 folders, 29.7 GB
        21/05/2022 00:00:09: Finished matching
    21/05/2022 00:00:09: Selector "All Files Except Cache Files" was used to select 5,296 files out of 5,296.
        21/05/2022 00:00:09: Copying: 0 files (zero KB) and 0 hard links
        Grooming Backup Set Backup Set A2021, optimizing for performance...
        Groomed 1,460 KB from Backup Set Backup Set A2021.
        Optimizing for performance skipped grooming 2,140 files (21.9 MB).
    21/05/2022 00:05:40: Building Snapshot...
        21/05/2022 00:05:43: Copying Snapshot: 1 files (1,453 KB)
        21/05/2022 00:05:44: Snapshot stored, 1,453 KB
    21/05/2022 00:05:44: Comparing Ace Surgical on share on WDMyCloud
    21/05/2022 00:05:44: Execution completed successfully        Duration: 00:06:23 (00:06:21 idle/loading/preparing)

-    21/05/2022 00:05:44: Copying Avenues on share on WDMyCloud
        21/05/2022 00:05:49: Found: 539 files, 75 folders, 1.2 GB
        21/05/2022 00:05:50: Finished matching
    21/05/2022 00:05:50: Selector "All Files Except Cache Files" was used to select 539 files out of 539.
        21/05/2022 00:05:50: Copying: 0 files (zero KB) and 0 hard links
    21/05/2022 12:10:49: Execution stopped by operator        Duration: 12:05:04 (12:05:03 idle/loading/preparing)

        21/05/2022 12:10:49: Compressing catalog file
    21/05/2022 12:10:49: Execution stopped by operator
    Total duration: 12:11:26 (12:11:25 idle/loading/preparing)
 

Any thoughts, guys?

[Lennart_T]

The first script starts by grooming, indication that the destinations id (too?) full to perform the backup. This script takes about 6 minutes.

The second script starts and the waits for about 12 hours. Maybe it starts grooming and can't groom out space enough to perform the actual backup?

What happens at 12:10:49? The user reboots the computer? Or does indeed stop the backup?

 

I would start looking at the (free) space on the destination.

 

[mbennett]

Also, remember that it's possible to change the client's settings so they can stop or not stop a running backup.  If this is running for 12 hours without completion there's not much reason to let it run, but the user might be seeing a balloon on the taskbar, and if they're allowed to kill the job they do so.

[Nigel Smith]

On 5/22/2022 at 12:32 PM, Brabian said:

one keeps failing with an "execution stopped by user" error

Note that the error is actually "...stopped by operator", not user. IMO that means it is being stopped on the Retrospect "admin" side, not at the client. Have you set a limited schedule of execution, a media timeout, or similar? Is something going into power save/sleep just after midnight, effectively pausing the execution until the timeout is reached?