From 35dfd47ec77df2b2f6b7034a89a14351494dc800 Mon Sep 17 00:00:00 2001
From: Piotr Ryba <55996264+prryb@users.noreply.github.com>
Date: Tue, 20 Jul 2021 12:06:25 +0200
Subject: [PATCH] Docs: explanation what is backed up and why (#599)

* Explanation what's backed up and why
---
 .../Getting Started/latest/configure-backup-and-restore.md    | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/website/content/en/docs/Getting Started/latest/configure-backup-and-restore.md b/website/content/en/docs/Getting Started/latest/configure-backup-and-restore.md
index d4df095c..01d1ef72 100644
--- a/website/content/en/docs/Getting Started/latest/configure-backup-and-restore.md	
+++ b/website/content/en/docs/Getting Started/latest/configure-backup-and-restore.md	
@@ -7,6 +7,10 @@ description: >
   Prevent loss of job history
 ---
 
+> Because of Jenkins Operator's architecture, the configuration of Jenkins should be done using ConfigurationAsCode 
+> or GroovyScripts and jobs should be defined as SeedJobs. It means that there is no point in backing up any job configuration 
+> up. Therefore, the backup script makes a copy of jobs history only.
+
 Backup and restore is done by a container sidecar.
 
 ### PVC