Recent content by UweOhse

I changed the schedule of the replication, so it doesn't run between 00:30 und 01:59. This keeps the backup window replication free, and i will not lose to much data at the time anyway. This seems to work good enough for now. i'd likely forget to pct unlock the container more often than that...

Replication is set to */30, and the bwlimit to 50 MB/s. The backup of that container takes 50 to 60 minutes (too many files changes, but that's hard to get rid of). So a schedule of */90 would avoid that problem? Thanks in advance, Uwe

Hello, the backup of one container fails with the message in the title. when i "pct unlock" it, the next backup works (i used the backup for development purposes, and i'm quite sure that the backup is complete). That container is the largest one on the machine, one of the two important ones...

Hello, when i tried to run a backup for a PVE Container it failed for the following reason: INFO: Error: error at "var/www/XYZ/data/upload/1732379/IMG_20200710_135246.jpg": file with negative mtime which is a bit annoying after it ran 3 hours :) File: IMG_20200710_135246.jpg Size...

Hello, these four log lines repeat every 10 seconds, which is a bit annoying, though obviously harmless. Jul 20 17:50:49 pbs proxmox-backup-proxy[12366]: find_mounted_device failed - failed to parse mount info line: [49, 53, 54, 56, 32, 49, 53, 54, 55, 32, 48, 58, 49, 50, 54, 32, 47, 32, 47...