Never seen this issue before myself but interested in what is found with this case.

I have never seen this behaviour in my environments, too.

Please keep us updated on this topic.

Same here, not experienced the issue. 

Same as Joe :)

Never seen nor heard of. As with others...interested to see the resolution. @Leo A. ..have you opened a support case with Veeam? Wonder what they have to say.

Cheers!

Hi Guys - thanks for your patience

- Veeam support also keeps me updated every week - with thanks for my patience :)

It seems that Veeam RnD still struggles to solve the issue in the current version 11 - but from support I have just received this statement:

“This behavior will be fixed in one of our future versions of product (most likely UTC time will be used in database).”
“Before implementation of the new logic we have to run the SQL script after Daylight Savings time switch to avoid full backup run.”

I have asked the support a few question about this  - and whether they will announce the bug - and how to handle with a “date-reset” script.
The send me a script - to use BEFORE the full backup runs after Daylight Saving Time change.….
I don`t know whether I can and are allowed to publice the script here?

I wonder why this issue only concern Files backup - and not VM Machine backups.
As I understand from other forums UTC is actually used in config. DB - to avoid international time issues - but maybe not for Files backup?? 

Cheers
Leo

Wonder if the new PostgresSQL for v12 will have the same issue.  Be interesting to test and see.

Hi, I have the same problem. Is it possible to get this script? I am using the community version.

Hi @SwissAndreas, please contact Veeam Support for the script.

Please note that this will not retroactively fix anything, it will just prevent the next run (if it’s affected) from doing the undesired behavior. You would need to rollback the database using a Configuration Backup prior to the affected job run in order to apply the script in a meaningful way.

File to tape is getting a major overhaul in v12, and I’m hopeful the new engine should avoid it but I’m not sure on the status of the fix. It’s not about MSSQL vs other instances, it’s just about the peculiarities with DST.

(lifehack: just “move” your computer to a locale without DST Joking of course, but it would likely work)

@Leo A. 

To answer your question, it’s just a quirk of how Windows handles DST and the LastModifiedDate attribute. You can see here it’s not unique to Veeam it’s just a peculiarity from Windows: https://qa.social.msdn.microsoft.com/Forums/vstudio/en-US/333e4402-291b-4dd1-aa9d-2df13cdb50e6/problem-with-file-dates-created-during-daylight-savings-time?forum=netfxbcl

(tldr: dates and time are hard Microsoft agrees)

Long story short, it’s solvable, and there are plans to address it, but probably not until at least v12 (Disclaimer: this is not saying it _will_ be fixed in v12, just with the major overhaul to the file to tape engine, I don’t think there would be a change until then)

Thank you very much for the answers. I contacted the support two days ago for the script and I am still waiting for the answer.

@SwissAndreas can you PM me the case? Shouldn’t take that long unless you’re on Basic Support (in that case, only support during Mon-Fri business hours)

Yes I am on basic support. What is PM?

Private Message

Just wondering if someone can share that script with me? I am on the community edition. Thanks 

Hi Kakachen001,

The issue was resolved in Veeam v12 release -- if you’re on that already, should not be an issue, else consider upgrading to v12.

I am using Veeam in a home lab environment but I have around 50tb to copy to tape so v12’s licensing doesn’t make sense to me.