The borg backup seems to create a bunch of directories. When I tried to zip it up I got a tar: ./NextCloudBackup20250308.tar.gz: file changed as we read it
after the tar command was finished. Does Nextcloud alter stuff in the “backup” directories AFTER the backup has completed? Am I zipping up the wrong thing? I’m confused.
Yesterday I went into https://myIp:8080 and clicked “create backup”. This shut down most of the containers and spinned for a while creating a backup. Then it told me the backup proces was FINISHED. It re-started the containers back up (no pun intended).
So then I’m like: Imma copy this onto my backup flash drive. But when I looked in the backup folder (/home/myUserName/Backup/borg) it seems to not be a single compressed file but a bunch of subdirectories. So I’m like: ok, imma just zip this all up and then copy that to the thumb drive.
So I sudo tar -czvf NextCloudBackup20250308.tar.gz ./borg .
. Note: I am NOT inside the borg directory when I’m doing this. I’m inside the /home/myUsernameBackup directory only zipping up the borg directory. I let it run overnight. After it finished I do see my zip file … but… There’s also a message saying: “tar: ./NextCloudBackup20250308.tar.gz: file changed as we read it” This gives me a concern… Does this mean that the directory that was being zipped up changed midway through the zipping up process? Does nextcloud continue to update the backup directory even after the official “backup” process is finished?
Am I doing things wrong? Should I NOT be zipping up the borg directory but instead copy it as is to the flash drive? What is the PROPER procedure for backing things up on something like a flash drive or another type of external media (like, if I wanted to transfer the backup onto another computer over the network for example)
- Nextcloud Server version (e.g., 29.x.x):
Nextcloud AIO v10.6.1
- Operating system and version (e.g., Ubuntu 24.04):
Fedora 41 server
- Web server and version (e.g, Apache 2.4.25):
Whichever Apache comes with Nextcloud AIO v10.6.1
- Reverse proxy and version _(e.g. nginx 1.27.2)
no reverse rpoxy used
- PHP version (e.g, 8.3):
Whichever coems with Nextcloud AIO v10.6.1
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
After first backup
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no