# Mysql backup using Duplicati **URL:** \ **Category:** Support\ **Created:** [May 6, 2020, 9:08pm UTC](https://forum.duplicati.com/t/mysql-backup-using-duplicati/9788 "2020-05-06T21:08:23Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\ **Post date:** [May 7, 2020, 12:43pm UTC](https://forum.duplicati.com/t/mysql-backup-using-duplicati/9788/11 "2020-05-07T12:43:31Z")
> [@floky13](#): > > So i suppose Duplicati could’t interpret the variable %DATE%. Duplicati never interprets such variables. If done at all, it’s done by whatever it runs, e.g. `cmd.exe`. Running a test, using Windows 10 `Settings` to change `Regional format` in `Region settings`, suggests that it’s per-user, as the user doing the change changed, and another user on PC didn’t. Because you are running Duplicati as the `SYSTEM` user, I wonder what date output it is giving you? You can test that with an `echo` command to a known file, e.g. `echo %DATE% > ` Possibly the SYSTEM account has a standard format, e.g. `English (United States)` for safety. Unexpected bugs can creep in when things vary, e.g. my format throws spaces and slashes out… > [@floky13](#): > > My duplicati is running over service. If that means a Windows service, you can change it to run as you instead (if that’s sufficient, and sometimes it isn’t) [Service for /localuser](https://forum.duplicati.com/t/service-for-localuser/9730) has thoughts on what works, and what might not work… But until you find out what your `%DATE%` is saying when run by Duplicati, this is all rather a guess. Does a date really need to be there anyway? What’s your cleanup plan for old ones sitting there? Theoretically, this file only needs to exist until Duplicati has backed it up, then it can be deleted… --- _[View the full topic](https://forum.duplicati.com/t/mysql-backup-using-duplicati/9788)._