Repair time check is no longer confused by time zones, but is confused by dlist retries:
The remote files are newer (5/5/2025 11:54:31 AM) than the local database (5/5/2025 11:54:29 AM), this is likely because the database is outdated. Consider deleting the local database and run the repair operation again. If this is expected, set the option “–repair-ignore-outdated-database”
An upload retry is done with a different name, random for dblock and dindex, 1 second higher for dlist. People normally wouldn’t notice tiny time change, but a Repair notices.
Live log at retry level:
May 5, 2025 11:54 AM: Backend event: Put - Completed: duplicati-20250505T155431Z.dlist.zip (667 bytes)
May 5, 2025 11:54 AM: Backend event: Put - Started: duplicati-20250505T155431Z.dlist.zip (667 bytes)
May 5, 2025 11:54 AM: Renaming "duplicati-20250505T155430Z.dlist.zip" to "duplicati-20250505T155431Z.dlist.zip"
May 5, 2025 11:54 AM: Backend event: Put - Rename: duplicati-20250505T155431Z.dlist.zip (667 bytes)
May 5, 2025 11:54 AM: Backend event: Put - Rename: duplicati-20250505T155430Z.dlist.zip (667 bytes)
May 5, 2025 11:54 AM: Backend event: Put - Retrying: duplicati-20250505T155430Z.dlist.zip ()
May 5, 2025 11:54 AM: Operation Put with file duplicati-20250505T155430Z.dlist.zip attempt 2 of 5 failed with message: No connection could be made because the target machine actively refused it.
May 5, 2025 11:54 AM: Backend event: Put - Started: duplicati-20250505T155430Z.dlist.zip (667 bytes)
May 5, 2025 11:54 AM: Renaming "duplicati-20250505T155429Z.dlist.zip" to "duplicati-20250505T155430Z.dlist.zip"
May 5, 2025 11:54 AM: Backend event: Put - Rename: duplicati-20250505T155430Z.dlist.zip (667 bytes)
May 5, 2025 11:54 AM: Backend event: Put - Rename: duplicati-20250505T155429Z.dlist.zip (667 bytes)
May 5, 2025 11:54 AM: Backend event: Put - Retrying: duplicati-20250505T155429Z.dlist.zip ()
May 5, 2025 11:54 AM: Operation Put with file duplicati-20250505T155429Z.dlist.zip attempt 1 of 5 failed with message: No connection could be made because the target machine actively refused it.
May 5, 2025 11:54 AM: Backend event: Put - Started: duplicati-20250505T155429Z.dlist.zip (667 bytes)
Job → Show log → Remote:
- May 5, 2025 11:54 AM: put duplicati-20250505T155431Z.dlist.zip
- May 5, 2025 11:54 AM: put duplicati-20250505T155430Z.dlist.zip
- May 5, 2025 11:54 AM: put duplicati-20250505T155429Z.dlist.zip
Fileset table Timestamp is 1746460469 3:54:29 PM
Repro:
Backup a short file to something easily turned on and off. I used FileZilla Server.
--no-backend-verification --upload-unchanged-backups
Turn server off then backup again, watching About → Show log → Live → Retry
Turn server on and let it finish uploading the time-incremented renamed dlist file.
Repair
Seeing ParsedVolumes makes me think it uses the retry-incremented dlist filename time.
EDIT 1:
Test for bug inspired by a user report where discussion on the theory might continue here.
EDIT 2:
Filed issue.