From de0f7ac528c9db49d0ee42519ce2a16cbde83535 Mon Sep 17 00:00:00 2001 From: Thomas Waldmann Date: Wed, 13 May 2026 10:16:04 +0200 Subject: [PATCH] docs: forward port error handling documentation for create (fixes #4912) --- src/borg/archiver/create_cmd.py | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/src/borg/archiver/create_cmd.py b/src/borg/archiver/create_cmd.py index e7ed66d35..9bf4d4f68 100644 --- a/src/borg/archiver/create_cmd.py +++ b/src/borg/archiver/create_cmd.py @@ -736,6 +736,22 @@ class CreateMixIn: - 'i' = backup data was read from standard input (stdin) - '?' = missing status code (if you see this, please file a bug report!) + Errors and (incomplete) archives + ++++++++++++++++++++++++++++++++ + + If an error happens during archive creation (e.g. some file could not be read + due to a permission error or some other OS error), borg will log a warning or + an error (depending on the type of issue) and continue with the next item. + + At the end of the backup, if there were any such issues, borg will exit with + a non-zero exit code (usually 1 for warnings). + + **The archive is still saved even if warnings or errors occurred**, but it will + only contain the data borg was able to read successfully. It is like a + checkpoint (see below), but with a user-given name. + + You should always check the backup logs and the exit code of the borg command. + Reading backup data from stdin ++++++++++++++++++++++++++++++