Backup keeps failing with error #615
Comments
|
Yep it was me :) I run Backrest in a Proxmox LXC and I only gave it 1GB of RAM. The container was running out of RAM and killing the process. |
|
Oh funny -- just to check, was backrest the big ram user? I've been pretty careful re: allocations so anything huge is a bug worth reporting! Some spikes in memory usage when restic itself is running a backup are more expected too, but I'd somewhat have expected a backup to complete successfully with 1GB total ram even for a sizable dataset. |
|
Yeah, Backrest is the only thing I have running in that container. When Backrest is idle, the container sits at about ~275MB utilization. Even after starting a backup, memory usage doesn't really budge. However, as soon as it hits new data that it actually needs to backup, memory usage increases by about ~900MB. 
The total size of my dataset is about ~1.1TB. |
Not sure if this is an issue with backrest or restic itself. Or it might not be an issue at all and there's something wrong with my setup. But my backup keeps failing with the following error:
[restic] {"message_type":"status","seconds_elapsed":88,"seconds_remaining":5409,"percent_done":0.0160063[tasklog] 10:10:24.283Z error backup for plan "b2" task failed {"error": "failed to backup: command \"/root/backrest/data/restic backup --json /nas/storage -o sftp.args=-oBatchMode=yes --exclude-caches ...\" failed: exit code -1: backup failed\nprocessing command output: no summary event found", "duration": 3366.759678671}It also seems mostly random. It doesn't seem to be happening at any particular time or with any particular file.
Platform Info
The text was updated successfully, but these errors were encountered: