From 95c6d4c5177d566fb069890a55961f6540c6f048 Mon Sep 17 00:00:00 2001 From: Juanita Balaraj Date: Thu, 22 Feb 2024 22:47:14 +0000 Subject: [PATCH] Update for backup --ignore-health option (dsr8MR3, dsr8MR2) Story: 2010709 Change-Id: I4f9a0f04b98302719470f0e3693ef742dc46f1bb Signed-off-by: Juanita Balaraj --- .../kubernetes/backing-up-starlingx-system-data.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/source/backup/kubernetes/backing-up-starlingx-system-data.rst b/doc/source/backup/kubernetes/backing-up-starlingx-system-data.rst index 28183651b..3888227ee 100644 --- a/doc/source/backup/kubernetes/backing-up-starlingx-system-data.rst +++ b/doc/source/backup/kubernetes/backing-up-starlingx-system-data.rst @@ -198,6 +198,16 @@ Recommended Backup and Retention Policies backups can be performed locally or remotely, and the archive must be stored off the system. +- Backups are not allowed till the system is healthy (this excludes non-management + affecting alarms). However, a new parameter ``-e ignore_health=true`` can be + added in the ansible playbook to ignore system health and force the backup + to proceed. + + .. warning:: + + Using the ``-e ignore_health=true`` option should be avoided unless + it is required. Restoring an unhealthy backup will result in system issues. + - All backups are done during off-peak hours (i.e. maintenance window). - Weekly backups should be performed under normal steady state conditions to