BAckup on SMB-Share fails

After I restarted my NS8-VM on a new Proxmox PVE, after the old one had crashed on the hardware side, the SMB-backup failed.

Some apps were successfully backed up, others were not.

To avoid artifacts, I

  • deleted the old backup
  • deleted the old backup destination
  • created a new share on my Synology NAS as the backup destination and
  • created a new backup task.

Nevertheless, the backup still fails for some apps.

{"context":{"action":"run-backup","data":{"id":4},"extra":{"backupName":"Sicherung nach SMB-Syno [DAHO-NS8-BAK]","completion":{"extraTextParams":["backupName"],"i18nString":"backup.backup_completed_successfully"},"description":"Starte Sicherung nach SMB-Syno [DAHO-NS8-BAK]","title":"Datensicherungen starten"},"id":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d","parent":"","queue":"cluster/tasks","timestamp":"2024-11-30T17:28:17.130774815Z","user":"admin"},"status":"aborted","progress":16,"subTasks":[{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/crowdsec1/run-backup"},"id":"6f82cb3d-7159-40a9-a951-972a8f7597d6","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"completed","progress":100,"subTasks":[],"result":{"error":"","exit_code":0,"file":"task/module/crowdsec1/6f82cb3d-7159-40a9-a951-972a8f7597d6","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/wordpress1/run-backup"},"id":"5d360f48-2123-49e6-af1d-29758fe50835","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"completed","progress":100,"subTasks":[],"result":{"error":"","exit_code":0,"file":"task/module/wordpress1/5d360f48-2123-49e6-af1d-29758fe50835","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/webserver1/run-backup"},"id":"d88f83d3-84a0-480a-9a40-ea77a56a017f","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"aborted","progress":0,"subTasks":[],"result":{"error":"Job for backup4.service failed because the control process exited with error code.\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\n","exit_code":1,"file":"task/module/webserver1/d88f83d3-84a0-480a-9a40-ea77a56a017f","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/it-tools1/run-backup"},"id":"d37195d8-50e7-486c-b1b5-90dca1cab693","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"aborted","progress":0,"subTasks":[],"result":{"error":"Job for backup4.service failed because the control process exited with error code.\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\n","exit_code":1,"file":"task/module/it-tools1/d37195d8-50e7-486c-b1b5-90dca1cab693","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/traefik1/run-backup"},"id":"c393fbe2-c9bc-4fdb-a5fd-5342b839f15b","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"aborted","progress":0,"subTasks":[],"result":{"error":"Job for backup4.service failed because the control process exited with error code.\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\n","exit_code":1,"file":"task/module/traefik1/c393fbe2-c9bc-4fdb-a5fd-5342b839f15b","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/dokuwiki1/run-backup"},"id":"2950cec9-2384-49f6-8768-50d61aa36ee3","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"aborted","progress":0,"subTasks":[],"result":{"error":"Job for backup4.service failed because the control process exited with error code.\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\n","exit_code":1,"file":"task/module/dokuwiki1/2950cec9-2384-49f6-8768-50d61aa36ee3","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/loki1/run-backup"},"id":"cdb3000a-4bc4-45ff-a150-0b8651edcf1c","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"aborted","progress":0,"subTasks":[],"result":{"error":"Job for backup4.service failed because the control process exited with error code.\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\n","exit_code":1,"file":"task/module/loki1/cdb3000a-4bc4-45ff-a150-0b8651edcf1c","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/samba1/run-backup"},"id":"f68e5c53-ef52-4556-afdf-3ffa3239e1b8","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"aborted","progress":0,"subTasks":[],"result":{"error":"Job for backup4.service failed because the control process exited with error code.\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\n","exit_code":1,"file":"task/module/samba1/f68e5c53-ef52-4556-afdf-3ffa3239e1b8","output":""}},{"context":{"action":"run-backup","data":{"id":4},"extra":{"description":"run-backup agent action","isNotificationHidden":true,"title":"module/lam1/run-backup"},"id":"4bcdb190-a3eb-4d7a-aa32-9cce5ac5a6ca","parent":"15a92ec1-0108-4bbf-9edd-b6453aff7a3d"},"status":"completed","progress":100,"subTasks":[],"result":{"error":"","exit_code":0,"file":"task/module/lam1/4bcdb190-a3eb-4d7a-aa32-9cce5ac5a6ca","output":""}}],"validated":true,"result":{"error":"Task module/webserver1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\\n', 'exit_code': 1}\nTask module/samba1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\\n', 'exit_code': 1}\nTask module/traefik1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\\n', 'exit_code': 1}\nTask module/dokuwiki1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\\n', 'exit_code': 1}\nTask module/it-tools1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\\n', 'exit_code': 1}\nTask module/loki1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\\nSee \"systemctl --user status backup4.service\" and \"journalctl --user -xeu backup4.service\" for details.\\n', 'exit_code': 1}\n6\n","exit_code":1,"file":"task/cluster/15a92ec1-0108-4bbf-9edd-b6453aff7a3d","output":""}}
Task module/webserver1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\nSee "systemctl --user status backup4.service" and "journalctl --user -xeu backup4.service" for details.\n', 'exit_code': 1}
Task module/samba1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\nSee "systemctl --user status backup4.service" and "journalctl --user -xeu backup4.service" for details.\n', 'exit_code': 1}
Task module/traefik1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\nSee "systemctl --user status backup4.service" and "journalctl --user -xeu backup4.service" for details.\n', 'exit_code': 1}
Task module/dokuwiki1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\nSee "systemctl --user status backup4.service" and "journalctl --user -xeu backup4.service" for details.\n', 'exit_code': 1}
Task module/it-tools1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\nSee "systemctl --user status backup4.service" and "journalctl --user -xeu backup4.service" for details.\n', 'exit_code': 1}
Task module/loki1/run-backup run failed: {'output': '', 'error': 'Job for backup4.service failed because the control process exited with error code.\nSee "systemctl --user status backup4.service" and "journalctl --user -xeu backup4.service" for details.\n', 'exit_code': 1}
6

If I do:

oot@daho-ns8:~# systemctl --user status backup4.service
Unit backup4.service could not be found.
journalctl --user -xeu backup4.service
~
~
-- No entries --
root@daho-ns8:~#

Does anyone have any ideas on how I can get a functioning backup again?

My Setup:

root@daho-ns8:~#  api-cli run list-backup-repositories
Warning: using user "cluster" credentials from the environment
{"repositories": [{"id": "cfd9b78e-86e5-5840-98d5-f82acb89f127", "provider": "smb", "name": "SMB-Syno [DAHO-NS8-BAK]", "url": "smb:DAHO-NS8-BAK", "password": "4400e5772a94142e32ba4f8b10ba7ddcbc9b06875a4b3424388fcc4267e5b159", "parameters": {"smb_domain": "WORKGROUP", "smb_host": "192.168.3.70", "smb_pass": "MY-PASSWORD", "smb_user": "NS8-BAK"}}], "password_exists": true}

@mrmarkuz had the right idea.
I analyzed the non-backupable apps and found a “zombie container” in each of them. It seems that these are references to containers that no longer exist.

I started them and thus removed the references.

However, it is not enough to clean up just one container; you have to touch all of them. As long as just one container contains artifacts, every backup job will abort.

Now the backup is running.

Special thanks to Markus for the right instinct.

2 Likes