Support intro
Hello everyone,
I’ve been using and enjoying Nextcloud AIO for quite a while now. I find it excellent. That aside, I need help with the backup process.
Recently, I’ve been getting errors in Borg when it comes to pruning all snapshots / images. It has been working fine for over a year, and I believe what triggered this issue was an integrity check (from the AIO panel). While the check went well, and did not find any problems, I’m now getting every day a “failed backup”, meaning that I do have the backup, but it fails deleting the old ones.
This is the end of a backup log :
----------------------------------------------------------------------
2024-10-02T16:27:20.387964508Z Repository: /mnt/borgbackup/borg
2024-10-02T16:27:20.388047192Z Archive name: 20241002_154803-nextcloud-aio
2024-10-02T16:27:20.388062206Z Archive fingerprint: 9b628407189c6abd7bcafbb0263ce6f950a78cc8f19d064e0b8e3c02d986aef0
2024-10-02T16:27:20.388065794Z Time (start): Wed, 2024-10-02 15:48:04
2024-10-02T16:27:20.388068513Z Time (end): Wed, 2024-10-02 16:27:17
2024-10-02T16:27:20.388071061Z Duration: 39 minutes 13.40 seconds
2024-10-02T16:27:20.388144306Z Number of files: 122766
2024-10-02T16:27:20.388160588Z Utilization of max. archive size: 0%
2024-10-02T16:27:20.388163994Z ------------------------------------------------------------------------------
2024-10-02T16:27:20.388166835Z Original size Compressed size Deduplicated size
2024-10-02T16:27:20.388169358Z This archive: 183.11 GB 158.09 GB 117.28 GB
2024-10-02T16:27:20.388171789Z All archives: 183.11 GB 158.09 GB 117.28 GB
2024-10-02T16:27:20.388174249Z
2024-10-02T16:27:20.388181546Z Unique chunks Total chunks
2024-10-02T16:27:20.388184330Z Chunk index: 132867 186334
2024-10-02T16:27:20.388188295Z ------------------------------------------------------------------------------
2024-10-02T16:27:20.480808400Z BORG_PRUNE_OPTS are "--keep-within=7d --keep-weekly=4 --keep-monthly=2"
2024-10-02T16:27:20.480841571Z Pruning the archives...
2024-10-02T16:27:21.157154097Z usage: borg prune [-h] [--critical] [--error] [--warning] [--info] [--debug]
2024-10-02T16:27:21.157197691Z [--debug-topic TOPIC] [-p] [--iec] [--log-json]
2024-10-02T16:27:21.157357830Z [--lock-wait SECONDS] [--bypass-lock] [--show-version]
2024-10-02T16:27:21.157366019Z [--show-rc] [--umask M] [--remote-path PATH]
2024-10-02T16:27:21.157369311Z [--remote-ratelimit RATE] [--upload-ratelimit RATE]
2024-10-02T16:27:21.157372077Z [--remote-buffer UPLOAD_BUFFER]
2024-10-02T16:27:21.157374825Z [--upload-buffer UPLOAD_BUFFER] [--consider-part-files]
2024-10-02T16:27:21.157377386Z [--debug-profile FILE] [--rsh RSH] [-n] [--force] [-s]
2024-10-02T16:27:21.157380045Z [--list] [--keep-within INTERVAL] [--keep-last SECONDLY]
2024-10-02T16:27:21.157382486Z [--keep-minutely MINUTELY] [-H HOURLY] [-d DAILY]
2024-10-02T16:27:21.157384906Z [-w WEEKLY] [-m MONTHLY] [-y YEARLY] [-P PREFIX | -a GLOB]
2024-10-02T16:27:21.157400760Z [--save-space] [-c SECONDS]
2024-10-02T16:27:21.157404174Z [REPOSITORY]
2024-10-02T16:27:21.157408016Z borg prune: error: argument -m/--keep-monthly: invalid int value: '2"'
2024-10-02T16:27:21.201609938Z Failed to prune archives!
Nextcloud version : 29.0.6
Operating system and version : Debian 12 Bookworm
Apache or nginx version : 2.4.62-1~deb12u1
PHP version : 8.2.23 (AIO version).
The issue you are facing:
Is this the first time you’ve seen this error? : Yes, it started appearing a month ago, but I never saw anything like this in my prior experience with Nextcloud or Nextcloud AIO.
Steps to replicate it :
WARNING: THIS IS MY BEST GUESS AND MIGHT NOT ACTUALLY BE THAT.
- Take a backup
- Verify the integrity of the backups
- Every subsequent backup will softly fail.
My docker compose file :
services:
nextcloud:
image: nextcloud/all-in-one:latest
restart: always
container_name: nextcloud-aio-mastercontainer
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- 8080:8080 #For the web interface
environment:
- APACHE_PORT=11000 #IMPORTANT! For the reverse proxy
- APACHE_IP_BINDING=127.0.0.1
- NEXTCLOUD_DATADIR=/data/current/nextcloud #IMPORTANT! The directory containing the data
- NEXTCLOUD_UPLOAD_LIMIT=10G
- NEXTCLOUD_MAX_TIME=3600
- SKIP_DOMAIN_VALIDATION=true
# - BORG_RETENTION_POLICY="--keep-within=7d --keep-weekly=4 --keep-monthly=2"
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
Steps tried :
- Commenting out my custom retention policy in the compose file (didn’t work)
- Removing the Borg config inside the mastercontainer, resetting the backup location to a new one and starting over, with
sudo docker exec nextcloud-aio-mastercontainer rm /mnt/docker-aio-config/data/borg.configand a new folder on the backup disk. (didn’t work)
I’m not sure why I’m having this problem, as I didn’t change my configuration in a while. My best current guess would be the integrity check as it checks out with the timeline, but then again it’s just a guess.
I tried to google it, but it seems that it’s not a widespread issue. Let me know if you have any clues 