only 1 volume backing up #12

Closed
opened 2025-08-30 11:31:50 -04:00 by kareem613 · 3 comments
kareem613 commented 2025-08-30 11:31:50 -04:00 (Migrated from github.com)

Should it be creating a backup folder per volume? Here's my scenario.

I have a service with two volumes.

With this config

services:
  app:
    image: ghcr.io/hargata/lubelogger:latest
    #build: .
    restart: unless-stopped
    # volumes used to keep data persistent
    volumes:
      - data:/App/data
      - keys:/root/.aspnet/DataProtection-Keys
    # expose port and/or use serving via traefik
    ports:
      - 8080:8080
    env_file:
      - .env
    labels:
      - docker-volume-backup.stop-during-backup=true
      - "repliqate.enabled=true"
      - "repliqate.engine=restic"
      - "repliqate.schedule=0 0/1 * 1/1 * ? *"
      - "repliqate.backup_id=lubelogger"
      - "repliqate.retention=14"
      #- "repliqate.excl_volumes=lubelogger_data"


volumes:
  data:
    name: lubelogger_data
  keys:
    name: lubelogger_keys

I get only the following folder
<backup_destination>/lubelogger/volumes/lubelogger_data

If I make it ignore lubelogger_data (the commented out line), then I get
<backup_destination>/lubelogger/volumes/lubelogger_keys

Is this a bug? I would have expected to get a folder per volume.

I'm using the cutting-edge tag.

Should it be creating a backup folder per volume? Here's my scenario. I have a service with two volumes. With this config ``` services: app: image: ghcr.io/hargata/lubelogger:latest #build: . restart: unless-stopped # volumes used to keep data persistent volumes: - data:/App/data - keys:/root/.aspnet/DataProtection-Keys # expose port and/or use serving via traefik ports: - 8080:8080 env_file: - .env labels: - docker-volume-backup.stop-during-backup=true - "repliqate.enabled=true" - "repliqate.engine=restic" - "repliqate.schedule=0 0/1 * 1/1 * ? *" - "repliqate.backup_id=lubelogger" - "repliqate.retention=14" #- "repliqate.excl_volumes=lubelogger_data" volumes: data: name: lubelogger_data keys: name: lubelogger_keys ``` I get only the following folder `<backup_destination>/lubelogger/volumes/lubelogger_data` If I make it ignore `lubelogger_data` (the commented out line), then I get `<backup_destination>/lubelogger/volumes/lubelogger_keys` Is this a bug? I would have expected to get a folder per volume. I'm using the `cutting-edge` tag.
WiggleWizard commented 2025-08-30 16:49:21 -04:00 (Migrated from github.com)

Definitely should be getting both volumes, you're right. Looks like a bug. I'll make it down and get to it this weekend

Definitely should be getting both volumes, you're right. Looks like a bug. I'll make it down and get to it this weekend
kareem613 commented 2025-08-30 16:58:27 -04:00 (Migrated from github.com)

I'll give it a go whenever it's ready.

Otherwise this system is working out pretty good. I like it!

I'll give it a go whenever it's ready. Otherwise this system is working out pretty good. I like it!
WiggleWizard commented 2025-08-30 20:49:37 -04:00 (Migrated from github.com)

Fixed now with new latest tag. Also to note, since you're using volume exclusion: it's changed to being a volume label now instead of a hacky container label. Please read the readme on this to continue using the feature!

Fixed now with new `latest` tag. Also to note, since you're using volume exclusion: it's changed to being a volume label now instead of a hacky container label. Please read the readme on this to continue using the feature!
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lminlone/repliqate#12
No description provided.