-
How to use GitHub
Steps to reproduce
Expected behaviorShow available restore points after backup. Actual behaviorAIO mastercontainer is not able to list past backups. Host OSUbuntu 20.04 Nextcloud AIO version1.3.1 Current channellatest Other valuable infoAs you can see the AIO container is not aware when the backup was done nor that there even is one. Does the mastercontainer has it's own backup database or does it just work by directly accessing the files in the backup folder? (The backup container logs look fine: "Backup finished successfully") |
Beta Was this translation helpful? Give feedback.
Answered by
szaimen
May 31, 2022
Replies: 28 comments 5 replies
-
|
Hello, can you show the logs of the last backup? (Click on logs right next to backup was successful) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi (I've removed the logs of the private files) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I need especially the last lines from the log that you probably redacted which should give us somehints why the internal database was not updated...) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Basically the internal database should be updated on every backup container execution... (Check backup, create backup, restore backup...) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I just ran another backup here are the full logs: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I see and probably the points are still not listed kn the aio interface? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Is anything written to this file? |
Beta Was this translation helpful? Give feedback.
0 replies
-
No still nothing there
The file is completely empty but shows a modified file timestamp which is equal to the backup time. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks! Can you do this and post the output of it here please? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Sure |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On what type of mount is the backup created on? On an directly connected drive or smb/nfs mount, other? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
That's an nfs4 mount |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I see. So somehow borg does not remove the borg lock correctly which is nothing we have control over. Does the integrity check work? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yes the integrity check did work when i ran it a few days ago. |
Beta Was this translation helpful? Give feedback.
0 replies
-
You can try by running |
Beta Was this translation helpful? Give feedback.
0 replies
-
I did run the break-lock command and then borg list again but the exception is still thrown. (I ran it without --debug first) I could just delete the lock file manually. |
Beta Was this translation helpful? Give feedback.
0 replies
-
you may try to rename it to a different name first which may also solve this problem... |
Beta Was this translation helpful? Give feedback.
0 replies
-
I did rename it, but as soon as i run "borg list" it is added again.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think the lock.roster is also in the way... please rename both and try again. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Both files are immediately re added after the "borg list" command.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
all right and it still produces an error when you run the borg list command? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yes still:
With debug: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Can you please try to run the integrity check from the aio interface? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ok I did that. Yes "g data 99.99%" is the very last line. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yes, you could try to start the backup from scratch by removing all backup related files from To me this now clearly looks like and issue of your nfs mount, borg or both in interplay. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
The nfs mount actually was the reason. |
Beta Was this translation helpful? Give feedback.
Answer selected by
m4nug
This comment has been hidden.
This comment has been hidden.
-
In case you automated / scripted breaking the lock: that is a very bad idea, please check the docs. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
all right. will change this. |
Beta Was this translation helpful? Give feedback.
-
|
done |
Beta Was this translation helpful? Give feedback.
-
|
That output is not normal for borg, something is broken there: |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
this is only a logging issue afaics. |
Beta Was this translation helpful? Give feedback.
-
|
because all backup operations work normal in my testing... |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, you could try to start the backup from scratch by removing all backup related files from
var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data, delete the borg folder from your nfs mount and try again. But I doubt it will improve things.To me this now clearly looks like and issue of your nfs mount, borg or both in interplay.