Weird "extra config" - maybe I've missed something obvious

[telnetdoogie]

Summary

I have only 6 configs, and when the container runs, it shows an error:
No 'appropriate database type' Entered! - Set '$DB07_TYPE' environment variable - Halting Backup Number 07

Incidentally, all 6 backups are working fine.

Steps to reproduce

Here's my (sanitized) .env (and no configs defined in the compose):

# DEFAULTS ----------------------------
DEBUG_MODE=TRUE
TIMEZONE=America/Chicago
CONTAINER_NAME=container-db-backup
CONTAINER_ENABLE_MONITORING=FALSE
BACKUP_JOB_CONCURRENCY=2
DEFAULT_CHECKSUM=NONE
DEFAULT_COMPRESSION=ZSTD
DEFAULT_BACKUP_INTERVAL=1440
#DEFAULT_BACKUP_BEGIN=2330
DEFAULT_CLEANUP_TIME=60


# DATABASES ---------------------------
DB01_TYPE=pgsql
DB01_HOST=sonarr-db
DB01_NAME=sonarr-main
DB01_USER=username_here
DB01_PASS=password_here

DB02_TYPE=pgsql
DB02_HOST=radarr-db
DB02_NAME=radarr-main
DB02_USER=username_here
DB02_PASS=password_here

DB03_TYPE=pgsql
DB03_HOST=radarr3d-db
DB03_NAME=radarr-main
DB03_USER=username_here
DB03_PASS=password_here

DB04_TYPE=pgsql
DB04_HOST=prowlarr-db
DB04_NAME=prowlarr-main
DB04_USER=username_here
DB04_PASS=password_here

DB05_TYPE=pgsql
DB05_HOST=outline-db
DB05_NAME=outline
DB05_USER=username_here
DB05_PASS=password_here

DB06_TYPE=mongo
DB06_HOST=wekan-db
DB06_MONGO_CUSTOM_URI=mongodb://wekan-db/wekan

I've deleted the image, cleaned out the logs and backup folder... still seems to think there's an 07? It happened after I added the mongo definition as 06, so maybe my mongo definition is missing something?

What is the expected correct behavior?

Should only be 6 jobs defined.

Relevant logs and/or screenshots

container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/04-scheduling/run ** [scheduling] [process_restart] - Sleeping for 1 seconds
container-db-backup  | 2026-03-26.10:55:04 [STARTING] /etc/services.available/04-scheduling/run ** [scheduling] [1] Starting cron
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-07/run ** [db-backup07-scheduler] [parse_variables] Looking for existence of DB07_TYPE environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-06/run ** [db-backup06-scheduler] [parse_variables] Looking for existence of DB06_TYPE environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-05/run ** [db-backup05-scheduler] [parse_variables] Looking for existence of DB05_TYPE environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-02/run ** [db-backup02-scheduler] [parse_variables] Looking for existence of DB02_TYPE environment variable
container-db-backup  | 2026-03-26.10:55:04 [ERROR] /etc/services.available/dbbackup-07/run ** [db-backup07-scheduler] No 'appropriate database type' Entered! - Set '$DB07_TYPE' environment variable - Halting Backup Number 07
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-04/run ** [db-backup04-scheduler] [parse_variables] Looking for existence of DB04_TYPE environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-01/run ** [db-backup01-scheduler] [parse_variables] Looking for existence of DB01_TYPE environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-05/run ** [db-backup05-scheduler] [parse_variables] Looking for existence of DB05_NAME environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-02/run ** [db-backup02-scheduler] [parse_variables] Looking for existence of DB02_NAME environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-03/run ** [db-backup03-scheduler] [parse_variables] Looking for existence of DB03_TYPE environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-04/run ** [db-backup04-scheduler] [parse_variables] Looking for existence of DB04_NAME environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-01/run ** [db-backup01-scheduler] [parse_variables] Looking for existence of DB01_NAME environment variable
container-db-backup  | 2026-03-26.10:55:04 [DEBUG] /etc/services.available/dbbackup-03/run ** [db-backup03-scheduler] [parse_variables] Looking for existence of DB03_NAME environment variable
container-db-backup  | 2026-03-26.10:55:06 [DEBUG] /etc/services.available/dbbackup-01/run ** [01-sonarr-db__sonarr-main] BACKUP_BEGIN is a jump of minute starting with +

Environment

• Image version / tag: :latest
• Host OS: debian 6.12.74+deb13+1-amd64 / docker v29.3.0

Details

My compose:

services:

  container-db-backup:
    container_name: container-db-backup
    image: tiredofit/db-backup:latest
    volumes:
      - /volume1/docker/container-db-backup/backup:/backup
      - /volume1/docker/container-db-backup/logs:/logs
    restart: always
    networks:
      - db-backup
    env_file:
      - .env
    environment:
      USER_DBBACKUP: 1024
      GROUP_DBBACKUP: 100
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

networks:
  db-backup:
    external: true

[telnetdoogie]

I believe this is a genuine bug.

The container incorrectly overcounts backup jobs when DB##_MONGO_CUSTOM_URI is present because the instance detection regex in functions/10-db-backup:
grep -Pc "^(DB[0-9]._HOST=|.*MONGO_CUSTOM_URI=)"

matches any MONGO_CUSTOM_URI globally instead of scoping it to a specific DB index. This results in a phantom job.

The regex should be constrained to indexed variables only:

grep -Pc "^(DB[0-9]+_HOST=|DB[0-9]+_MONGO_CUSTOM_URI=)"

so only valid, numbered database definitions for MONGO are counted.

Here's the log output for that section as-is:

container-db-backup  | ++ set -o posix
container-db-backup  | ++ set
container-db-backup  | ++ grep -Pc '^(DB[0-9]._HOST=|.*MONGO_CUSTOM_URI=)'
container-db-backup  | + local backup_instances=7
container-db-backup  | + print_debug '[create_schedulers] Found '\''7'\'' DB_HOST instances'
container-db-backup  | + output_off
container-db-backup  | + '[' true = true ']'
container-db-backup  | + set +x
container-db-backup  | 2026-03-26.10:55:03 [DEBUG] /etc/cont-init.d/10-db-backup ** [db-backup] [create_schedulers] Found '7' DB_HOST instances

[telnetdoogie]

Switching my .env to be:

DB06_TYPE=mongo
DB06_HOST=wekan-db
DB06_NAME=wekan

and not using the CUSTOM_URI works to stop the error, and the backup succeeds as before.

[telnetdoogie]

I see now how perhaps this was because I foolishly provided extraneous entries in the environment that conflicted / collided with the values extracted from the CUSTOM_URI

If I change my env to just contain:

DB06_TYPE=mongo
DB06_HOST=wekan-db
DB06_NAME=wekan

or, alternatively:

DB06_TYPE=mongo
DB06_MONGO_CUSTOM_URI=mongodb://wekan-db/wekan

It doesn't enter trip up that same code. Perhaps a 'note' in the README would be a good idea. I'm happy to do that and submit a PR, if you'd like, @tiredofit

Sorry for the chatter, and THANKS for a kickass utility!! Very powerful.