Tasks run manually do not always run

[Todd]

2: Randomly, the task does not run properly and backup does not occur. The result look like this on the console:

Bad task on the console

Reflector.BadBackup.png (41.43 KiB) Viewed 2399 times

The eMailed log (attachment) is a perfect match to what shows on the console

Here is a verbose log console message:

Bad Task with verbose logging

Reflector.BadBackup.VerboseLogging.png (55 KiB) Viewed 2399 times

Note that the verbose log does not tell me "there are errors. consult the log file"

And the, written to hard drive, "Log" shows no errors as directed by the console's message:

Log on drive showing no errors

Reflector.Log.Without.an.error.png (81.35 KiB) Viewed 2399 times

3. What I get is: randomly the task will run properly and attempt to backup the files requested. And randomly the task will not attempt to do a backup and gives a message not related to the task that was requested.

Resolution needs to solve the problem: the requested task MUST ALWAYS run properly.

[gvd]

Hi Todd,

A few comments from a spectator :

Randomly, the task does not run properly and backup does not occur.

Maybe the problem is only a matter of reporting. Your backup does never run properly as you did not give it room to backup your files.
Maybe there is an exception catch that bypasses the end of the handling (and reporting) when there is an error. In this case some messages would be welcome.
Why not everytime ? Maybe Microsoft does not handle consecutive requests to do the same impossible thing with the same answer.

Note that the verbose log does not tell me "there are errors. consult the log file"

As you requested the verbose mode, there will never be anything more in the log file than on your console. No need to add a message.
I know, this would be a problem as there is not more information in the log file while not in verbose mode.

My 2 cents.

[Todd]

Maybe the problem is only a matter of reporting. Your backup does never run properly as you did not give it room to backup your files.

I checked. The bad tasks runs are not actually even trying to do a backup. The small backup drive is on purpose so I CAN see the errors reported. My customers run out of disk space all-the-time, so I need to simulate it.

[cobian]

The Verbose file won't show anything extra here. The DEBUG option perhaps will show something. I'm testing now with the list and a full USB drive. Have worked 10 out of of 10 times with the same error:

ERR 2022-02-07 22:17:35 The destination directory "F:\ClientHealth 2022-02-07 22;17;35" couldn't be created: (112) There is not enough space on the disk: [F:\ClientHealth 2022-02-07 22;17;35]

[Todd]

Keep at it. Every time you post a new update, I think it is fixed, but then got my heart broken. The last one (rc1) got all the way up to eight.

Is there any test I can run for you?

[Todd]

First run of CobianReflector-0.9.91.exe. Tears.

2022-02-08 14:05:43 A backup has started...
2022-02-08 14:05:43 Calculating the number of files. This could take a while...

2022-02-08 14:05:43 Backing up the task "KVM-W11 Reflector Test"
2022-02-08 14:05:43 Applying the parameters to the task "KVM-W11 Reflector Test" (if any).
2022-02-08 14:05:43 Requesting the creation of a Volume Shadow Copy image for the source...
2022-02-08 14:05:48 Compressing the log files to: "C:\WINDOWS\TEMP\Log files for Cobian Reflector.zip".

2022-02-08 14:05:48 The backup has ended. There are errors. Consult the log file.

2022-02-08 14:05:49 Getting the backup history for the task "08c0ae1f-3f4f-4336-8e4a-2bd216b17e04"...
2022-02-08 14:05:49 The log files have been successfully deleted.
2022-02-08 14:05:49 Deleting the temporary directory that holds the log files: C:\WINDOWS\TEMP\cd9a41d7-a1ec-4ed3-a807-c7a6919f7212...
2022-02-08 14:05:49 Deleting the compressed log files. Archive name: C:\WINDOWS\TEMP\Log files for Cobian Reflector.zip...

Here us with Debugging enabled:

2022-02-08 14:14:36 The log files have been successfully deleted.
2022-02-08 14:14:40 Backing up some selected tasks.
2022-02-08 14:14:40 The task KVM-W11 Reflector Test (08c0ae1f-3f4f-4336-8e4a-2bd216b17e04) was added to the queue.

2022-02-08 14:14:42 A backup has started...

2022-02-08 14:14:42 Individual file operations will be logged only to the log file and not seen on the user interface! Consult the log **file** when the backup is done.

2022-02-08 14:14:42 Calculating the number of files. This could take a while...

2022-02-08 14:14:42 Backing up the task "KVM-W11 Reflector Test"
2022-02-08 14:14:42 Applying the parameters to the task "KVM-W11 Reflector Test" (if any).
2022-02-08 14:14:42 Requesting the creation of a Volume Shadow Copy image for the source...
2022-02-08 14:14:44 Compressing the log files to: "C:\WINDOWS\TEMP\Log files for Cobian Reflector.zip".

2022-02-08 14:14:45 The backup has ended. There are errors. Consult the log file.

2022-02-08 14:14:45 The log files have been successfully sent.
2022-02-08 14:14:45 Deleting the temporary directory that holds the log files: C:\WINDOWS\TEMP\bf3846b7-181f-4254-93e0-e713185d2c81...
2022-02-08 14:14:45 Deleting the compressed log files. Archive name: C:\WINDOWS\TEMP\Log files for Cobian Reflector.zip...

2022-02-08 14:14:45 Getting the backup history for the task "08c0ae1f-3f4f-4336-8e4a-2bd216b17e04"...

[cobian]

Something is fishy with the shadow copy. It is being requested but not being created. No result at all. I wonder if it's timing out. Can you disable the shadow copy and see if it works as expected?

[Todd]

This is when the mirror directory was enabled.

Mirror Directory when enabled

Reflector.MirroDir.png (11.64 KiB) Viewed 2358 times

Every time I exited options, it complained about not finding the mirror directory.

Mirror not accessible error when options

Reflector.Mirror.not.accessible.png (4.47 KiB) Viewed 2358 times

When I changed the mirror to another directory, the accessible error went away:

Mirror in an alternate location

Reflector.Mirror.alternate.location.png (3.05 KiB) Viewed 2358 times

Bad task runs still not fixed.

I disabled mirror and there was no symptom change in the bad task runs.

Mirror disabled

Reflector.Mirror.Disabled.png (3.42 KiB) Viewed 2358 times

Tears.

[cobian]

Something is fishy with the shadow copy. It is being requested but not being created. No result at all. I wonder if it's timing out. Can you disable the shadow copy and see if it works as expected?

[gvd]

Every time I exited options, it complained about not finding the mirror directory.

It does not complain for not finding the mirror directory. It's just it seems he has no rights on this directory.
I had the same problem from the very first version I installed. System user though.

But this is not what Luis asks for . Disable shadow copy and retry.
Eager to know what's going on.