docs: mention DWO_NAMESPACE env var in backup docs

modules/administration-guide/pages/devworkspace-backup-integrated-openshift-registry.adoc

@@ -45,3 +45,5 @@ echo "https://$(oc get route default-route -n openshift-image-registry --templat
 
 Once the backup job is finished, the backup archives will be available in the {devworkspace} {namespace} under a repository
 with a matching {devworkspace} name.
+
+include::partial$snip_defining-dwo-namespace-for-backups.adoc[]

modules/administration-guide/pages/devworkspace-backup-regular-oci-registry.adoc

@@ -33,6 +33,8 @@ config:
 ----
 <1> For Red Hat OpenShift, the default installation namespace for the {devworkspace} operator is `openshift-operators`. See the xref:devworkspace-operator.adoc[{devworkspace} operator overview].
 
+include::partial$snip_defining-dwo-namespace-for-backups.adoc[]
+
 The `authSecret` must be named `devworkspace-backup-registry-auth`. It must reference a {kubernetes} Secret of type `kubernetes.io/dockerconfigjson` that contains credentials to access the registry.
 The secret should be created in the installation {namespace} for the {devworkspace} operator.
 

modules/administration-guide/partials/snip_defining-dwo-namespace-for-backups.adoc

@@ -0,0 +1,18 @@
+:_content-type: SNIPPET
+
+**Note:** If the installation {namespace} for the {devworkspace} operator is not `openshift-operators`, you must define it as an environment variable for the {prod} dashboard in the `CheCluster` Custom Resource.
+
+[source,yaml,subs="+attributes,+quotes"]
+----
+apiVersion: org.eclipse.che/v2
+kind: CheCluster
+spec:
+  components:
+    dashboard:
+      deployment:
+        containers:
+          - env:
+              - name: DWO_NAMESPACE
+                value: $OPERATOR_INSTALL_NAMESPACE
+            name: che-dashboard
+----