Log File Timestamps in the future

[BackupBytesTim]

The log files for running backup jobs have time stamps at the front of each line, is that just exactly the time from the computer or is Veeam tracking time on its own somehow?

I ask because I have a running backup job that both VSPC and VBR show started at the appropriate time, the logs didn't start until 20 minutes later and the first thing was a connection error, so that seems odd, but I downloaded the logs shortly after it started actually transferring data to see the progress and the time for the most recent lines was what I would expect, about a minute or two in the past, accounting for the delay in packaging and transferring the logs, then me opening it and finding the file and scrolling to the bottom. This is something I typically do several times a day so I'm used to it. Side note, it'd be nice if the VSPC UI actually showed status information so I didn't need to download the logs repeatedly just to see job progress.

However, just under an hour later I downloaded the logs again to see how much progress had been made, it's been a while since the computer successfully backed up so I'm trying to track its progress to see that it finishes without substantial delays. At that time when I looked at the most recent lines in the logs, the time listed was about 20 minutes into the future. Which seems wrong.

The file modified time for the actual log file is similarly in the future. The computer running the agent and the VSPC and VBR servers and my computer that I'm viewing the logs in are all in the same time zone, so I'm not coming up with any explanation here. Scrolling through the log file it doesn't appear as though there's any gap where the time just jumped ahead, it really just seems like Veeam thinks time is passing faster than it actually is.

Does Veeam manually set the modified time for the log file in any way? If it doesn't, since that's wrong too, then I assume the problem is with Windows and not Veeam.

Assuming the problem is with Windows, could this be causing authentication issues due to system times being misaligned relative to the servers? I ask because we sometimes see different connection problems, some of which may give authentication related errors, but we usually disregard it as a connection failure since restarting the agent service and trying again fixes it, at least it fixes it right then, until it happens again later on.

[HannesK]

Hello,
we use the time from the operating system when we write something to the log files. I see no reason why we should set the "modified time" from our side. The operating system does that. Yes, wrong times on the machines where the agent is running causes side-effects.

Best regards,
Hannes

[BackupBytesTim]

That was my thought, I can't think of any reason for the computer's clock to be behaving like that, but we'll look into it further since it seems unlikely to be a Veeam issue.