Open williamwgant opened 1 week ago
a) you may wanna update your legacy variables
b) time format is HHMM which is four digits
c) see https://github.com/tiredofit/docker-db-backup?tab=readme-ov-file#scheduling-options
You may need to wrap your DEFAULT_BACKUP_BEGIN value in quotes for it to properly parse. There have been reports of backups that start with a 0 get converted into a different format which will not allow the timer to start at the correct time.
Summary
When I set a DB_DUMP_BEGIN value without four digits (500), I get an error "_BACKUP_BEGIN is invalid - Unable to perform scheduling". If I set it to 0500, I get the same error. It doesn't seem to like the leading zero.
Steps to reproduce
What is the expected correct behavior?
Should correctly schedule the backup and run the backup at the specified time.
Relevant logs and/or screenshots
Environment
``` db-backup-gitea: container_name: db-backup-gitea hostname: db-backup-gitea image: tiredofit/db-backup links: - db-gitea depends_on: - db-gitea volumes: - /volume1/Backups/gitea:/backup labels: - "com.centurylinklabs.watchtower.enable=true" environment: TZ: America/Chicago DB_TYPE : mariadb DB_HOST : db-gitea DB_NAME : ${MYSQL_DATABASE} DB_USER : root DB_PASS : "${MYSQL_ROOT_PASSWORD}" DB_DUMP_FREQ : 1440 DB_DUMP_BEGIN : 345 DB_CLEANUP_TIME : 8640 CHECKSUM : SHA1 COMPRESSION : ZSTD SPLIT_DB : FALSE restart: unless-stopped networks: gitea: ```
Possible fixes
I suspect this is probably just a one-off parsing error. It may also be that I'm misunderstanding the error message.