Ok, this is what I did:
- Started a virtual machine and set it's timezone to Eastern Europe (which I assume is your timezone as you've not actually told me yet).
- Set the timezone on Google Drive (via its web interface) to Tallinn
- Create one file with a last mod date & time of 1st October 11:55PM, so that's in DST
- Create one file with a last mod date & time of 1st March 11:55PM, so that's outside of DST
- Ran SyncBackPro to upload those files to Google Drive. It uploaded the files.
- I can see the March file (outside of DST) is showing it as 2nd March in Google Drive. But that is Google Drive showing that, not SyncBack. If I run SyncBack again it correctly knows they're identical, meaning the dates & times match.
So I then set the date & time in the Virtual Machine to after DST, 1st December, and restored the files from Google Drive using SyncBack. Both files restored and had exactly the same date & time as the original files. So restoring will not get different results. They will restore with the correct date & time regardless of it being DST or not.
I even changed the timezone to one without DST, restored the files, and they still had the correct date & time. So they will restore with the correct date & time regardless of the time zone.
When Syncback sends files to Google Drive it uses the GMT/UTC date & time (as Google expects), so it doesn't matter what the time zone is on the local computer. All date & time comparisons are done using GMT/UTC so time zones and DST won't affect it.
- Started a virtual machine and set it's timezone to Eastern Europe (which I assume is your timezone as you've not actually told me yet).
- Set the timezone on Google Drive (via its web interface) to Tallinn
- Create one file with a last mod date & time of 1st October 11:55PM, so that's in DST
- Create one file with a last mod date & time of 1st March 11:55PM, so that's outside of DST
- Ran SyncBackPro to upload those files to Google Drive. It uploaded the files.
- I can see the March file (outside of DST) is showing it as 2nd March in Google Drive. But that is Google Drive showing that, not SyncBack. If I run SyncBack again it correctly knows they're identical, meaning the dates & times match.
So I then set the date & time in the Virtual Machine to after DST, 1st December, and restored the files from Google Drive using SyncBack. Both files restored and had exactly the same date & time as the original files. So restoring will not get different results. They will restore with the correct date & time regardless of it being DST or not.
I even changed the timezone to one without DST, restored the files, and they still had the correct date & time. So they will restore with the correct date & time regardless of the time zone.
When Syncback sends files to Google Drive it uses the GMT/UTC date & time (as Google expects), so it doesn't matter what the time zone is on the local computer. All date & time comparisons are done using GMT/UTC so time zones and DST won't affect it.