-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backup files creation times #92
Comments
Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks! |
ok - some further information that may help ... Bitwarden is running on a Windows 11 server in my home as a self-hosted instance on Docker. I am in the North American Eastern Time Zone. Currently the time zone offset is the Coordinated Universal Time (UTC) -5, in other words 5 hours behind the UTC. For more information please see: https://www.timeanddate.com/time/zones/edt |
Self hosted backup files are being created with a file name which includes the UTC date and time as part of the filename itself, but with a file timestamp (modified time) based on Local time.
This is confusing, and should be corrected. Especially as it may be assumed that the backups are being taken at the local time shown in the filename, when in fact they are not. Additionally, one would assume the backups would be taken at midnight, but in fact they are being taken at midnight UTC which may be quite unexpected in many cases.
Also, some backup files are being created just one minute after the previous backup, while others are created one day after the previous backup. Again, confusing. One backup every 24 hours is what I would suspect most people would assume should happen.
Please see the screen shot below:
While the above is a bug report, it is related to the following feature request:
https://community.bitwarden.com/t/feature-request-self-hosting-respect-for-local-time-zone/53130
The text was updated successfully, but these errors were encountered: