Repository: openshift/openshift-docs
Pull request #89068: OADP-5634: Add new structure for 3scale user story
Author: login: apurvabhide17
Labels: name: peer-review-in-progress
description: Signifies that the peer review team is reviewing this PR
name: size/XL
description: Denotes a PR that changes 500-999 lines, ignoring generated files.
name: merge-review-in-progress
description: Signifies that the merge review team is reviewing this PR
name: OADP
description: Label for all OADP PRs
name: jira/valid-reference
description: Indicates that this PR references a valid Jira ticket of any type.
name: branch/enterprise-4.14
name: branch/enterprise-4.15
name: branch/enterprise-4.16
name: branch/enterprise-4.17
name: branch/enterprise-4.18
name: branch/enterprise-4.19
Created: 2025-02-24T14:38:16Z | Merged: 2025-04-30T16:03:08Z

Version(s):
OCP 4.14 → OCP 4.19

Issue:
[OADP-5634](https://issues.redhat.com/browse/OADP-5634)

Link to docs preview:

- [Backing up and restoring 3scale API Management by using OADP
](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-api-management-by-using-oadp)
- [Backing up 3scale API Management by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp)
- [Restoring 3scale API Management by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp)

QE review:
- [x] QE has approved this change.

Additional information - 
This PR focuses on the following points to improve the existing [Backing up and restoring 3scale by using OADP](https://docs.openshift.com/container-platform/4.17/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.html). user story from the related PR - [PR#85994](https://github.com/openshift/openshift-docs/pull/85994) - 

- Updating description/command for oc get deployment -n threescale and oc edit deployment system-mysql -n threescale.

Structural changes to split Backing up and restoring 3scale by using OADP:

- Backing up 3scale
-- Creating the Data Protection Application
-- Backing up the 3scale Operator
-- Backing up the mysql database
-- Backing up the backend Redis database

- Restoring 3scale
-- Restoring the secrets and APIManager
-- Restoring the mysql database
-- Restoring the back-end Redis database
-- Scaling up the 3scale operator and deployment


Diff:
diff --git a/_topic_maps/_topic_map.yml b/_topic_maps/_topic_map.yml
index 73a457a71471..dadc4a653da3 100644
--- a/_topic_maps/_topic_map.yml
+++ b/_topic_maps/_topic_map.yml
@@ -3658,8 +3658,12 @@ Topics:
   - Name: OADP and 3scale
     Dir: oadp-3scale
     Topics:
-    - Name: Backing up and restoring 3scale by using OADP
-      File: backing-up-and-restoring-3scale-by-using-oadp
+    - Name: Backing up and restoring 3scale API Management by using OADP
+      File: backing-up-and-restoring-3scale-api-management-by-using-oadp
+    - Name: Backing up 3scale API Management by using OADP
+      File: backing-up-3scale-api-management-by-using-oadp
+    - Name: Restoring 3scale API Management by using OADP
+      File: restoring-3scale-api-management-by-using-oadp
   - Name: OADP Data Mover
     Dir: installing
     Topics:
diff --git a/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.adoc b/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.adoc
new file mode 100644
index 000000000000..38c62d67319c
--- /dev/null
+++ b/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.adoc
@@ -0,0 +1,31 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-api-management-by-using-oadp"]
+= Backing up 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-api-management-by-using-oadp
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://docs.redhat.com/en/documentation/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
+toc::[]
+
+You can back up Red{nbsp}Hat 3scale API Management components by backing up the 3scale operator, and databases such as MySQL and Redis.
+
+.Prerequisites
+
+* You installed and configured Red{nbsp}Hat 3scale API Management. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management[Red Hat 3scale API Management].
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator-secret-apimanager.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+
+include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
+
+include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+1]
\ No newline at end of file
diff --git a/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-api-management-by-using-oadp.adoc b/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-api-management-by-using-oadp.adoc
new file mode 100644
index 000000000000..021db02dddf9
--- /dev/null
+++ b/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-api-management-by-using-oadp.adoc
@@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-and-restoring-3scale-api-management-by-using-oadp"]
+= Backing up and restoring 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-and-restoring-3scale-api-management-by-using-oadp
+
+toc::[]
+
+With Red{nbsp}Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale API Management deployments by backing up application resources, persistent volumes, and configurations. 
+
+[NOTE]
+====
+You can use the {oadp-first} Operator to back up and restore your 3scale API Management on-cluster storage databases without affecting your running services
+====
+
+You can configure OADP to perform the following operations with 3scale API Management: 
+
+* Create a backup of 3scale components by following the steps in xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.adoc#backing-up-3scale-api-management-by-using-oadp[Backing up 3scale API Management].
+* Restore the components to scale up the 3scale operator and deployment by following the steps in xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc#restoring-3scale-api-management-by-using-oadp[Restoring 3scale API Management].
+
+
+
+
+
diff --git a/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc b/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
deleted file mode 100644
index 7381a8a42e7a..000000000000
--- a/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
+++ /dev/null
@@ -1,43 +0,0 @@
-:_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
-= Backing up and restoring 3scale by using OADP
-include::_attributes/common-attributes.adoc[]
-:context: backing-up-and-restoring-3scale-by-using-oadp
-
-toc::[]
-
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
-
-[NOTE]
-====
-In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator.
-Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
-====
-
-.Prerequisites
-
-* You installed and configured Red Hat 3scale. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management[Red Hat 3scale API Management].
-
-include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
-
-include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
-
-include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
-
-include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+1]
-
-include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]
-
-include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]
-
-include::modules/restoring-the-backend-redis-database.adoc[leveloffset=+1]
-
-include::modules/scaling-up-the-3scale-operator-and-deployment.adoc[leveloffset=+1]
\ No newline at end of file
diff --git a/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc b/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc
new file mode 100644
index 000000000000..9326a37459e8
--- /dev/null
+++ b/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc
@@ -0,0 +1,32 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-api-management-by-using-oadp"]
+= Restoring 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-api-management-by-using-oadp
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://docs.redhat.com/en/documentation/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
+toc::[]
+
+You can restore Red{nbsp}Hat 3scale API Management components by restoring the backed up 3scale operator resources. You can also restore databases such as MySQL and Redis. 
+
+After the data has been restored, you can scale up the 3scale operator and deployment. 
+
+.Prerequisites
+
+* You installed and configured Red{nbsp}Hat 3scale API Management. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management[Red Hat 3scale API Management].
+
+* You backed up the 3scale operator, and databases such as MySQL and Redis.
+
+* Ensure that you are restoring 3scale on the same cluster where it was backed up from. 
+
+* If you want to restore 3scale on a different cluster, ensure that the original backed-up cluster and the cluster you want to restore the operator on are using the same custom domain.
+
+include::modules/restoring-the-3scale-api-management-operator-secrets-and-apimanager.adoc[leveloffset=+1]
+
+include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]
+
+include::modules/restoring-the-backend-redis-database.adoc[leveloffset=+1]
+
+include::modules/scaling-up-the-3scale-api-management-operator-and-deployment.adoc[leveloffset=+1]
\ No newline at end of file
diff --git a/modules/backing-up-the-3scale-operator.adoc b/modules/backing-up-the-3scale-operator-secret-apimanager.adoc
similarity index 55%
rename from modules/backing-up-the-3scale-operator.adoc
rename to modules/backing-up-the-3scale-operator-secret-apimanager.adoc
index 2360281b88d5..e74139107194 100644
--- a/modules/backing-up-the-3scale-operator.adoc
+++ b/modules/backing-up-the-3scale-operator-secret-apimanager.adoc
@@ -1,11 +1,11 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in backing-up-3scale-api-management-by-using-oadp.adoc assembly
 
-[id="backing-up-the-3scale-operator_{context}"]
-= Backing up the 3scale Operator
+[id="backing-up-the-3scale-operator-secret-apimanager_{context}"]
+= Backing up the 3scale API Management operator, secret, and APIManager
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the Red{nbsp}Hat 3scale API Management operator resources, and both the `Secret` and APIManager custom resource (CR).
 
 .Prerequisites
 
@@ -13,7 +13,7 @@ You can back up the Operator resources, and Secret and APIManager custom resourc
 
 .Procedure
 
-. Back up the Operator resources, such as `operatorgroup`, `namespaces`, and `subscriptions`, by creating a YAML file with the following configuration: 
+. Back up your 3scale operator CRs, such as `operatorgroup`, `namespaces`, and `subscriptions`, by creating a YAML file with the following configuration: 
 +
 .Example `backup.yaml` file
 +
@@ -22,13 +22,13 @@ You can back up the Operator resources, and Secret and APIManager custom resourc
 apiVersion: velero.io/v1
 kind: Backup
 metadata:
-  name: operator-install-backup
+  name: operator-install-backup <1>
   namespace: openshift-adp
 spec:
   csiSnapshotTimeout: 10m0s
   defaultVolumesToFsBackup: false
   includedNamespaces:
-  - threescale   <1>
+  - threescale   <2>
   includedResources:
   - operatorgroups
   - subscriptions
@@ -37,7 +37,8 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> Namespace where the 3scale Operator is installed.
+<1> The value of the `metadata.name` parameter in the backup is the same value used in the `metadata.backupName` parameter used when restoring the 3scale operator.
+<2> Namespace where the 3scale operator is installed.
 +
 [NOTE]
 ====
@@ -50,8 +51,15 @@ You can also back up and restore `ReplicationControllers`, `Deployment`, and `Po
 ----
 $ oc create -f backup.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+backup.velero.io/operator-install-backup created
+----
 
-. Back up the Secret CR by creating a YAML file with the following configuration:
+. Back up the `Secret` CR by creating a YAML file with the following configuration:
 +
 .Example `backup-secret.yaml` file
 +
@@ -60,7 +68,7 @@ $ oc create -f backup.yaml
 apiVersion: velero.io/v1
 kind: Backup
 metadata:
-  name: operator-resources-secrets
+  name: operator-resources-secrets <1>
   namespace: openshift-adp
 spec:
   csiSnapshotTimeout: 10m0s
@@ -77,13 +85,21 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> The value of the `metadata.name` parameter in the backup is the same value used in the `metadata.backupName` parameter used when restoring the `Secret`.
 
-. Create the Secret CR by running the following command:
+. Create the `Secret` backup CR by running the following command:
 +
 [source,terminal]
 ----
 $ oc create -f backup-secret.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+backup.velero.io/operator-resources-secrets created
+----
 
 . Back up the APIManager CR by creating a YAML file with the following configuration:
 +
@@ -93,7 +109,7 @@ $ oc create -f backup-secret.yaml
 apiVersion: velero.io/v1
 kind: Backup
 metadata:
-  name: operator-resources-apim
+  name: operator-resources-apim <1>
   namespace: openshift-adp
 spec:
   csiSnapshotTimeout: 10m0s
@@ -110,6 +126,7 @@ spec:
   volumeSnapshotLocations:
   - ts-dpa-1
 ----
+<1> The value of the `metadata.name` parameter in the backup is the same value used in the `metadata.backupName` parameter used when restoring the APIManager.
 
 . Create the APIManager CR by running the following command:
 +
@@ -117,7 +134,10 @@ spec:
 ----
 $ oc create -f backup-apimanager.yaml
 ----
-
-.Next steps
-
-* Back up the `mysql` database.
\ No newline at end of file
++
+.Example output
++
+[source,terminal]
+----
+backup.velero.io/operator-resources-apim created
+----
\ No newline at end of file
diff --git a/modules/backing-up-the-backend-redis-database.adoc b/modules/backing-up-the-backend-redis-database.adoc
index 5848d9f81e9d..e27f3af02f72 100644
--- a/modules/backing-up-the-backend-redis-database.adoc
+++ b/modules/backing-up-the-backend-redis-database.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in backing-up-3scale-api-management-by-using-oadp.adoc assembly
 
 [id="backing-up-the-backend-redis-database_{context}"]
 = Backing up the back-end Redis database
@@ -10,8 +10,8 @@ You can back up the Redis database by adding the required annotations and by lis
 
 .Prerequisites
 
-* You backed up the 3scale Operator.
-* You backed up the mysql database.
+* You backed up the Red{nbsp}Hat 3scale API Management operator.
+* You backed up your MySQL database.
 * The Redis queues have been drained before performing the backup.
 
 
@@ -23,8 +23,6 @@ You can back up the Redis database by adding the required annotations and by lis
 ----
 $ oc edit deployment backend-redis -n threescale
 ----
-
-. Add the following annotations:
 +
 [source,yaml]
 ----
@@ -46,7 +44,7 @@ post.hook.backup.velero.io/command: >-
 apiVersion: velero.io/v1
 kind: Backup
 metadata:
-  name: redis-backup
+  name: redis-backup <1>
   namespace: openshift-adp
 spec:
   csiSnapshotTimeout: 10m0s
@@ -69,23 +67,44 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> The value of the `metadata.name` parameter in the backup is the same value used in the `metadata.backupName` parameter used when restoring the restoring the Redis database.
 
 . Back up the Redis database by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io redis-backup -o yaml
+$ oc create -f redis-backup.yaml
+----
++
+.Example output:
++
+[source,terminal]
 ----
+backup.velero.io/redis-backup created
+----
+
 
 .Verification
 
-* Verify that the Redis backup is completed by running the following command:: 
+* Verify that the Redis backup is completed by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io
+$ oc get backups.velero.io redis-backup -o yaml
 ----
-
-.Next steps
-
-* Restore the Secrets and APIManager CRs.
\ No newline at end of file
++
+.Example output:
++
+[source,terminal]
+----
+status:
+completionTimestamp: "2025-04-17T13:25:19Z"
+errors: 1
+expiration: "2025-05-17T13:25:16Z"
+formatVersion: 1.1.0
+hookStatus: {}
+phase: Completed
+progress: {}
+startTimestamp: "2025-04-17T13:25:16Z"
+version: 1
+----
\ No newline at end of file
diff --git a/modules/backing-up-the-mysql-database.adoc b/modules/backing-up-the-mysql-database.adoc
index e7470f470f38..68c7052f7646 100644
--- a/modules/backing-up-the-mysql-database.adoc
+++ b/modules/backing-up-the-mysql-database.adoc
@@ -1,15 +1,15 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in backing-up-3scale-api-management-by-using-oadp.adoc assembly
 
 [id="backing-up-the-mysql-database_{context}"]
-= Backing up the mysql database
+= Backing up a MySQL database
 
-You can back up the `mysql` database by creating and attaching a persistent volume claim (PVC) to include the dumped data in the specified path.
+You can back up a MySQL database by creating and attaching a persistent volume claim (PVC) to include the dumped data in the specified path.
 
 .Prerequisites
 
-* You have backed up the 3scale operator. 
+* You have backed up the Red{nbsp}Hat 3scale API Management operator. 
 
 .Procedure
 
@@ -40,7 +40,7 @@ spec:
 $ oc create -f ts_pvc.yml 
 ----
 
-. Attach the PVC to the system database pod by editing the system database deployment to use the `mysql` dump:
+. Attach the PVC to the system database pod by editing the `system-mysql` deployment to use the MySQL dump:
 +
 [source,terminal]
 ----
@@ -68,7 +68,7 @@ $ oc edit deployment system-mysql -n threescale
 ----
 <1> The PVC that contains the dumped data.
 
-. Create a YAML file with following configuration to back up the `mysql` database:
+. Create a YAML file with following configuration to back up the MySQL database:
 +
 .Example `mysql.yaml` file
 +
@@ -77,7 +77,7 @@ $ oc edit deployment system-mysql -n threescale
 apiVersion: velero.io/v1
 kind: Backup
 metadata:
-  name: mysql-backup
+  name: mysql-backup <1>
   namespace: openshift-adp
 spec:
   csiSnapshotTimeout: 10m0s
@@ -91,13 +91,13 @@ spec:
           - /bin/sh
           - -c
           - mysqldump -u $MYSQL_USER --password=$MYSQL_PASSWORD system --no-tablespaces
-            > /var/lib/mysqldump/data/dump.sql <1>
+            > /var/lib/mysqldump/data/dump.sql <2>
           container: system-mysql
           onError: Fail
           timeout: 5m
-  includedNamespaces: <2>
+  includedNamespaces: 
   - threescale
-  includedResources:
+  includedResources: <3>
   - deployment
   - pods
   - replicationControllers
@@ -111,34 +111,45 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> A directory where the data is backed up.
-<2> Resources to back up.
+<1> The value of the `metadata.name` parameter in the backup is the same value used in the `metadata.backupName` parameter used when restoring the MySQL database.
+<2> A directory where the data is backed up.
+<3> Resources to back up.
 
-. Back up the `mysql` database by running the following command:
+. Back up the MySQL database by running the following command:
 +
 [source,terminal]
 ----
 $ oc create -f mysql.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+backup.velero.io/mysql-backup created
+----
 
 .Verification
 
-* Verify that the `mysql` backup is completed by running the following command:
+* Verify that the MySQL backup is completed by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io mysql-backup
+$ oc get backups.velero.io mysql-backup -o yaml
 ----
 +
 .Example output
 +
 [source,terminal]
 ----
-NAME                  STATUS      CREATED   NAMESPACE    POD                    VOLUME          UPLOADER TYPE   STORAGE LOCATION   AGE
-mysql-backup-4g7qn   Completed   30s       threescale   system-mysql-2-9pr44   example-claim   kopia           ts-dpa-1           30s
-mysql-backup-smh85   Completed   23s       threescale   system-mysql-2-9pr44   mysql-storage   kopia           ts-dpa-1           30s
-----
-
-.Next steps
-
-* Back up the back-end Redis database.
\ No newline at end of file
+status:
+completionTimestamp: "2025-04-17T13:25:19Z"
+errors: 1
+expiration: "2025-05-17T13:25:16Z"
+formatVersion: 1.1.0
+hookStatus: {}
+phase: Completed
+progress: {}
+startTimestamp: "2025-04-17T13:25:16Z"
+version: 1
+----
\ No newline at end of file
diff --git a/modules/creating-the-data-protection-application.adoc b/modules/creating-the-data-protection-application.adoc
index f9c353576f7a..4b36830bebe8 100644
--- a/modules/creating-the-data-protection-application.adoc
+++ b/modules/creating-the-data-protection-application.adoc
@@ -1,11 +1,11 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in backing-up-3scale-api-management-by-using-oadp.adoc assembly
 
 [id="creating-the-data-protection-application_{context}"]
 = Creating the Data Protection Application
 
-You can create a Data Protection Application (DPA) custom resource (CR) for 3scale. For more information on DPA, see "Installing the Data Protection Application".
+You can create a Data Protection Application (DPA) custom resource (CR) for Red{nbsp}Hat 3scale API Management.
 
 .Procedure
 
@@ -18,7 +18,7 @@ You can create a Data Protection Application (DPA) custom resource (CR) for 3sca
 apiVersion: oadp.openshift.io/v1alpha1
 kind: DataProtectionApplication
 metadata:
-  name: dpa_sample
+  name: dpa-sample
   namespace: openshift-adp 
 spec:
   configuration:
@@ -58,8 +58,4 @@ spec:
 [source,terminal]
 ----
 $ oc create -f dpa.yaml
-----
-
-.Next steps
-
-* Back up the 3scale Operator.
\ No newline at end of file
+----
\ No newline at end of file
diff --git a/modules/restoring-the-secrets-and-apimanager.adoc b/modules/restoring-the-3scale-api-management-operator-secrets-and-apimanager.adoc
similarity index 59%
rename from modules/restoring-the-secrets-and-apimanager.adoc
rename to modules/restoring-the-3scale-api-management-operator-secrets-and-apimanager.adoc
index a67eef2fa470..df4de2e32400 100644
--- a/modules/restoring-the-secrets-and-apimanager.adoc
+++ b/modules/restoring-the-3scale-api-management-operator-secrets-and-apimanager.adoc
@@ -1,24 +1,24 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in restoring-3scale-api-management-by-using-oadp assembly
 
 
-[id="restoring-the-secrets-and-apimanager_{context}"]
-= Restoring the secrets and APIManager
+[id="restoring-the-3scale-api-management-operator-secrets-and-apimanager_{context}"]
+= Restoring the 3scale API Management operator, secrets, and APIManager
 
-You can restore the Secrets and APIManager by using the following procedure.
+You can restore the Red{nbsp}Hat 3scale API Management operator resources, and both the `Secret` and APIManager custom resources (CRs) by using the following procedure.
 
 .Prerequisites
 
-* You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up the 3scale operator.
+* You backed up the MySQL and Redis databases.
 * You are restoring the database on the same cluster, where it was backed up. 
 +
-If it is on a different cluster, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster as it was on the source cluster.
+If you are restoring the operator to a different cluster that you backed up from, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster. Ensure that the {oadp-short} configuration is same as it was on the source cluster.
 
 .Procedure
 
-. Delete the 3scale Operator custom resource definitions (CRDs) along with the `threescale` namespace by running the following command:
+. Delete the 3scale operator custom resource definitions (CRDs) along with the `threescale` namespace by running the following command:
 +
 [source,terminal]
 ----
@@ -32,7 +32,7 @@ $ oc delete project threescale
 "threescale" project deleted successfully
 ----
 
-. Create a YAML file with the following configuration to restore the 3scale Operator:
+. Create a YAML file with the following configuration to restore the 3scale operator:
 +
 .Example `restore.yaml` file
 +
@@ -44,7 +44,7 @@ metadata:
   name: operator-installation-restore
   namespace: openshift-adp
 spec:
-  backupName: operator-install-backup
+  backupName: operator-install-backup <1>
   excludedResources:
   - nodes
   - events
@@ -57,15 +57,23 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
+<1> Restoring the 3scale operator's backup
 
-. Restore the 3scale Operator by running the following command:
+. Restore the 3scale operator by running the following command:
 +
 [source,terminal]
 ----
 $ oc create -f restore.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+restore.velerio.io/operator-installation-restore created
+----
 
-. Manually create the `s3-credentials` Secret object by running the following command:
+. Manually create the `s3-credentials` `Secret` object by running the following command:
 +
 [source,terminal]
 ----
@@ -89,14 +97,21 @@ EOF
 <3> Replace <mybucket.example.com> with your target bucket name.
 <4> Replace <us-east-1> with the AWS region of your bucket.
 
-. Scale down the 3scale Operator by running the following command:
+. Scale down the 3scale operator by running the following command:
 +
 [source,terminal]
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=0 -n threescale
 ----
++
+.Example output
++
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
 
-. Create a YAML file with the following configuration to restore the Secrets:
+. Create a YAML file with the following configuration to restore the `Secret`:
 +
 .Example `restore-secret.yaml` file
 +
@@ -108,7 +123,7 @@ metadata:
   name: operator-resources-secrets
   namespace: openshift-adp
 spec:
-  backupName: operator-resources-secrets
+  backupName: operator-resources-secrets <1>
   excludedResources:
   - nodes
   - events
@@ -121,13 +136,21 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
+<1> Restoring the `Secret` backup.
 
-. Restore the Secrets by running the following command:
+. Restore the `Secret` by running the following command:
 +
 [source,terminal]
 ----
 $ oc create -f restore-secrets.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+restore.velerio.io/operator-resources-secrets created
+----
 
 . Create a YAML file with the following configuration to restore APIManager:
 +
@@ -140,8 +163,8 @@ metadata:
   name: operator-resources-apim
   namespace: openshift-adp
 spec:
-  backupName: operator-resources-apim
-  excludedResources: <1>
+  backupName: operator-resources-apim <1>
+  excludedResources: <2>
   - nodes
   - events
   - events.events.k8s.io
@@ -153,7 +176,8 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
-<1> The resources that you do not want to restore.
+<1> Restoring the APIManager backup.
+<2> The resources that you do not want to restore.
 
 . Restore the APIManager by running the following command:
 +
@@ -161,14 +185,24 @@ spec:
 ----
 $ oc create -f restore-apimanager.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+restore.velerio.io/operator-resources-apim created
+----
 
-. Scale up the 3scale Operator by running the following command:
+. Scale up the 3scale operator by running the following command:
 +
 [source,terminal]
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
-
-.Next steps
-
-* Restore the `mysql` database.
\ No newline at end of file
++
+.Example output
++
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
\ No newline at end of file
diff --git a/modules/restoring-the-backend-redis-database.adoc b/modules/restoring-the-backend-redis-database.adoc
index 623d7272d0be..01a346d27c28 100644
--- a/modules/restoring-the-backend-redis-database.adoc
+++ b/modules/restoring-the-backend-redis-database.adoc
@@ -1,6 +1,6 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in restoring-3scale-api-management-by-using-oadp assembly
 
 [id="restoring-the-backend-redis-database_{context}"]
 = Restoring the back-end Redis database
@@ -9,8 +9,8 @@ You can restore the back-end Redis database by deleting the deployment and speci
 
 .Prerequisites
 
-* You restored the Secret and APIManager custom resources.
-* You restored the `mysql` database.
+* You restored the Red{nbsp}Hat 3scale API Management operator resources, `Secret`, and APIManager custom resources.
+* You restored the MySQL database.
 
 .Procedure
 
@@ -41,7 +41,7 @@ metadata:
   name: restore-backend
   namespace: openshift-adp
 spec:
-  backupName: redis-backup
+  backupName: redis-backup <1>
   excludedResources:
     - nodes
     - events
@@ -55,6 +55,7 @@ spec:
   itemOperationTimeout: 1h0m0s
   restorePVs: true
 ----
+<1> Restoring the Redis backup.
 
 . Restore the Redis database by running the following command:
 +
@@ -62,6 +63,13 @@ spec:
 ----
 $ oc create -f restore-backend.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+restore.velerio.io/restore-backend created
+----
 
 .Verification 
 
@@ -77,8 +85,4 @@ $ oc get podvolumerestores.velero.io -n openshift-adp
 ----
 NAME                    NAMESPACE    POD                     UPLOADER TYPE   VOLUME                  STATUS      TOTALBYTES   BYTESDONE   AGE
 restore-backend-jmrwx   threescale   backend-redis-1-bsfmv   kopia           backend-redis-storage   Completed   76123        76123       21m
-----
-
-.Next steps
-
-* Scale the 3scale Operator and deployment.
\ No newline at end of file
+----
\ No newline at end of file
diff --git a/modules/restoring-the-mysql-database.adoc b/modules/restoring-the-mysql-database.adoc
index 7dabb625656b..6db14c702048 100644
--- a/modules/restoring-the-mysql-database.adoc
+++ b/modules/restoring-the-mysql-database.adoc
@@ -1,15 +1,15 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in restoring-3scale-api-management-by-using-oadp assembly
 
 [id="restoring-the-mysql-database_{context}"]
-= Restoring the mysql database
+= Restoring a MySQL database
 
-Restoring the `mysql` database re-creates the following resources:
+Restoring a MySQL database re-creates the following resources:
 
 * The `Pod`, `ReplicationController`, and `Deployment` objects.
 * The additional persistent volumes (PVs) and associated persistent volume claims (PVCs). 
-* The `mysql` dump, which the `example-claim` PVC contains.
+* The MySQL dump, which the `example-claim` PVC contains.
 
 [WARNING]
 ====
@@ -18,11 +18,11 @@ Do not delete the default PV and PVC associated with the database. If you do, yo
 
 .Prerequisites
 
-* You restored the Secret and APIManager custom resources (CR).
+* You restored the `Secret` and APIManager custom resources (CRs).
 
 .Procedure
 
-. Scale down the 3scale Operator by running the following command:
+. Scale down the Red{nbsp}Hat 3scale API Management operator by running the following command:
 +
 [source,terminal]
 ----
@@ -42,7 +42,7 @@ deployment.apps/threescale-operator-controller-manager-v2 scaled
 $ vi ./scaledowndeployment.sh
 ----
 +
-.Example output:
+.Example script:
 [source,terminal]
 ----
 for deployment in apicast-production apicast-staging backend-cron backend-listener backend-redis backend-worker system-app system-memcache system-mysql system-redis system-searchd system-sidekiq zync zync-database zync-que; do
@@ -91,7 +91,7 @@ Warning: apps.openshift.io/v1 deployment is deprecated in v4.14+, unavailable in
 deployment.apps.openshift.io "system-mysql" deleted
 ----
 
-. Create the following YAML file to restore the `mysql` database:
+. Create the following YAML file to restore the MySQL database:
 +
 .Example `restore-mysql.yaml` file
 [source,yaml]
@@ -102,7 +102,7 @@ metadata:
   name: restore-mysql
   namespace: openshift-adp
 spec:
-  backupName: mysql-backup
+  backupName: mysql-backup <1>
   excludedResources:
     - nodes
     - events
@@ -126,7 +126,7 @@ spec:
                   
                   mysql -h 127.0.0.1 -D system -u root
                   --password=$MYSQL_ROOT_PASSWORD <
-                  /var/lib/mysqldump/data/dump.sql <1>
+                  /var/lib/mysqldump/data/dump.sql <2>
               container: system-mysql
               execTimeout: 80s
               onError: Fail
@@ -134,14 +134,22 @@ spec:
   itemOperationTimeout: 1h0m0s
   restorePVs: true
 ----
-<1> A path where the data is restored from.
+<1> Restoring the MySQL backup.
+<2> A path where the data is restored from.
 
-. Restore the `mysql` database by running the following command:
+. Restore the MySQL database by running the following command:
 +
 [source,terminal]
 ----
 $ oc create -f restore-mysql.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+restore.velerio.io/restore-mysql created
+----
 
 .Verification 
 
@@ -176,8 +184,4 @@ example-claim           Bound    pvc-cbaa49b0-06cd-4b1a-9e90-0ef755c67a54   1Gi
 mysql-storage           Bound    pvc-4549649f-b9ad-44f7-8f67-dd6b9dbb3896   1Gi        RWO            gp3-csi        <unset>                 68m
 system-redis-storage    Bound    pvc-04dadafd-8a3e-4d00-8381-6041800a24fc   1Gi        RWO            gp3-csi        <unset>                 68m
 system-searchd          Bound    pvc-afbf606c-d4a8-4041-8ec6-54c5baf1a3b9   1Gi        RWO            gp3-csi        <unset>                 68m
-----
-
-.Next steps
-
-* Restore the back-end Redis database.
\ No newline at end of file
+----
\ No newline at end of file
diff --git a/modules/scaling-up-the-3scale-api-management-operator-and-deployment.adoc b/modules/scaling-up-the-3scale-api-management-operator-and-deployment.adoc
new file mode 100644
index 000000000000..a1b4193df2ee
--- /dev/null
+++ b/modules/scaling-up-the-3scale-api-management-operator-and-deployment.adoc
@@ -0,0 +1,110 @@
+:_mod-docs-content-type: PROCEDURE
+
+//included in restoring-3scale-api-management-by-using-oadp assembly assembly
+
+[id="scaling-up-the-3scale-api-management-operator-and-deployment_{context}"]
+= Scaling up the 3scale API Management operator and deployment
+
+You can scale up the Red{nbsp}Hat 3scale API Management operator and any deployment that was manually scaled down. After a few minutes, 3scale installation should be fully functional, and its state should match the backed-up state.
+
+.Prerequisites
+
+* You restored the 3scale operator resources, and both the `Secret` and APIManager custom resources (CRs).
+* You restored the MySQL and back-end Redis databases.
+* Ensure that there are no scaled up deployments or no extra pods running.
+There might be some `system-mysql` or `backend-redis` pods running detached from deployments after restoration, which can be removed after the restoration is successful.
+
+
+.Procedure
+
+. Scale up the 3scale operator by running the following command:
++
+[source,terminal]
+----
+$ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
+----
++
+.Example output
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
+
+. Ensure that the 3scale pod is running to verify if the 3scale operator was deployed by running the following command: 
++
+[source,terminal]
+----
+$ oc get pods -n threescale
+----
++
+.Example output
+[source,terminal]
+----
+NAME									                    READY        STATUS	  RESTARTS	 AGE
+threescale-operator-controller-manager-v2-79546bd8c-b4qbh	1/1	         Running  0          2m5s
+----
+
+. Create the following script to scale up the deployments:
++
+[source,terminal]
+----
+$ vi ./scaledeployment.sh
+----
++
+.Example script file:
+[source,terminal]
+----
+for deployment in apicast-production apicast-staging backend-cron backend-listener backend-redis backend-worker system-app system-memcache system-mysql system-redis system-searchd system-sidekiq zync zync-database zync-que; do
+    oc scale deployment/$deployment --replicas=1 -n threescale
+done
+----
+
+. Scale up the deployments by running the following script:
++
+[source,terminal]
+----
+$ ./scaledeployment.sh 
+----
++
+.Example output:
+[source,terminal]
+----
+deployment.apps.openshift.io/apicast-production scaled
+deployment.apps.openshift.io/apicast-staging scaled
+deployment.apps.openshift.io/backend-cron scaled
+deployment.apps.openshift.io/backend-listener scaled
+deployment.apps.openshift.io/backend-redis scaled
+deployment.apps.openshift.io/backend-worker scaled
+deployment.apps.openshift.io/system-app scaled
+deployment.apps.openshift.io/system-memcache scaled
+deployment.apps.openshift.io/system-mysql scaled
+deployment.apps.openshift.io/system-redis scaled
+deployment.apps.openshift.io/system-searchd scaled
+deployment.apps.openshift.io/system-sidekiq scaled
+deployment.apps.openshift.io/zync scaled
+deployment.apps.openshift.io/zync-database scaled
+deployment.apps.openshift.io/zync-que scaled
+----
+
+. Get the `3scale-admin` route to log in to the 3scale UI by running the following command:
++
+[source,terminal]
+----
+$ oc get routes -n threescale
+----
++
+.Example output
+[source,terminal]
+----
+NAME                         HOST/PORT                                                                   PATH   SERVICES             PORT      TERMINATION     WILDCARD
+backend                      backend-3scale.apps.custom-cluster-name.openshift.com                         backend-listener     http      edge/Allow      None
+zync-3scale-api-b4l4d        api-3scale-apicast-production.apps.custom-cluster-name.openshift.com          apicast-production   gateway   edge/Redirect   None
+zync-3scale-api-b6sns        api-3scale-apicast-staging.apps.custom-cluster-name.openshift.com             apicast-staging      gateway   edge/Redirect   None
+zync-3scale-master-7sc4j     master.apps.custom-cluster-name.openshift.com                                 system-master        http      edge/Redirect   None
+zync-3scale-provider-7r2nm   3scale-admin.apps.custom-cluster-name.openshift.com                           system-provider      http      edge/Redirect   None
+zync-3scale-provider-mjxlb   3scale.apps.custom-cluster-name.openshift.com                                 system-developer     http      edge/Redirect   None
+----
++
+In this example, `3scale-admin.apps.custom-cluster-name.openshift.com` is the 3scale-admin URL.
+
+. Use the URL from this output to log in to the 3scale operator as an administrator. You can verify that the data, when you took backup, is available.
\ No newline at end of file
diff --git a/modules/scaling-up-the-3scale-operator-and-deployment.adoc b/modules/scaling-up-the-3scale-operator-and-deployment.adoc
deleted file mode 100644
index 3184fd2be9d3..000000000000
--- a/modules/scaling-up-the-3scale-operator-and-deployment.adoc
+++ /dev/null
@@ -1,60 +0,0 @@
-:_mod-docs-content-type: PROCEDURE
-
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
-
-[id="scaling-up-the-3scale-operator-and-deployment_{context}"]
-= Scaling up the 3scale Operator and deployment
-
-You can scale up the 3scale Operator and any deployment that was manually scaled down. After a few minutes, 3scale installation should be fully functional, and its state should match the backed-up state.
-
-.Prerequisites
-
-* Ensure that there are no scaled up deployments or no extra pods running.
-There might be some `system-mysql` or `backend-redis` pods running detached from deployments after restoration, which can be removed after the restoration is successful.
-
-
-.Procedure
-
-. Scale up the 3scale Operator by running the following command:
-+
-[source,terminal]
-----
-$ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
-----
-
-. Ensure that the 3scale Operator was deployed by running the following command: 
-+
-[source,terminal]
-----
-$ oc get deployment -n threescale
-----
-
-. Scale up the deployments by executing the following script:
-+
-[source,terminal]
-----
-$ ./scaledeployment.sh
-----
-
-. Get the `3scale-admin` route to log in to the 3scale UI by running the following command:
-+
-[source,terminal]
-----
-$ oc get routes -n threescale
-----
-+
-.Example output
-[source,terminal]
-----
-NAME                         HOST/PORT                                                                   PATH   SERVICES             PORT      TERMINATION     WILDCARD
-backend                      backend-3scale.apps.custom-cluster-name.openshift.com                         backend-listener     http      edge/Allow      None
-zync-3scale-api-b4l4d        api-3scale-apicast-production.apps.custom-cluster-name.openshift.com          apicast-production   gateway   edge/Redirect   None
-zync-3scale-api-b6sns        api-3scale-apicast-staging.apps.custom-cluster-name.openshift.com             apicast-staging      gateway   edge/Redirect   None
-zync-3scale-master-7sc4j     master.apps.custom-cluster-name.openshift.com                                 system-master        http      edge/Redirect   None
-zync-3scale-provider-7r2nm   3scale-admin.apps.custom-cluster-name.openshift.com                           system-provider      http      edge/Redirect   None
-zync-3scale-provider-mjxlb   3scale.apps.custom-cluster-name.openshift.com                                 system-developer     http      edge/Redirect   None
-----
-+
-In this example, `3scale-admin.apps.custom-cluster-name.openshift.com` is the 3scale-admin URL.
-
-. Use the URL from this output to log in to the 3scale Operator as an administrator. You can verify that the existing data is available before trying to create a backup.
\ No newline at end of file


Reviews:
user: login: ocpdocs-vale-bot
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-03T18:59:22Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:01:38Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:02:01Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:02:53Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:03:34Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:04:34Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:05:37Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:07:27Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-04T22:12:26Z
user: login: dfennessy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-05T10:54:09Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T18:35:01Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T18:36:13Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:06:08Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:08:36Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:09:00Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:09:16Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:14:59Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:23:25Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:30:24Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:38:31Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:39:59Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:43:25Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:46:16Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:48:31Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T19:49:59Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T20:02:43Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T20:08:17Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T20:18:40Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-10T22:50:15Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-13T18:51:02Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-13T18:51:10Z
user: login: shdeshpa07
body: Left a few comments. I have a few suggestions for consistency with other OADP doc sets. Please let me know if you have questions. Thanks!
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-18T06:08:45Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-21T18:16:05Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-21T18:17:48Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-21T18:22:40Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-21T18:24:20Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-21T18:54:50Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-21T18:59:14Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-24T18:17:48Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-24T18:18:00Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-24T18:19:57Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-24T18:20:09Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-24T18:20:25Z
user: login: stillalearner
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-03T07:00:27Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T07:13:03Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-03T13:34:10Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T18:37:18Z
user: login: stillalearner
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-16T07:13:08Z
user: login: stillalearner
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-16T07:13:46Z
user: login: stillalearner
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-16T07:15:54Z
user: login: stillalearner
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-17T13:27:45Z
user: login: stillalearner
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-17T13:28:28Z
user: login: stillalearner
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-17T13:29:19Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-21T06:17:46Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-21T06:18:01Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-21T06:18:09Z
user: login: stillalearner
body: lgtm
state: APPROVED
author_association: NONE
submitted_at: 2025-04-21T13:08:18Z
user: login: ShaunaDiaz
body: I think you need to determine the product or component naming that should be used. A lot of places need solid explanatory text that is missing; this PR feels unfinished and not truly ready for peer review. Please make changes and put back in peer review prior to submitting for merge review.
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-22T14:39:28Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-28T18:51:19Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-29T13:39:04Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-29T13:41:01Z
user: login: stevsmit
body: This looks really good overall, and nothing I've commented should hold up a merge. I've left a few comments for you to consider in a future PR. One thing I've noticed is that, in our docs, we sometimes either capitalize 3scale Operator and in your PR you do not. Maybe the official name isn't capitalized, or maybe it is. Generally for OCP we require Operator to be capitalized, but there needs to be some consistency between what's in the docs now (whether that requires changed it to a capital O or lowercase o). 

Overall, good work! 
state: COMMENTED
author_association: MEMBER
submitted_at: 2025-04-30T16:02:55Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-30T17:39:07Z
user: login: apurvabhide17
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-30T17:40:30Z

Review comments:
diff_hunk: @@ -15,29 +15,9 @@ In this example, the non-service affecting approach is used to back up and resto
 Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
 ====
 
+You can xref:../oadp-3scale/backing-up-3scale-by-using-oadp.adoc[back up 3scale] and xref:../oadp-3scale/restoring-3scale-by-using-oadp.adoc[restore 3scale] by using OADP.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ocpdocs-vale-bot
body: 🤖 **[error] OpenShiftAsciiDoc.XrefContainsAnchorID**: The xref is missing an anchor ID. 
created_at: 2025-03-03T18:59:22Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,24 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+
+include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
include::modules/backing-up-the-mysql-database.adoc[leveloffset=+2]
```
created_at: 2025-03-04T22:01:37Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,24 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+
+include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
+
+include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+2]
```
created_at: 2025-03-04T22:02:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,24 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
Add a *Back up use cases* section 
```
created_at: 2025-03-04T22:02:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,24 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
You can back up 3scale by backing up 3scale Operator. 

You can also backup and databases such as MySQL and Redis.
```
created_at: 2025-03-04T22:03:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,9 +1,13 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
 With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: this introduction could be improved upon. it reads a bit like a marketing brief
created_at: 2025-03-04T22:04:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -15,29 +19,9 @@ In this example, the non-service affecting approach is used to back up and resto
 Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
 ====
 
-.Prerequisites
-
-* You installed and configured Red Hat 3scale. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management[Red Hat 3scale API Management].
-
-include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
-
-include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
+You can xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[back up 3scale] and xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc#restoring-3scale-by-using-oadp[restore 3scale] by using OADP.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: this would be better split into two lines, possibly bullet-pointed

![image](https://github.com/user-attachments/assets/ecedc0b3-8a88-4abe-8e08-3cb4bb5a66a3)

think of user navigating this document in the context of this sentence
created_at: 2025-03-04T22:05:37Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,17 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore the 3scale by restoring the backed up 3scale Operator resources, and databases such as MySQL and Redis. Once the data has been restored, you can scale up the 3scale Operator and deployment. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
You can restore the 3scale by restoring the backed up 3scale Operator resources. 

You can also restore databases such as MySQL and Redis. 

Once the data has been restored, you can scale up the 3scale Operator and deployment. 
```
created_at: 2025-03-04T22:07:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,17 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: i wonder whether you should add an introduction, then putting these use cases underneath that introduction. Even if it is just a short sentence, followed by a list of the restore use cases
created_at: 2025-03-04T22:12:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,9 +1,13 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
 With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: dfennessy
body: As far as I am aware, there isn't an acronym like APIM used for Red Hat 3scale API Management. You can remove it. After the first usage of Red Hat 3scale API Management, you can use 3scale API Management thereafter.

For this, we can think in terms of our user story structured like the following:

As a [user role], I want to [perform an action], so that [benefit or goal].

For OADP, we might write the user story something like: 

As an OpenShift administrator, I want to use OpenShift API for Data Protection (OADP) to back up and restore applications, cluster resources, persistent volumes, and internal images, so that I can ensure comprehensive disaster recovery and protect both containerized applications and virtual machines (VMs) on OpenShift.

Based on the user story, we might have an intro similar to this:
Back up and restore for 3scale API Management is critical for ensuring data protection and disaster recovery. With OpenShift API for Data Protection (OADP), you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. You can configure OADP to create backups of 3scale components and restore them when needed, ensuring minimal downtime and data integrity.

My knowledge of OADP is minimal, so this is just an example that hopefully helps.
created_at: 2025-03-05T10:54:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,9 +1,13 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
 With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: Thanks, @dfennessy for reviewing and adding your suggestions.
created_at: 2025-03-10T18:35:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,24 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: @anarnold97, could you please help me by sharing a few examples for this? 
created_at: 2025-03-10T18:36:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,24 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: @stillalearner - please can i ask if you have any backup test cases you could share with Apurva?
Thanks
created_at: 2025-03-10T19:06:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,13 +1,22 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. You can configure OADP to perform the following operations with 3scale: 
+
+* create backup of 3scale components by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[Backing up 3scale].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
* Create backup of 3scale components by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[Backing up 3scale].
```
created_at: 2025-03-10T19:08:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,13 +1,22 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. You can configure OADP to perform the following operations with 3scale: 
+
+* create backup of 3scale components by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[Backing up 3scale].
+* restore the components to scale up the 3scale Operator and deployment by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc#restoring-3scale-by-using-oadp[Restoring 3scale].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
* Restore the components to scale up the 3scale Operator and deployment by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc#restoring-3scale-by-using-oadp[Restoring 3scale].
```
created_at: 2025-03-10T19:09:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,13 +1,22 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
```

Maintain the singular/plural agreement
created_at: 2025-03-10T19:09:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ```suggestion
You can back up 3scale by backing up 3scale Operator. You can also back up databases such as MySQL and Redis.
```
Verb is back up
created_at: 2025-03-10T19:14:59Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: Please can you have a look at this module?

Is it meant to look like this

![image](https://github.com/user-attachments/assets/e5b15f64-3def-44ff-b71b-2524235017a5)

created_at: 2025-03-10T19:23:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -40,7 +40,7 @@ spec:
 $ oc create -f ts_pvc.yml 
 ----
 
-. Attach the PVC to the system database pod by editing the system database deployment to use the `mysql` dump:
+. Attach the PVC to the system database pod by editing the `system-mysql` deployment to use the `mysql` dump:
path: modules/backing-up-the-mysql-database.adoc
user: login: anarnold97
body: The formatting in this file is not correct:

![image](https://github.com/user-attachments/assets/83e781f7-5690-4219-b86a-fa1ea499be39)

I think it should be MySQL not mysql

![image](https://github.com/user-attachments/assets/6d2cead0-393f-4972-bc3b-dbdfd501a13d)


created_at: 2025-03-10T19:30:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: In this module why is a **Use case** listed as **Next steps**

Do you think it looks a bit weird?
created_at: 2025-03-10T19:38:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,18 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore the 3scale by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
+Once the data has been restored, you can scale up the 3scale Operator and deployment. 
+
+include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]
+
+include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: ![image](https://github.com/user-attachments/assets/0324e494-cc48-4464-a7e0-fd4821cf8d95)
 Same here
created_at: 2025-03-10T19:39:59Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: Yes, it was suggested in the OCP review for using xref as adding it in the module isn't supported, and the same additional resources related information was added in the assembly. 
Let me know if you have any other suggestion for this approach. 
created_at: 2025-03-10T19:43:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: As per the user story template that we had created for OADP, I've added the module under next steps to explain the sequence to the users. 
Let me know if you've any other suggestion for the "Next steps" section, or if it is not required. 
created_at: 2025-03-10T19:46:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: I would remove - `For more information ... " . Without an xref, it just looks weird like it should be a link but is mis-formatted
WDYT

If it is so important, add an additional resources section at the bottom of the document
created_at: 2025-03-10T19:48:30Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,18 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore the 3scale by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
+Once the data has been restored, you can scale up the 3scale Operator and deployment. 
+
+include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]
+
+include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: anarnold97
body: Is the next step after restoring the MySQL DB,  backing up Redis DB? or are they independent use case elements?
created_at: 2025-03-10T19:49:59Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,18 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore the 3scale by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
+Once the data has been restored, you can scale up the 3scale Operator and deployment. 
+
+include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]
+
+include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: After [restoring mysql](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp), the next step is restoring the backend-redis database followed by scaling 3scale operator.
For [backing up 3scale](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp), the sequence is - backing up 3scale operator followed by backing up mysql database and then redis database.
created_at: 2025-03-10T20:02:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -40,7 +40,7 @@ spec:
 $ oc create -f ts_pvc.yml 
 ----
 
-. Attach the PVC to the system database pod by editing the system database deployment to use the `mysql` dump:
+. Attach the PVC to the system database pod by editing the `system-mysql` deployment to use the `mysql` dump:
path: modules/backing-up-the-mysql-database.adoc
user: login: apurvabhide17
body: I've replaced `mysql` with MySQL in all the modules.
created_at: 2025-03-10T20:08:17Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: I don't mind removing that line and having the existing xref added to additional resources section in the assembly. 
created_at: 2025-03-10T20:18:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: anarnold97
body: Please remove *Next steps*. 
You are talking about the next use cases and not logical next steps. 
created_at: 2025-03-10T22:50:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: done
created_at: 2025-03-13T18:51:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator. You can also backup and databases such as MySQL and Redis.
+
+
+include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
+[role="_additional-resources"]
+.Additional resources
+* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
+
+include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: done
created_at: 2025-03-13T18:51:10Z
author_association: CONTRIBUTOR
diff_hunk: @@ -17,27 +26,5 @@ Additionally, ensure that you are restoring 3scale on the same cluster where it
 
 .Prerequisites
 
-* You installed and configured Red Hat 3scale. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management[Red Hat 3scale API Management].
-
-include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
-
-include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
-
-include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
-
-include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+1]
-
-include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]
-
-include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]
-
-include::modules/restoring-the-backend-redis-database.adoc[leveloffset=+1]
+* You installed and configured Red Hat 3scale. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red Hat 3scale API Management].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: shdeshpa07
body: The prerequisites section here looks odd. Since this is an assembly, I would suggest moving the pre-req to the procedure module (maybe each of the procedure modules). Here, it looks incomplete.
created_at: 2025-03-18T04:53:57Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,13 +1,22 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. You can configure OADP to perform the following operations with 3scale: 
+
+* Create backup of 3scale components by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[Backing up 3scale].
+* Restore the components to scale up the 3scale Operator and deployment by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc#restoring-3scale-by-using-oadp[Restoring 3scale].
 
 [NOTE]
 ====
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: shdeshpa07
body: I don't understand the `non-service affecting approach` part of the note. We will need to explain this in simpler terms, probably.
created_at: 2025-03-18T04:55:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: shdeshpa07
body: ```suggestion
You can back up 3scale components by backing up 3scale Operator, and databases such as MySQL and Redis.
```
created_at: 2025-03-18T04:56:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale by backing up 3scale Operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: shdeshpa07
body: I suggest being consistent with the usage of the term `3scale components` or `3scale Operator`. For example, in the intro assembly, the term `3scale components` has been used. But, in the module `Backing up 3scale by using OADP`, the term `3scale Operator` is being used in the intro. Elsewhere, I see just `3scale` is being used. Please use either one of the terms. I would suggest using `3scale Operator` rather than `components`.
created_at: 2025-03-18T05:01:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="creating-the-data-protection-application_{context}"]
 = Creating the Data Protection Application
 
-You can create a Data Protection Application (DPA) custom resource (CR) for 3scale. For more information on DPA, see "Installing the Data Protection Application".
+You can create a Data Protection Application (DPA) custom resource (CR) for 3scale.
 
 .Procedure
 
path: modules/creating-the-data-protection-application.adoc
user: login: shdeshpa07
body: ```suggestion
.Example `dpa.yaml` file
+
[source,yaml]
----
apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  name: dpa-sample
  namespace: openshift-adp 
spec:
  configuration:
    velero:
      defaultPlugins:
        - openshift 
        - aws
        - csi
      resourceTimeout: 10m 
    nodeAgent: 
	
```
created_at: 2025-03-18T05:13:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="creating-the-data-protection-application_{context}"]
 = Creating the Data Protection Application
 
-You can create a Data Protection Application (DPA) custom resource (CR) for 3scale. For more information on DPA, see "Installing the Data Protection Application".
+You can create a Data Protection Application (DPA) custom resource (CR) for 3scale.
 
 .Procedure
 
path: modules/creating-the-data-protection-application.adoc
user: login: shdeshpa07
body: The name of the CR must use a hypen rather than an underscore. Underscore is for variables.
created_at: 2025-03-18T05:14:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="backing-up-the-3scale-operator_{context}"]
 = Backing up the 3scale Operator
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the Operator resources, and Secret and APIManager custom resources (CR).
path: modules/backing-up-the-3scale-operator.adoc
user: login: shdeshpa07
body: ```suggestion
You can back up the Operator resources, and `Secret` and APIManager custom resources (CR).
```
created_at: 2025-03-18T05:17:17Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="backing-up-the-3scale-operator_{context}"]
 = Backing up the 3scale Operator
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the Operator resources, and Secret and APIManager custom resources (CR).
path: modules/backing-up-the-3scale-operator.adoc
user: login: shdeshpa07
body: So there will be lots of f/b when this goes for OCP review about usage of back ticks for CRs. For example, here if you capitalize the S in secret, it must be annotated in back ticks to indicate that it is a CR, like this, `Secret`. Otherwise, use small case if you are using the term in a generic way. And use the term in a similar way throughout the doc set. Either way, I anticipate this getting flagged.
created_at: 2025-03-18T05:27:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="backing-up-the-3scale-operator_{context}"]
 = Backing up the 3scale Operator
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the Operator resources, and Secret and APIManager custom resources (CR).
path: modules/backing-up-the-3scale-operator.adoc
user: login: shdeshpa07
body: In step 3, `. Back up the Secret CR by creating a YAML file with the following configuration:`  , use back ticks for secret as it is being referenced as a CR.
created_at: 2025-03-18T05:28:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="backing-up-the-3scale-operator_{context}"]
 = Backing up the 3scale Operator
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the Operator resources, and Secret and APIManager custom resources (CR).
path: modules/backing-up-the-3scale-operator.adoc
user: login: shdeshpa07
body: I don't know if APIManagers is a CR. You will need to follow the same nomenclature (back ticks), if it is a CR.
created_at: 2025-03-18T05:29:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can back up the Redis database by adding the required annotations and by lis
 .Prerequisites
 
path: modules/backing-up-the-backend-redis-database.adoc
user: login: shdeshpa07
body: ```suggestion
You can back up the Redis database by adding the required annotations and by listing the resources to back up using the `includedResources` parameter.
```
created_at: 2025-03-18T05:36:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can back up the Redis database by adding the required annotations and by lis
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up the mysql database.
+* You backed up the MySQL database.
 * The Redis queues have been drained before performing the backup.
 
 
path: modules/backing-up-the-backend-redis-database.adoc
user: login: shdeshpa07
body: . Add the following annotations:
+
[source,yaml]
----
annotations:
post.hook.backup.velero.io/command: >-
         ["/bin/bash", "-c", "redis-cli CONFIG SET auto-aof-rewrite-percentage
         100"]
       pre.hook.backup.velero.io/command: >-
         ["/bin/bash", "-c", "redis-cli CONFIG SET auto-aof-rewrite-percentage
         0"]



This YAML is not fully formed. This needs the resource definition, like the `apiversion`, `kind`, `metadata`, etc. Otherwise, user will not know where to add the annotations.
created_at: 2025-03-18T05:39:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -84,8 +84,4 @@ $ oc get backups.velero.io redis-backup -o yaml
 [source,terminal]
 ----
 $ oc get backups.velero.io
-----
-
-.Next steps
-
-* Restore the Secrets and APIManager CRs.
\ No newline at end of file
+----
path: modules/backing-up-the-backend-redis-database.adoc
user: login: shdeshpa07
body: Suggest adding an example output.
created_at: 2025-03-18T05:41:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,19 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore the 3scale by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: shdeshpa07
body: ```suggestion
You can restore 3scale by restoring the backed up the 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
```
created_at: 2025-03-18T05:42:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can restore the Secrets and APIManager by using the following procedure.
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up MySQL and Redis databases.
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: shdeshpa07
body: ```suggestion
* You backed up the MySQL and Redis databases.
```
created_at: 2025-03-18T05:45:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can restore the Secrets and APIManager by using the following procedure.
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up MySQL and Redis databases.
 * You are restoring the database on the same cluster, where it was backed up. 
 +
 If it is on a different cluster, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster as it was on the source cluster.
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: shdeshpa07
body: ```suggestion
If you are restoring on a different cluster, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster. Ensure the {oadp-short} configuration is same as it was on the source cluster.
```
created_at: 2025-03-18T05:47:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can restore the Secrets and APIManager by using the following procedure.
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up MySQL and Redis databases.
 * You are restoring the database on the same cluster, where it was backed up. 
 +
 If it is on a different cluster, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster as it was on the source cluster.
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: shdeshpa07
body: In the procedure, on step 6, add a call out to indicate the user that they need to use the backup specific for the secrets. It is an important point to call out. 

`
 backupName: operator-resources-secrets
`
created_at: 2025-03-18T05:53:30Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can restore the Secrets and APIManager by using the following procedure.
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up MySQL and Redis databases.
 * You are restoring the database on the same cluster, where it was backed up. 
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: shdeshpa07
body: In the procedure, on step 8, add a call out to indicate the user that they need to use the backup specific for the APIManager. It is an important point to call out.

`backupName: operator-resources-apim`
created_at: 2025-03-18T05:55:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -167,8 +167,4 @@ $ oc create -f restore-apimanager.yaml
 [source,terminal]
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
-----
-
-.Next steps
-
-* Restore the `mysql` database.
\ No newline at end of file
+----
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: shdeshpa07
body: Please add example output steps for verification at each restore.
created_at: 2025-03-18T05:56:10Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,13 +3,13 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 [id="restoring-the-mysql-database_{context}"]
-= Restoring the mysql database
+= Restoring the MySQL database
 
-Restoring the `mysql` database re-creates the following resources:
+Restoring the MySQL database re-creates the following resources:
 
 * The `Pod`, `ReplicationController`, and `Deployment` objects.
 * The additional persistent volumes (PVs) and associated persistent volume claims (PVCs). 
-* The `mysql` dump, which the `example-claim` PVC contains.
+* The MySQL dump, which the `example-claim` PVC contains.
path: modules/restoring-the-mysql-database.adoc
user: login: shdeshpa07
body: ```suggestion
* The MySQL dump, that the `example-claim` PVC contains.
```
created_at: 2025-03-18T05:57:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -91,7 +91,7 @@ Warning: apps.openshift.io/v1 deployment is deprecated in v4.14+, unavailable in
 deployment.apps.openshift.io "system-mysql" deleted
 ----
 
-. Create the following YAML file to restore the `mysql` database:
+. Create the following YAML file to restore the MySQL database:
path: modules/restoring-the-mysql-database.adoc
user: login: shdeshpa07
body: Call out the `backupName: mysql-backup` , as the user needs to know they are restoring the MySQL backup.
created_at: 2025-03-18T05:59:32Z
author_association: CONTRIBUTOR
diff_hunk: @@ -10,7 +10,7 @@ You can restore the back-end Redis database by deleting the deployment and speci
 .Prerequisites
path: modules/restoring-the-backend-redis-database.adoc
user: login: shdeshpa07
body: ```suggestion
You can restore the back-end Redis database by deleting the deployment and specifying the resources you do not want to restore.
```
created_at: 2025-03-18T06:00:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -10,7 +10,7 @@ You can restore the back-end Redis database by deleting the deployment and speci
 .Prerequisites
 
 * You restored the Secret and APIManager custom resources.
-* You restored the `mysql` database.
+* You restored the MySQL database.
 
 .Procedure
path: modules/restoring-the-backend-redis-database.adoc
user: login: shdeshpa07
body: Call out the `backupName: redis-backup` at step 2 of the procedure. User needs to know that they are restoring the redis backup.
created_at: 2025-03-18T06:02:18Z
author_association: CONTRIBUTOR
diff_hunk: @@ -22,11 +22,11 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
 +
 [source,terminal]
 ----
-$ oc get deployment -n threescale
+$ oc get pods -n threescale
 ----
 
 . Scale up the deployments by executing the following script:
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: shdeshpa07
body: ```suggestion
. Scale up the deployments by running the following script:
```
created_at: 2025-03-18T06:04:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -22,11 +22,11 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
 +
 [source,terminal]
 ----
-$ oc get deployment -n threescale
+$ oc get pods -n threescale
 ----
 
 . Scale up the deployments by executing the following script:
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: shdeshpa07
body: Avoid the word `execute`.
created_at: 2025-03-18T06:04:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -22,11 +22,11 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
 +
 [source,terminal]
 ----
-$ oc get deployment -n threescale
+$ oc get pods -n threescale
 ----
 
 . Scale up the deployments by executing the following script:
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: shdeshpa07
body: In the last step, step 5, rewrite the sentence:

. Use the URL from this output to log in to the 3scale Operator as an administrator. You can verify that the data, when you took the backup, is available.
created_at: 2025-03-18T06:07:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,13 +3,13 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 [id="restoring-the-mysql-database_{context}"]
-= Restoring the mysql database
+= Restoring the MySQL database
 
-Restoring the `mysql` database re-creates the following resources:
+Restoring the MySQL database re-creates the following resources:
 
 * The `Pod`, `ReplicationController`, and `Deployment` objects.
 * The additional persistent volumes (PVs) and associated persistent volume claims (PVCs). 
-* The `mysql` dump, which the `example-claim` PVC contains.
+* The MySQL dump, which the `example-claim` PVC contains.
path: modules/restoring-the-mysql-database.adoc
user: login: apurvabhide17
body: As per IBM SSG - Use "which", preceded by a comma, to introduce a nonrestrictive clause. Use "that", without a comma, to introduce a
restrictive clause.
created_at: 2025-03-21T18:16:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -10,7 +10,7 @@ You can restore the back-end Redis database by deleting the deployment and speci
 .Prerequisites
path: modules/restoring-the-backend-redis-database.adoc
user: login: apurvabhide17
body: There is a step added in the procedure explaining how to delete it, and is not a prerequisite. 
created_at: 2025-03-21T18:17:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can back up the Redis database by adding the required annotations and by lis
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up the mysql database.
+* You backed up the MySQL database.
 * The Redis queues have been drained before performing the backup.
 
 
path: modules/backing-up-the-backend-redis-database.adoc
user: login: apurvabhide17
body: I'll check it again with Sachin but the previous command opens the backend-redis deployment, where this annotation must be added.
created_at: 2025-03-21T18:22:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can back up the Redis database by adding the required annotations and by lis
 .Prerequisites
 
path: modules/backing-up-the-backend-redis-database.adoc
user: login: apurvabhide17
body: This is not a prerequisite.
created_at: 2025-03-21T18:24:20Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="backing-up-the-3scale-operator_{context}"]
 = Backing up the 3scale Operator
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the Operator resources, and Secret and APIManager custom resources (CR).
path: modules/backing-up-the-3scale-operator.adoc
user: login: apurvabhide17
body: I've added it for Secret but not for APIManager. In 3scale docs, they are not using back ticks for APIManager - https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management/index, following the same style.
created_at: 2025-03-21T18:54:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -17,27 +26,5 @@ Additionally, ensure that you are restoring 3scale on the same cluster where it
 
 .Prerequisites
 
-* You installed and configured Red Hat 3scale. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management[Red Hat 3scale API Management].
-
-include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
-
-include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
-
-include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
-
-include::modules/backing-up-the-backend-redis-database.adoc[leveloffset=+1]
-
-include::modules/restoring-the-secrets-and-apimanager.adoc[leveloffset=+1]
-
-include::modules/restoring-the-mysql-database.adoc[leveloffset=+1]
-
-include::modules/restoring-the-backend-redis-database.adoc[leveloffset=+1]
+* You installed and configured Red Hat 3scale. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red Hat 3scale API Management].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: Added it to the backup and restore assembly instead of adding it here. 
created_at: 2025-03-21T18:59:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -91,7 +91,7 @@ Warning: apps.openshift.io/v1 deployment is deprecated in v4.14+, unavailable in
 deployment.apps.openshift.io "system-mysql" deleted
 ----
 
-. Create the following YAML file to restore the `mysql` database:
+. Create the following YAML file to restore the MySQL database:
path: modules/restoring-the-mysql-database.adoc
user: login: apurvabhide17
body: Added about it to both backup and restore file.
created_at: 2025-03-24T18:17:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -10,7 +10,7 @@ You can restore the back-end Redis database by deleting the deployment and speci
 .Prerequisites
 
 * You restored the Secret and APIManager custom resources.
-* You restored the `mysql` database.
+* You restored the MySQL database.
 
 .Procedure
path: modules/restoring-the-backend-redis-database.adoc
user: login: apurvabhide17
body: Added about it to both backup and restore file.
created_at: 2025-03-24T18:18:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can restore the Secrets and APIManager by using the following procedure.
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up MySQL and Redis databases.
 * You are restoring the database on the same cluster, where it was backed up. 
 +
 If it is on a different cluster, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster as it was on the source cluster.
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: apurvabhide17
body: Added about it to both backup and restore file.
created_at: 2025-03-24T18:19:57Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can restore the Secrets and APIManager by using the following procedure.
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up MySQL and Redis databases.
 * You are restoring the database on the same cluster, where it was backed up. 
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: apurvabhide17
body: Added about it to both backup and restore file.
created_at: 2025-03-24T18:20:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -167,8 +167,4 @@ $ oc create -f restore-apimanager.yaml
 [source,terminal]
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
-----
-
-.Next steps
-
-* Restore the `mysql` database.
\ No newline at end of file
+----
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: apurvabhide17
body: done
created_at: 2025-03-24T18:20:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -21,15 +21,28 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
++
+.Example output
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
 +
 [source,terminal]
 ----
-$ oc get deployment -n threescale
+$ oc get pods -n threescale
+----
++
+.Example output
+[source,terminal]
+----
+NAME									                    READY        STATUS	  RESTARTS	 AGE
+threescale-operator-controller-manager-v2-79546bd8c-b4qbh	1/1	         Running  0          2m5s
 ----
 
-. Scale up the deployments by executing the following script:
+. Scale up the deployments by running the following script:
 +
 [source,terminal]
 ----
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: stillalearner
body: where are the contents of this script?
created_at: 2025-04-03T07:00:27Z
author_association: NONE
diff_hunk: @@ -21,15 +21,28 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
++
+.Example output
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
 +
 [source,terminal]
 ----
-$ oc get deployment -n threescale
+$ oc get pods -n threescale
+----
++
+.Example output
+[source,terminal]
+----
+NAME									                    READY        STATUS	  RESTARTS	 AGE
+threescale-operator-controller-manager-v2-79546bd8c-b4qbh	1/1	         Running  0          2m5s
 ----
 
-. Scale up the deployments by executing the following script:
+. Scale up the deployments by running the following script:
 +
 [source,terminal]
 ----
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: apurvabhide17
body: @stillalearner, could you share the content of this script? 
Or should it be same like "scaledowndeployment.sh"?
created_at: 2025-04-03T07:13:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -21,15 +21,28 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
++
+.Example output
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
 +
 [source,terminal]
 ----
-$ oc get deployment -n threescale
+$ oc get pods -n threescale
+----
++
+.Example output
+[source,terminal]
+----
+NAME									                    READY        STATUS	  RESTARTS	 AGE
+threescale-operator-controller-manager-v2-79546bd8c-b4qbh	1/1	         Running  0          2m5s
 ----
 
-. Scale up the deployments by executing the following script:
+. Scale up the deployments by running the following script:
 +
 [source,terminal]
 ----
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: apurvabhide17
body: done, I've added it.
created_at: 2025-04-03T13:34:10Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can back up the Redis database by adding the required annotations and by lis
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up the mysql database.
+* You backed up the MySQL database.
 * The Redis queues have been drained before performing the backup.
 
 
path: modules/backing-up-the-backend-redis-database.adoc
user: login: apurvabhide17
body: No need to add the resources because these steps will only edit the existing resources to add annotation.
created_at: 2025-04-14T18:37:18Z
author_association: CONTRIBUTOR
diff_hunk: @@ -69,23 +67,40 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring the Redis database.
 
 . Back up the Redis database by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io redis-backup -o yaml
+$ oc create -f redis-backup.yaml
 ----
++
+.Example output:
++
+[source,terminal]
+----
+backup.velero.io/redis-backup created
+----
+
 
 .Verification
 
-* Verify that the Redis backup is completed by running the following command:: 
+* Verify that the Redis backup is completed by running the following command:
 +
 [source,terminal]
 ----
 $ oc get backups.velero.io
path: modules/backing-up-the-backend-redis-database.adoc
user: login: stillalearner
body: oc get backups.velero.io redis-backup
created_at: 2025-04-16T07:13:08Z
author_association: NONE
diff_hunk: @@ -69,23 +67,40 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring the Redis database.
 
 . Back up the Redis database by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io redis-backup -o yaml
+$ oc create -f redis-backup.yaml
 ----
++
+.Example output:
++
+[source,terminal]
+----
+backup.velero.io/redis-backup created
+----
+
 
 .Verification
 
-* Verify that the Redis backup is completed by running the following command:: 
+* Verify that the Redis backup is completed by running the following command:
 +
 [source,terminal]
 ----
 $ oc get backups.velero.io
 ----
-
-.Next steps
-
-* Restore the Secrets and APIManager CRs.
\ No newline at end of file
++
+.Example output:
path: modules/backing-up-the-backend-redis-database.adoc
user: login: stillalearner
body: and this output needs to be changed according to command.
created_at: 2025-04-16T07:13:46Z
author_association: NONE
diff_hunk: @@ -6,15 +6,15 @@
 [id="restoring-the-secrets-and-apimanager_{context}"]
 = Restoring the secrets and APIManager
path: modules/restoring-the-secrets-and-apimanager.adoc
user: login: stillalearner
body: Restoring the 3scale operator resources, secrets and APIManager
created_at: 2025-04-16T07:15:54Z
author_association: NONE
diff_hunk: @@ -69,23 +67,36 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring the Redis database.
 
 . Back up the Redis database by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io redis-backup -o yaml
+$ oc create -f redis-backup.yaml
 ----
++
+.Example output:
++
+[source,terminal]
+----
+backup.velero.io/redis-backup created
+----
+
 
 .Verification
 
-* Verify that the Redis backup is completed by running the following command:: 
+* Verify that the Redis backup is completed by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io
+$ oc get backups.velero.io redis-backup
path: modules/backing-up-the-backend-redis-database.adoc
user: login: stillalearner
body: you have to add  " -o yaml " as well here to check backup status
created_at: 2025-04-17T13:27:44Z
author_association: NONE
diff_hunk: @@ -69,23 +67,36 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring the Redis database.
 
 . Back up the Redis database by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io redis-backup -o yaml
+$ oc create -f redis-backup.yaml
 ----
++
+.Example output:
++
+[source,terminal]
+----
+backup.velero.io/redis-backup created
+----
+
 
 .Verification
 
-* Verify that the Redis backup is completed by running the following command:: 
+* Verify that the Redis backup is completed by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io
+$ oc get backups.velero.io redis-backup
 ----
-
-.Next steps
-
-* Restore the Secrets and APIManager CRs.
\ No newline at end of file
++
+.Example output:
++
+[source,terminal]
path: modules/backing-up-the-backend-redis-database.adoc
user: login: stillalearner
body: please paste the output after running -o yaml
like this
----

status:
  completionTimestamp: "2025-04-17T13:25:19Z"
  errors: 1
  expiration: "2025-05-17T13:25:16Z"
  formatVersion: 1.1.0
  hookStatus: {}
  phase: Completed
  progress: {}
  startTimestamp: "2025-04-17T13:25:16Z"
  version: 1
created_at: 2025-04-17T13:28:28Z
author_association: NONE
diff_hunk: @@ -111,19 +111,27 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> A directory where the data is backed up.
-<2> Resources to back up.
+<1> Use this as the `backupName` value while restoring the MySQL database.
+<2> A directory where the data is backed up.
+<3> Resources to back up.
 
-. Back up the `mysql` database by running the following command:
+. Back up the MySQL database by running the following command:
 +
 [source,terminal]
 ----
 $ oc create -f mysql.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+backup.velero.io/mysql-backup created
+----
 
 .Verification
 
-* Verify that the `mysql` backup is completed by running the following command:
+* Verify that the MySQL backup is completed by running the following command:
 +
 [source,terminal]
 ----
path: modules/backing-up-the-mysql-database.adoc
user: login: stillalearner
body: same here -o yaml

and same output
created_at: 2025-04-17T13:29:18Z
author_association: NONE
diff_hunk: @@ -69,23 +67,36 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring the Redis database.
 
 . Back up the Redis database by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io redis-backup -o yaml
+$ oc create -f redis-backup.yaml
 ----
++
+.Example output:
++
+[source,terminal]
+----
+backup.velero.io/redis-backup created
+----
+
 
 .Verification
 
-* Verify that the Redis backup is completed by running the following command:: 
+* Verify that the Redis backup is completed by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io
+$ oc get backups.velero.io redis-backup
path: modules/backing-up-the-backend-redis-database.adoc
user: login: apurvabhide17
body: done
created_at: 2025-04-21T06:17:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -69,23 +67,36 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring the Redis database.
 
 . Back up the Redis database by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io redis-backup -o yaml
+$ oc create -f redis-backup.yaml
 ----
++
+.Example output:
++
+[source,terminal]
+----
+backup.velero.io/redis-backup created
+----
+
 
 .Verification
 
-* Verify that the Redis backup is completed by running the following command:: 
+* Verify that the Redis backup is completed by running the following command:
 +
 [source,terminal]
 ----
-$ oc get backups.velero.io
+$ oc get backups.velero.io redis-backup
 ----
-
-.Next steps
-
-* Restore the Secrets and APIManager CRs.
\ No newline at end of file
++
+.Example output:
++
+[source,terminal]
path: modules/backing-up-the-backend-redis-database.adoc
user: login: apurvabhide17
body: done, I've updated the output
created_at: 2025-04-21T06:18:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -111,19 +111,27 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> A directory where the data is backed up.
-<2> Resources to back up.
+<1> Use this as the `backupName` value while restoring the MySQL database.
+<2> A directory where the data is backed up.
+<3> Resources to back up.
 
-. Back up the `mysql` database by running the following command:
+. Back up the MySQL database by running the following command:
 +
 [source,terminal]
 ----
 $ oc create -f mysql.yaml
 ----
++
+.Example output
++
+[source,terminal]
+----
+backup.velero.io/mysql-backup created
+----
 
 .Verification
 
-* Verify that the `mysql` backup is completed by running the following command:
+* Verify that the MySQL backup is completed by running the following command:
 +
 [source,terminal]
 ----
path: modules/backing-up-the-mysql-database.adoc
user: login: apurvabhide17
body: done, I've updated the output
created_at: 2025-04-21T06:18:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,28 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale components by backing up 3scale Operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
You can back up Red{nbsp}Hat 3scale components by backing up the Red{nbsp}Hat build of 3scale Operator and your databases, for example, MySQL and Redis.
```
It seems like 3scale is something that is a "_Red Hat build of_..." component? In that case, I would make sure you are consistent in calling 3scale something like "Red Hat build of 3scale". 

Probably want to talk to marketing about how to talk about 3scale in prod docs. Their guidance on the [spreadsheet](https://docs.google.com/spreadsheets/d/1DLS_lS3VKidgZIvcLmLp9BoiqptkvqHWfe1D5FD2kfk/edit?gid=1375785039#gid=1375785039.) is contradictory. You might just use something like "Red{nbsp}Hat build of 3scale" and make an attribute for it in the meantime. When I search for "Janus 3scale" I get their Deprecated page, which isn't great, https://janus-idp.io/plugins/3scale/.
created_at: 2025-04-22T11:12:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,28 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-by-using-oadp"]
+= Backing up 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-by-using-oadp
+
+toc::[]
+
+You can back up 3scale components by backing up 3scale Operator, and databases such as MySQL and Redis.
+
+.Prerequisites
+
+* You installed and configured Red Hat 3scale. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red Hat 3scale API Management].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You installed and configured the Red{nbsp}Hat build of 3scale Operator. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red Hat 3scale API Management].
```
See https://redhat-documentation.github.io/supplementary-style-guide/#non-breaking-spaces

And these links are broken; the attribute is not working.
created_at: 2025-04-22T11:20:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: Links should point to docs.redhat.com, not the customer portal. docs.redhat is open, and the Portal is behind a paywall. Better to use the URL you want from https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15
created_at: 2025-04-22T11:26:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
With Red{nbsp}Hat 3scale API management, you can manage your APIs for internal or external users. 
```
Not a product name, lowercase the "M". Is this a component of the Operator? Or are we using this synonymously with the Operator, e.g., APIManager? Terminology is inconsistent throughout this PR. It's confusing.
created_at: 2025-04-22T11:31:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
You can deploy Red{nbsp}Hat 3scale API management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
```
created_at: 2025-04-22T11:32:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
With {oadp-first}, you can safeguard Red{nbsp}Hat 3scale deployments by backing up application resources, persistent volumes, and configurations. 
```
I would keep a RH with mentions of 3scale concepts since it is different from the upstream deprecated version.
created_at: 2025-04-22T11:34:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. 
 
 [NOTE]
 ====
-In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator.
-Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
+In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
You can use the {oadp-first} Operator to back up your Red{nbsp}Hat 3scale on-cluster storage databases without affecting your running services.
```
I think this is what you mean. Much simpler. And the examples aren't within this assembly anymore, so the "this example" language can just be removed.
created_at: 2025-04-22T11:35:51Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. 
 
 [NOTE]
 ====
-In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator.
-Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
+In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator. 
+With this approach, the service is not affected during the backup. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
```
created_at: 2025-04-22T11:56:30Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. 
 
 [NOTE]
 ====
-In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator.
-Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
+In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator. 
+With this approach, the service is not affected during the backup. 
+Therefore, it is recommended to use the databse tooling while creating a backup without affectting the service.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
```
created_at: 2025-04-22T11:56:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. 
 
 [NOTE]
 ====
-In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator.
-Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
+In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator. 
+With this approach, the service is not affected during the backup. 
+Therefore, it is recommended to use the databse tooling while creating a backup without affectting the service.
 ====
 
-.Prerequisites
-
-* You installed and configured Red Hat 3scale. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management[Red Hat 3scale API Management].
-
-include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
-
-include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+You can configure OADP to perform the following operations with 3scale: 
 
-include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
+* Create a backup of 3scale components by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[Backing up 3scale].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
* Create a backup of Red{nbsp}Hat 3scale components by following the steps in xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[Backing up 3scale].
```
"in" is a more accurate/common preposition for this type of reference
created_at: 2025-04-22T11:57:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. 
 
 [NOTE]
 ====
-In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator.
-Additionally, ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
+In this example, the non-service affecting approach is used to back up and restore 3scale on-cluster storage by using the {oadp-first} Operator. 
+With this approach, the service is not affected during the backup. 
+Therefore, it is recommended to use the databse tooling while creating a backup without affectting the service.
 ====
 
-.Prerequisites
-
-* You installed and configured Red Hat 3scale. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management/2.15/html/installing_red_hat_3scale_api_management[Red Hat 3scale API Management].
-
-include::modules/creating-the-data-protection-application.adoc[leveloffset=+1]
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#oadp-installing-dpa_installing-oadp-aws[Installing the Data Protection Application]
-
-include::modules/backing-up-the-3scale-operator.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-* xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc#oadp-creating-backup-cr-doc[Creating a Backup CR]
+You can configure OADP to perform the following operations with 3scale: 
 
-include::modules/backing-up-the-mysql-database.adoc[leveloffset=+1]
+* Create a backup of 3scale components by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp.adoc#backing-up-3scale-by-using-oadp[Backing up 3scale].
+* Restore the components to scale up the 3scale Operator and deployment by following the steps from xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc#restoring-3scale-by-using-oadp[Restoring 3scale].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
* Restore the components to scale up the Red{nbsp}Hat build of 3scale Operator and deployment by following the steps in xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc#restoring-3scale-by-using-oadp[Restoring 3scale].
```
created_at: 2025-04-22T11:57:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
= Restoring the Red{nbsp}Hat build of 3scale Operator by using OADP
```
Are we restoring the Operator, or just certain components of it?
created_at: 2025-04-22T12:00:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore 3scale components by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
You can restore Red{nbsp}Hat 3scale components by restoring backed up Red{nbsp}Hat build of 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
```
created_at: 2025-04-22T12:02:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore 3scale components by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
+
+Once the data has been restored, you can scale up the 3scale Operator and deployment. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
After the data has been restored, you can scale up the Red{nbsp}Hat build of 3scale Operator and deployment. 
```
created_at: 2025-04-22T12:02:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore 3scale components by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
+
+Once the data has been restored, you can scale up the 3scale Operator and deployment. 
+
+.Prerequisites
+
+* You installed and configured Red Hat 3scale. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red Hat 3scale API Management].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You installed and configured the Red{nbsp}Hat build of 3scale Operator. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red{nbsp}Hat 3scale API Management].
```
created_at: 2025-04-22T13:00:30Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore 3scale components by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
+
+Once the data has been restored, you can scale up the 3scale Operator and deployment. 
+
+.Prerequisites
+
+* You installed and configured Red Hat 3scale. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red Hat 3scale API Management].
+
+* You backed up the 3scale Operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You backed up the Red{nbsp}Hat build of 3scale Operator, and your databases, for example, MySQL and Redis.
```
created_at: 2025-04-22T13:01:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-by-using-oadp"]
+= Restoring 3scale by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-by-using-oadp
+
+toc::[]
+
+You can restore 3scale components by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
+
+Once the data has been restored, you can scale up the 3scale Operator and deployment. 
+
+.Prerequisites
+
+* You installed and configured Red Hat 3scale. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:{Link3scaleInstalling3scale}[Red Hat 3scale API Management].
+
+* You backed up the 3scale Operator, and databases such as MySQL and Redis.
+
+* Ensure that you are restoring 3scale on the same cluster where it was backed up from. If you want to restore 3scale on a different cluster, ensure that both clusters are using the same custom domain.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp.adoc
user: login: ShaunaDiaz
body: ```suggestion
* In most cases, you ensured that you are restoring Red{nbsp}Hat build of 3scale Operator to the same cluster where it was backed up from. 

* If you want to restore Red{nbsp}Hat build of 3scale Operator to a different cluster, ensure that the original backed-up cluster and the cluster you want to restore the Operator on are using the same custom domain.
```
How can you restore something to another cluster that wasn't backed up there? I think we need some more detail/mention of this use case. I would also make this a separate bullet. Is this typical, or an edge case?
created_at: 2025-04-22T13:06:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2,18 +2,18 @@
 
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
-[id="backing-up-the-3scale-operator_{context}"]
-= Backing up the 3scale Operator
+[id="backing-up-the-3scale-operator-secret-apimanager_{context}"]
+= Backing up the 3scale Operator, secret, and APIManager
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the 3scale Operator resources, and `Secret` and APIManager custom resources (CR).
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
You can back up Red{nbsp}Hat build of 3scale Operator resources, and both the `Secret` custom resource (CR) and APIManager CR.
```
"CR" is not plural. We use CRs in that case, but you're wanting to define "CR" here.
created_at: 2025-04-22T13:09:59Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2,18 +2,18 @@
 
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
-[id="backing-up-the-3scale-operator_{context}"]
-= Backing up the 3scale Operator
+[id="backing-up-the-3scale-operator-secret-apimanager_{context}"]
+= Backing up the 3scale Operator, secret, and APIManager
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the 3scale Operator resources, and `Secret` and APIManager custom resources (CR).
 
 .Prerequisites
 
 * You created the Data Protection Application (DPA). 
 
 .Procedure
 
-. Back up the Operator resources, such as `operatorgroup`, `namespaces`, and `subscriptions`, by creating a YAML file with the following configuration: 
+. Back up the 3scale Operator resources, such as `operatorgroup`, `namespaces`, and `subscriptions`, by creating a YAML file with the following configuration: 
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
. Back up your Red{nbsp}Hat build of 3scale Operator CRs, such as `operatorgroup`, `namespaces`, and `subscriptions`, by creating a YAML file with the following configuration: 
```
We say "such as" here, but that leads me to believe there are more, and potentially custom CRs, so I would change "the" to "your" here.
created_at: 2025-04-22T13:12:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -37,7 +37,8 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> Namespace where the 3scale Operator is installed.
+<1> Use this as the `backupName` value while restoring the 3scale Operator.
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
<1> The value of the `metadata.name` parameter in the backup is the same value used in the `metadata.backupName` parameter used when restoring the Red{nbsp} build of 3scale Operator.
```
Maybe? This bullet does needs clarification.
created_at: 2025-04-22T13:17:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -37,7 +37,8 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> Namespace where the 3scale Operator is installed.
+<1> Use this as the `backupName` value while restoring the 3scale Operator.
+<2> Namespace where the 3scale Operator is installed.
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
<2> Namespace where the Red{nbsp}Hat build of 3scale Operator is installed.
```
Can this be more than one namespace? It is presented as a list here. Do we need to backup instances one namespace at a time?
created_at: 2025-04-22T13:18:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -77,13 +85,21 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring `Secret`.
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: ShaunaDiaz
body: clarify, see previous comment
created_at: 2025-04-22T13:19:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -77,13 +85,21 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring `Secret`.
 
-. Create the Secret CR by running the following command:
+. Create the `Secret` CR by running the following command:
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
. Create the `Secret` backup CR by running the following command:
```
These CRs are specific to the backups, correct? We are creating the `backup-secret` YAML here? Not the original. Should be specified throughout if true.
created_at: 2025-04-22T13:20:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -110,14 +126,18 @@ spec:
   volumeSnapshotLocations:
   - ts-dpa-1
 ----
+<1> Use this as the `backupName` value while APIManager.
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: ShaunaDiaz
body: clarify, see previous
created_at: 2025-04-22T13:41:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can back up the Redis database by adding the required annotations and by lis
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up the mysql database.
+* You backed up the MySQL database.
path: modules/backing-up-the-backend-redis-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You backed up your MySQL database.
```
Are we only supporting MySQL and Redis? It's unclear.
created_at: 2025-04-22T13:42:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -69,23 +67,44 @@ spec:
   snapshotVolumes: false
   ttl: 720h0m0s
 ----
+<1> Use this as the `backupName` value while restoring the Redis database.
path: modules/backing-up-the-backend-redis-database.adoc
user: login: ShaunaDiaz
body: clarify, see previous
created_at: 2025-04-22T13:42:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,9 +3,9 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 [id="backing-up-the-mysql-database_{context}"]
-= Backing up the mysql database
+= Backing up the MySQL database
path: modules/backing-up-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
= Backing up a MySQL database
```
created_at: 2025-04-22T13:43:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,9 +3,9 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 [id="backing-up-the-mysql-database_{context}"]
-= Backing up the mysql database
+= Backing up the MySQL database
 
-You can back up the `mysql` database by creating and attaching a persistent volume claim (PVC) to include the dumped data in the specified path.
+You can back up the MySQL database by creating and attaching a persistent volume claim (PVC) to include the dumped data in the specified path.
path: modules/backing-up-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
You can back up a MySQL database by creating and attaching a persistent volume claim (PVC) to include the dumped data in the specified path.
```
In the path you specify to the PV itself?
created_at: 2025-04-22T13:43:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -111,34 +111,45 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> A directory where the data is backed up.
-<2> Resources to back up.
+<1> Use this as the `backupName` value while restoring the MySQL database.
path: modules/backing-up-the-mysql-database.adoc
user: login: ShaunaDiaz
body: clarify, see previous
created_at: 2025-04-22T13:45:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -111,34 +111,45 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> A directory where the data is backed up.
-<2> Resources to back up.
+<1> Use this as the `backupName` value while restoring the MySQL database.
+<2> A directory where the data is backed up.
path: modules/backing-up-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
<2> Specify a directory for the backed up data.
```
Are there any requirements around which directories can be used?
created_at: 2025-04-22T13:51:17Z
author_association: CONTRIBUTOR
diff_hunk: @@ -111,34 +111,45 @@ spec:
   snapshotMoveData: false
   ttl: 720h0m0s
 ----
-<1> A directory where the data is backed up.
-<2> Resources to back up.
+<1> Use this as the `backupName` value while restoring the MySQL database.
+<2> A directory where the data is backed up.
+<3> Resources to back up.
path: modules/backing-up-the-mysql-database.adoc
user: login: ShaunaDiaz
body: Should the footnote be on line 100? This note is tied to the namespaces parameter.
created_at: 2025-04-22T13:55:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="creating-the-data-protection-application_{context}"]
 = Creating the Data Protection Application
path: modules/creating-the-data-protection-application.adoc
user: login: ShaunaDiaz
body: ```suggestion
= Creating a Data Protection Application
```
Why? What's the goal of this procedure?
created_at: 2025-04-22T13:57:18Z
author_association: CONTRIBUTOR
diff_hunk: @@ -5,7 +5,7 @@
 [id="creating-the-data-protection-application_{context}"]
 = Creating the Data Protection Application
 
-You can create a Data Protection Application (DPA) custom resource (CR) for 3scale. For more information on DPA, see "Installing the Data Protection Application".
+You can create a Data Protection Application (DPA) custom resource (CR) for 3scale.
path: modules/creating-the-data-protection-application.adoc
user: login: ShaunaDiaz
body: ```suggestion
To <insert why here>, you can create a Data Protection Application (DPA) custom resource (CR) for Red{nbsp}Hat build of 3scale.
```
why?
created_at: 2025-04-22T13:57:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,18 +3,18 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 
-[id="restoring-the-secrets-and-apimanager_{context}"]
-= Restoring the secrets and APIManager
+[id="restoring-the-3scale-operator-secrets-and-apimanager_{context}"]
+= Restoring the 3scale Operator, secrets, and APIManager
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
= Restoring the Red{nbsp}Hat build of 3scale Operator, secrets, and APIManager
```
created_at: 2025-04-22T13:59:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,18 +3,18 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 
-[id="restoring-the-secrets-and-apimanager_{context}"]
-= Restoring the secrets and APIManager
+[id="restoring-the-3scale-operator-secrets-and-apimanager_{context}"]
+= Restoring the 3scale Operator, secrets, and APIManager
 
-You can restore the Secrets and APIManager by using the following procedure.
+You can restore the 3scale Operator resources, and `Secret` and APIManager custom resources (CR) by using the following procedure.
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
You can restore the Red{nbsp}Hat build of 3scale Operator and `Secret` and APIManager custom resources (CRs) by using the following procedure.
```
why?
created_at: 2025-04-22T14:00:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,18 +3,18 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 
-[id="restoring-the-secrets-and-apimanager_{context}"]
-= Restoring the secrets and APIManager
+[id="restoring-the-3scale-operator-secrets-and-apimanager_{context}"]
+= Restoring the 3scale Operator, secrets, and APIManager
 
-You can restore the Secrets and APIManager by using the following procedure.
+You can restore the 3scale Operator resources, and `Secret` and APIManager custom resources (CR) by using the following procedure.
 
 .Prerequisites
 
 * You backed up the 3scale Operator.
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You backed up the Red{nbsp}Hat build of 3scale Operator.
```
I would fix this naming throughout.
created_at: 2025-04-22T14:01:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,18 +3,18 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 
-[id="restoring-the-secrets-and-apimanager_{context}"]
-= Restoring the secrets and APIManager
+[id="restoring-the-3scale-operator-secrets-and-apimanager_{context}"]
+= Restoring the 3scale Operator, secrets, and APIManager
 
-You can restore the Secrets and APIManager by using the following procedure.
+You can restore the 3scale Operator resources, and `Secret` and APIManager custom resources (CR) by using the following procedure.
 
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up the MySQL and Redis databases.
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You backed up the MySQL and Redis databases.
```
Again, are these required databases, supported databases, just examples for any customer databases?
created_at: 2025-04-22T14:01:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,18 +3,18 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 
-[id="restoring-the-secrets-and-apimanager_{context}"]
-= Restoring the secrets and APIManager
+[id="restoring-the-3scale-operator-secrets-and-apimanager_{context}"]
+= Restoring the 3scale Operator, secrets, and APIManager
 
-You can restore the Secrets and APIManager by using the following procedure.
+You can restore the 3scale Operator resources, and `Secret` and APIManager custom resources (CR) by using the following procedure.
 
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up `mysql` and Redis databases.
+* You backed up the MySQL and Redis databases.
 * You are restoring the database on the same cluster, where it was backed up. 
 +
-If it is on a different cluster, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster as it was on the source cluster.
+If you are restoring on a different cluster, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster. Ensure that the {oadp-short} configuration is same as it was on the source cluster.
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
If you are restoring the Operator to a different cluster that you backed up from, install and configure {oadp-short} with `nodeAgent` enabled on the destination cluster. Ensure that the {oadp-short} configuration is same as it was on the source cluster.
```
created_at: 2025-04-22T14:02:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -57,15 +57,23 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
+<1> Restoring the 3scale Operator's backup
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ? this clearly needs some explanatory text
created_at: 2025-04-22T14:07:44Z
author_association: CONTRIBUTOR
diff_hunk: @@ -95,8 +103,15 @@ EOF
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=0 -n threescale
 ----
++
+.Example output
++
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
 
-. Create a YAML file with the following configuration to restore the Secrets:
+. Create a YAML file with the following configuration to restore the `Secret`:
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
. Create a `restore-secret` YAML file with the following configuration to restore the `Secret` CR:
```
created_at: 2025-04-22T14:08:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -121,13 +136,21 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
+<1> Restoring the `Secret` backup.
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: explanatory text, e.g., "Use the name you specified in the `metadata.name` field of the backup YAML", etc.
created_at: 2025-04-22T14:10:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -121,13 +136,21 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
+<1> Restoring the `Secret` backup.
 
-. Restore the Secrets by running the following command:
+. Restore the `Secret` by running the following command:
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
. Restore the `Secret` CR by running the following command:
```
created_at: 2025-04-22T14:10:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -153,22 +176,33 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
-<1> The resources that you do not want to restore.
+<1> Restoring the APIManager backup.
+<2> The resources that you do not want to restore.
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
<2> List any resources that you do not want to restore.
```
created_at: 2025-04-22T14:10:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -153,22 +176,33 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
-<1> The resources that you do not want to restore.
+<1> Restoring the APIManager backup.
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: explanatory text needed
created_at: 2025-04-22T14:11:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -153,22 +176,33 @@ spec:
   - backuprepositories.velero.io
   itemOperationTimeout: 4h0m0s
 ----
-<1> The resources that you do not want to restore.
+<1> Restoring the APIManager backup.
+<2> The resources that you do not want to restore.
 
 . Restore the APIManager by running the following command:
path: modules/restoring-the-3scale-operator-secrets-and-apimanager.adoc
user: login: ShaunaDiaz
body: ```suggestion
. Restore the `APIManager` CR by running the following command:
```
created_at: 2025-04-22T14:11:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -55,13 +55,21 @@ spec:
   itemOperationTimeout: 1h0m0s
   restorePVs: true
 ----
+<1> Restoring the Redis backup.
path: modules/restoring-the-backend-redis-database.adoc
user: login: ShaunaDiaz
body: explanatory text needed
created_at: 2025-04-22T14:14:57Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,13 +3,13 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 [id="restoring-the-mysql-database_{context}"]
-= Restoring the mysql database
+= Restoring the MySQL database
path: modules/restoring-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
= Restoring a MySQL database
```
created_at: 2025-04-22T14:15:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,13 +3,13 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 [id="restoring-the-mysql-database_{context}"]
-= Restoring the mysql database
+= Restoring the MySQL database
 
-Restoring the `mysql` database re-creates the following resources:
+Restoring the MySQL database re-creates the following resources:
path: modules/restoring-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
Restoring a MySQL database re-creates the following resources:
```
created_at: 2025-04-22T14:15:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -3,13 +3,13 @@
 //included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
 
 [id="restoring-the-mysql-database_{context}"]
-= Restoring the mysql database
+= Restoring the MySQL database
 
-Restoring the `mysql` database re-creates the following resources:
+Restoring the MySQL database re-creates the following resources:
 
 * The `Pod`, `ReplicationController`, and `Deployment` objects.
 * The additional persistent volumes (PVs) and associated persistent volume claims (PVCs). 
-* The `mysql` dump, which the `example-claim` PVC contains.
+* The MySQL dump, which the `example-claim` PVC contains.
path: modules/restoring-the-mysql-database.adoc
user: login: ShaunaDiaz
body: A PVC doesn't contain anything, it is a request for resources, to my understanding. The PV would hold the actual data. 
created_at: 2025-04-22T14:20:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -18,7 +18,7 @@ Do not delete the default PV and PVC associated with the database. If you do, yo
 
 .Prerequisites
 
-* You restored the Secret and APIManager custom resources (CR).
+* You restored the `Secret` and APIManager custom resources (CR).
path: modules/restoring-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You restored the `Secret` and APIManager custom resources (CRs).
```
created_at: 2025-04-22T14:21:08Z
author_association: CONTRIBUTOR
diff_hunk: @@ -42,7 +42,7 @@ deployment.apps/threescale-operator-controller-manager-v2 scaled
 $ vi ./scaledowndeployment.sh
 ----
 +
-.Example output:
+.Example script file:
path: modules/restoring-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
.Example script:
```
I think this is just contents, not a file itself
created_at: 2025-04-22T14:21:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -126,22 +126,30 @@ spec:
                   
                   mysql -h 127.0.0.1 -D system -u root
                   --password=$MYSQL_ROOT_PASSWORD <
-                  /var/lib/mysqldump/data/dump.sql <1>
+                  /var/lib/mysqldump/data/dump.sql <2>
               container: system-mysql
               execTimeout: 80s
               onError: Fail
               waitTimeout: 5m
   itemOperationTimeout: 1h0m0s
   restorePVs: true
 ----
-<1> A path where the data is restored from.
+<1> Restoring the MySQL backup.
path: modules/restoring-the-mysql-database.adoc
user: login: ShaunaDiaz
body: explanatory text needed
created_at: 2025-04-22T14:22:05Z
author_association: CONTRIBUTOR
diff_hunk: @@ -126,22 +126,30 @@ spec:
                   
                   mysql -h 127.0.0.1 -D system -u root
                   --password=$MYSQL_ROOT_PASSWORD <
-                  /var/lib/mysqldump/data/dump.sql <1>
+                  /var/lib/mysqldump/data/dump.sql <2>
               container: system-mysql
               execTimeout: 80s
               onError: Fail
               waitTimeout: 5m
   itemOperationTimeout: 1h0m0s
   restorePVs: true
 ----
-<1> A path where the data is restored from.
+<1> Restoring the MySQL backup.
+<2> A path where the data is restored from.
path: modules/restoring-the-mysql-database.adoc
user: login: ShaunaDiaz
body: ```suggestion
<2> Specify the path where the data is restored from.
```
Unless the path is auto-generated.
created_at: 2025-04-22T14:22:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -9,6 +9,8 @@ You can scale up the 3scale Operator and any deployment that was manually scaled
 
 .Prerequisites
 
+* You restored the 3scale Operator resources, `Secret` and APIManager custom resources (CR).
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You restored the Red{nbsp}Hat build of 3scale Operator and both the `Secret` and `APIManager` custom resources (CRs).
```
created_at: 2025-04-22T14:23:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -9,6 +9,8 @@ You can scale up the 3scale Operator and any deployment that was manually scaled
 
 .Prerequisites
 
+* You restored the 3scale Operator resources, `Secret` and APIManager custom resources (CR).
+* You restored the MySQL and back-end Redis database.
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: ShaunaDiaz
body: ```suggestion
* You restored the MySQL and back-end Redis databases.
```
created_at: 2025-04-22T14:23:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -21,19 +23,67 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
++
+.Example output
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: ShaunaDiaz
body: ```suggestion
. Verify that the Red{nbsp}Hat build of 3scale Operator was deployed by running the following command: 
```
created_at: 2025-04-22T14:30:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -21,19 +23,67 @@ There might be some `system-mysql` or `backend-redis` pods running detached from
 ----
 $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale
 ----
++
+.Example output
+[source,terminal]
+----
+deployment.apps/threescale-operator-controller-manager-v2 scaled
+----
 
-. Ensure that the 3scale Operator was deployed by running the following command: 
+. Ensure that all pods are running to verify if the 3scale Operator was deployed by running the following command: 
++
+[source,terminal]
+----
+$ oc get pods -n threescale
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: ShaunaDiaz
body: This isn't `oc get pods -A` which I expect to see when I read that I should verify "that all pods are running," hence the edit to the step text. (This command appears to only verify `threescale` pods.
created_at: 2025-04-22T14:32:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -57,4 +107,4 @@ zync-3scale-provider-mjxlb   3scale.apps.custom-cluster-name.openshift.com
 +
 In this example, `3scale-admin.apps.custom-cluster-name.openshift.com` is the 3scale-admin URL.
 
-. Use the URL from this output to log in to the 3scale Operator as an administrator. You can verify that the existing data is available before trying to create a backup.
\ No newline at end of file
+. Use the URL from this output to log in to the 3scale Operator as an administrator. You can verify that the data, when you took backup, is available.
path: modules/scaling-up-the-3scale-operator-and-deployment.adoc
user: login: ShaunaDiaz
body: ```suggestion
. Use the URL from this output to log in to the Red{nbsp}Hat build of 3scale Operator as an administrator. You can verify that the data, when you took backup, is available.
```
"You can verify that the data, when you took backup, is available." This isn't intelligible; do you mean something like "verify that the restored data is available"?
created_at: 2025-04-22T14:36:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -11,7 +11,7 @@ You can back up the Redis database by adding the required annotations and by lis
 .Prerequisites
 
 * You backed up the 3scale Operator.
-* You backed up the mysql database.
+* You backed up the MySQL database.
path: modules/backing-up-the-backend-redis-database.adoc
user: login: apurvabhide17
body: yes
created_at: 2025-04-28T18:51:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: that's how 3scale refers in their documentation, and APIManager is a CR
created_at: 2025-04-29T13:39:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,43 +1,33 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="backing-up-and-restoring-3scale-by-using-oadp_{context}"]
+[id="backing-up-and-restoring-3scale-by-using-oadp"]
 = Backing up and restoring 3scale by using OADP
 include::_attributes/common-attributes.adoc[]
 :context: backing-up-and-restoring-3scale-by-using-oadp
 
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://access.redhat.com/documentation/en-us/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
 toc::[]
 
-With Red Hat 3scale API Management (APIM), you can manage your APIs for internal or external users. Share, secure, distribute, control, and monetize your APIs on an infrastructure platform built with performance, customer control, and future growth in mind.
-You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirement.
+With Red Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale API Management components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale deployments by backing up application resources, persistent volumes, and configurations. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.adoc
user: login: apurvabhide17
body: In the 3scale docs, they are using RH 3scale in the first instance followed by using only "3scale" further. I'm following the consistency as per their documentation. 
created_at: 2025-04-29T13:41:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,31 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-api-management-by-using-oadp"]
+= Backing up 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-api-management-by-using-oadp
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://docs.redhat.com/en/documentation/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
+toc::[]
+
+You can back up Red{nbsp}Hat 3scale API Management components by backing up the 3scale operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.adoc
user: login: stevsmit
body: ```suggestion
You can back up Red{nbsp}Hat 3scale API Management components by backing up the 3scale Operator, and databases such as MySQL and Redis.
```
created_at: 2025-04-30T13:56:55Z
author_association: MEMBER
diff_hunk: @@ -3658,8 +3658,12 @@ Topics:
   - Name: OADP and 3scale
     Dir: oadp-3scale
     Topics:
-    - Name: Backing up and restoring 3scale by using OADP
-      File: backing-up-and-restoring-3scale-by-using-oadp
+    - Name: Backing up and restoring 3scale API Management by using OADP
path: _topic_maps/_topic_map.yml
user: login: stevsmit
body: This is something for future consideration: I'm not sure if 3 new assemblies are necessary when 2 would do. If these were nested I could understand why, but they're all the same level. So this specific module, "Backing up and restoring 3scale API Management by using OADP" probably isn't wholly necessary when the other two modules could cover the information provided in here. I'm not requesting you fix this before merging, but something you might look at in the future. 
created_at: 2025-04-30T13:58:14Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,27 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-and-restoring-3scale-api-management-by-using-oadp"]
+= Backing up and restoring 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-and-restoring-3scale-api-management-by-using-oadp
+
+toc::[]
+
+With Red{nbsp}Hat 3scale API Management, you can manage your APIs for internal or external users. 
+You can deploy 3scale components on-premise, in the cloud, as a managed service, or in any combination based on your requirements.
+
+With {oadp-first}, you can safeguard 3scale API Management deployments by backing up application resources, persistent volumes, and configurations. 
+
+[NOTE]
+====
+You can use the {oadp-first} Operator to back up and restore your 3scale API Management on-cluster storage databases without affecting your running services
+====
+
+You can configure OADP to perform the following operations with 3scale API Management: 
+
+* Create a backup of 3scale components by following the steps in xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.adoc#backing-up-3scale-api-management-by-using-oadp[Backing up 3scale API Management].
+* Restore the components to scale up the 3scale operator and deployment by following the steps in xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc#restoring-3scale-api-management-by-using-oadp[Restoring 3scale API Management].
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-api-management-by-using-oadp.adoc
user: login: stevsmit
body: ```suggestion
* Restore the components to scale up the 3scale Operator and deployment by following the steps in xref:../../../backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc#restoring-3scale-api-management-by-using-oadp[Restoring 3scale API Management].
```
created_at: 2025-04-30T14:20:28Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,32 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-api-management-by-using-oadp"]
+= Restoring 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-api-management-by-using-oadp
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://docs.redhat.com/en/documentation/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
+toc::[]
+
+You can restore Red{nbsp}Hat 3scale API Management components by restoring the backed up 3scale operator resources. You can also restore databases such as MySQL and Redis. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc
user: login: stevsmit
body: ```suggestion
You can restore Red{nbsp}Hat 3scale API Management components by restoring the backed up 3scale Operator resources. You can also restore databases such as MySQL and Redis. 
```
created_at: 2025-04-30T14:24:43Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,32 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-api-management-by-using-oadp"]
+= Restoring 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-api-management-by-using-oadp
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://docs.redhat.com/en/documentation/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
+toc::[]
+
+You can restore Red{nbsp}Hat 3scale API Management components by restoring the backed up 3scale operator resources. You can also restore databases such as MySQL and Redis. 
+
+After the data has been restored, you can scale up the 3scale operator and deployment. 
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc
user: login: stevsmit
body: ```suggestion
After the data has been restored, you can scale up the 3scale Operator and deployment. 
```
created_at: 2025-04-30T14:24:56Z
author_association: MEMBER
diff_hunk: @@ -0,0 +1,32 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="restoring-3scale-api-management-by-using-oadp"]
+= Restoring 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: restoring-3scale-api-management-by-using-oadp
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://docs.redhat.com/en/documentation/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
+toc::[]
+
+You can restore Red{nbsp}Hat 3scale API Management components by restoring the backed up 3scale operator resources. You can also restore databases such as MySQL and Redis. 
+
+After the data has been restored, you can scale up the 3scale operator and deployment. 
+
+.Prerequisites
+
+* You installed and configured Red{nbsp}Hat 3scale API Management. For more information, see link:{Link3scaleInstalling3scale}#install-threescale-on-openshift-guide[Installing 3scale API Management on OpenShift] and link:https://docs.redhat.com/en/documentation/red_hat_3scale_api_management[Red Hat 3scale API Management].
+
+* You backed up the 3scale operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.adoc
user: login: stevsmit
body: Last time I'll call it out, but we always capitalize Operator: https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#operator-name-capitalization
created_at: 2025-04-30T14:51:19Z
author_association: MEMBER
diff_hunk: @@ -1,19 +1,19 @@
 :_mod-docs-content-type: PROCEDURE
 
-//included in backing-up-and-restoring-3scale-by-using-oadp.adoc assembly
+//included in backing-up-3scale-api-management-by-using-oadp.adoc assembly
 
-[id="backing-up-the-3scale-operator_{context}"]
-= Backing up the 3scale Operator
+[id="backing-up-the-3scale-operator-secret-apimanager_{context}"]
+= Backing up the 3scale API Management operator, secret, and APIManager
 
-You can back up the Operator resources, and Secret and APIManager custom resources (CR). For more information, see "Creating a Backup CR".
+You can back up the Red{nbsp}Hat 3scale API Management operator resources, and both the `Secret` and APIManager custom resource (CR).
path: modules/backing-up-the-3scale-operator-secret-apimanager.adoc
user: login: stevsmit
body: Because you use plural resources everywhere else: 

```suggestion
You can back up the Red{nbsp}Hat 3scale API Management operator resources, and both the `Secret` and APIManager custom resources (CR).
```
created_at: 2025-04-30T15:55:28Z
author_association: MEMBER
diff_hunk: @@ -3658,8 +3658,12 @@ Topics:
   - Name: OADP and 3scale
     Dir: oadp-3scale
     Topics:
-    - Name: Backing up and restoring 3scale by using OADP
-      File: backing-up-and-restoring-3scale-by-using-oadp
+    - Name: Backing up and restoring 3scale API Management by using OADP
path: _topic_maps/_topic_map.yml
user: login: apurvabhide17
body: It helps to find the sub-assemblies in the right side ToC with the existing OCP structure 
created_at: 2025-04-30T17:39:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,31 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="backing-up-3scale-api-management-by-using-oadp"]
+= Backing up 3scale API Management by using OADP
+include::_attributes/common-attributes.adoc[]
+:context: backing-up-3scale-api-management-by-using-oadp
+:3scaleProductVersion: 2.15
+:3scaleDocInfoProductName: red_hat_3scale_api_management
+:Link3scaleInstalling3scale: https://docs.redhat.com/en/documentation/{3scaleDocInfoProductName}/{3scaleProductVersion}/html-single/installing_red_hat_3scale_api_management/index
+
+toc::[]
+
+You can back up Red{nbsp}Hat 3scale API Management components by backing up the 3scale operator, and databases such as MySQL and Redis.
path: backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.adoc
user: login: apurvabhide17
body: Since this user story focuses on 3scale, their team suggested to use "operator" instead of "Operator" along with other guidelines for using the official product name for 3scale
created_at: 2025-04-30T17:40:29Z
author_association: CONTRIBUTOR

PR comments:
user: login: openshift-ci-robot
created_at: 2025-02-24T14:38:23Z
body: @apurvabhide17: This pull request references [OADP-5634](https://issues.redhat.com//browse/OADP-5634) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068):

>Version(s):
>OCP 4.14 → OCP 4.18
>
>Issue:
>[OADP-5634](https://issues.redhat.com/browse/OADP-5634)
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: apurvabhide17
created_at: 2025-02-24T14:39:18Z
body: /label OADP
author_association: CONTRIBUTOR
user: login: ocpdocs-previewbot
created_at: 2025-02-24T14:57:08Z
body: 🤖 Tue Apr 29 19:14:47 - Prow CI generated the docs preview:

https://89068--ocpdocs-pr.netlify.app/
https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp.html
https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-api-management-by-using-oadp.html
https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp.html
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-03-02T18:46:55Z
body: @apurvabhide17: This pull request references [OADP-5634](https://issues.redhat.com//browse/OADP-5634) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068):

>Version(s):
>OCP 4.14 → OCP 4.18
>
>Issue:
>[OADP-5634](https://issues.redhat.com/browse/OADP-5634)
>
>Link to docs preview:
>https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.html
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-03-13T18:53:04Z
body: @apurvabhide17: This pull request references [OADP-5634](https://issues.redhat.com//browse/OADP-5634) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068):

>Version(s):
>OCP 4.14 → OCP 4.18
>
>Issue:
>[OADP-5634](https://issues.redhat.com/browse/OADP-5634)
>
>Link to docs preview:
>
>- [Backing up and restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp)
>- [Backing up 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp)
>- [Restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp)
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: anarnold97
created_at: 2025-03-21T19:48:11Z
body: LGTM ... no need to send it for another review, once QE are happy kick it over to OCP review. 
 
Taxonomy looks good, easier to navigate

I think this works well

![image](https://github.com/user-attachments/assets/16da0cbf-0201-42ed-b60d-bd41c4efeb77)

Eases navigation... should we do more things like this?

author_association: CONTRIBUTOR
user: login: apurvabhide17
created_at: 2025-04-17T09:44:00Z
body: /test validate-asciidoc
/test validate-portal
author_association: CONTRIBUTOR
user: login: openshift-ci-robot
created_at: 2025-04-21T17:02:54Z
body: @apurvabhide17: This pull request references [OADP-5634](https://issues.redhat.com//browse/OADP-5634) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068):

>Version(s):
>OCP 4.14 → OCP 4.18
>
>Issue:
>[OADP-5634](https://issues.redhat.com/browse/OADP-5634)
>
>Link to docs preview:
>
>- [Backing up and restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp)
>- [Backing up 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp)
>- [Restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp)
>
>QE review:
>- [x] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-21T17:12:50Z
body: @apurvabhide17: This pull request references [OADP-5634](https://issues.redhat.com//browse/OADP-5634) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068):

>Version(s):
>OCP 4.14 → OCP 4.18
>
>Issue:
>[OADP-5634](https://issues.redhat.com/browse/OADP-5634)
>
>Link to docs preview:
>
>- [Backing up and restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp)
>- [Backing up 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp)
>- [Restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp)
>
>QE review:
>- [x] QE has approved this change.
>
>Additional information - 
>This PR focuses on the following points to improve the existing [Backing up and restoring 3scale by using OADP](https://docs.openshift.com/container-platform/4.17/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.html). user story from the related PR - [PR#85994](https://github.com/openshift/openshift-docs/pull/85994) - 
>
>- Updating description/command for oc get deployment -n threescale and oc edit deployment system-mysql -n threescale.
>
>Structural changes to split Backing up and restoring 3scale by using OADP:
>
>- Backing up 3scale
>-- Creating the Data Protection Application
>-- Backing up the 3scale Operator
>-- Backing up the mysql database
>-- Backing up the backend Redis database
>
>- Restoring 3scale
>-- Restoring the secrets and APIManager
>-- Restoring the mysql database
>-- Restoring the back-end Redis database
>-- Scaling up the 3scale operator and deployment


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: apurvabhide17
created_at: 2025-04-21T17:13:24Z
body: /label peer-review-needed
author_association: CONTRIBUTOR
user: login: ShaunaDiaz
created_at: 2025-04-22T11:07:12Z
body: @apurvabhide17 This PR cannot merge into `main` unless it also goes to `enterprise-4.19`.  If this content _cannot_ also go in 4.19, you can make a new one from the 4.18 branch and we can cherry-pick back. Please confirm either way.
author_association: CONTRIBUTOR
user: login: openshift-ci-robot
created_at: 2025-04-22T13:41:35Z
body: @apurvabhide17: This pull request references [OADP-5634](https://issues.redhat.com//browse/OADP-5634) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068):

>Version(s):
>OCP 4.14 → OCP 4.19
>
>Issue:
>[OADP-5634](https://issues.redhat.com/browse/OADP-5634)
>
>Link to docs preview:
>
>- [Backing up and restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp)
>- [Backing up 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-by-using-oadp)
>- [Restoring 3scale by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-by-using-oadp)
>
>QE review:
>- [x] QE has approved this change.
>
>Additional information - 
>This PR focuses on the following points to improve the existing [Backing up and restoring 3scale by using OADP](https://docs.openshift.com/container-platform/4.17/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.html). user story from the related PR - [PR#85994](https://github.com/openshift/openshift-docs/pull/85994) - 
>
>- Updating description/command for oc get deployment -n threescale and oc edit deployment system-mysql -n threescale.
>
>Structural changes to split Backing up and restoring 3scale by using OADP:
>
>- Backing up 3scale
>-- Creating the Data Protection Application
>-- Backing up the 3scale Operator
>-- Backing up the mysql database
>-- Backing up the backend Redis database
>
>- Restoring 3scale
>-- Restoring the secrets and APIManager
>-- Restoring the mysql database
>-- Restoring the back-end Redis database
>-- Scaling up the 3scale operator and deployment


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: apurvabhide17
created_at: 2025-04-22T13:43:04Z
body: > @apurvabhide17 This PR cannot merge into `main` unless it also goes to `enterprise-4.19`. If this content _cannot_ also go in 4.19, you can make a new one from the 4.18 branch and we can cherry-pick back. Please confirm either way.

Hi @ShaunaDiaz, I've updated the version (OCP 4.14 → OCP 4.19) after confirming it with QE.
author_association: CONTRIBUTOR
user: login: openshift-ci-robot
created_at: 2025-04-29T18:36:24Z
body: @apurvabhide17: This pull request references [OADP-5634](https://issues.redhat.com//browse/OADP-5634) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068):

>Version(s):
>OCP 4.14 → OCP 4.19
>
>Issue:
>[OADP-5634](https://issues.redhat.com/browse/OADP-5634)
>
>Link to docs preview:
>
>- [Backing up and restoring 3scale API Management by using OADP
>](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-api-management-by-using-oadp)
>- [Backing up 3scale API Management by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-3scale-api-management-by-using-oadp)
>- [Restoring 3scale API Management by using OADP](https://89068--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/application_backup_and_restore/oadp-3scale/restoring-3scale-api-management-by-using-oadp)
>
>QE review:
>- [x] QE has approved this change.
>
>Additional information - 
>This PR focuses on the following points to improve the existing [Backing up and restoring 3scale by using OADP](https://docs.openshift.com/container-platform/4.17/backup_and_restore/application_backup_and_restore/oadp-3scale/backing-up-and-restoring-3scale-by-using-oadp.html). user story from the related PR - [PR#85994](https://github.com/openshift/openshift-docs/pull/85994) - 
>
>- Updating description/command for oc get deployment -n threescale and oc edit deployment system-mysql -n threescale.
>
>Structural changes to split Backing up and restoring 3scale by using OADP:
>
>- Backing up 3scale
>-- Creating the Data Protection Application
>-- Backing up the 3scale Operator
>-- Backing up the mysql database
>-- Backing up the backend Redis database
>
>- Restoring 3scale
>-- Restoring the secrets and APIManager
>-- Restoring the mysql database
>-- Restoring the back-end Redis database
>-- Scaling up the 3scale operator and deployment


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: apurvabhide17
created_at: 2025-04-29T18:53:50Z
body: > I think you need to determine the product or component naming that should be used. A lot of places need solid explanatory text that is missing; this PR feels unfinished and not truly ready for peer review. Please make changes and put back in peer review prior to submitting for merge review.

Hi @ShaunaDiaz, thanks for reviewing my PR, I've implemented the suggestions apart from naming guidelines for 3scale. 
I had discussion with the 3scale writer and I've updated it as per the 3scale team's guidelines w.r.t to this [epic](https://issues.redhat.com/browse/THREESCALE-10508).  This includes -

- 3scale API Management instead of 3scale in the title
- Red Hat 3scale API Management in the abstract
- Once the above usage is completed, further refer to it as only 3scale for the ease of reading
- Replace Operator by operator
- There were no guidelines to use Red Hat build of 3scale
- It is APIManager and not API manager.
- It is API Management and not API management

If all looks good, could I go ahead with the merge review? If there are any other improvements, I can create another PR for it. Thanks!
author_association: CONTRIBUTOR
user: login: apurvabhide17
created_at: 2025-04-29T19:02:25Z
body: /label merge-review-needed

author_association: CONTRIBUTOR
user: login: apurvabhide17
created_at: 2025-04-29T19:06:13Z
body: I've incorporated all the basic suggestions related to links, callouts, prerequisites, and other suggestions from the peer-review. Apart from that, I've also followed the guidelines of using 3scale in the docs as per the [official RH product names](https://docs.google.com/spreadsheets/d/1DLS_lS3VKidgZIvcLmLp9BoiqptkvqHWfe1D5FD2kfk/edit?gid=1259317633#gid=1259317633) sheet and by discussing with the 3scale writer.

Could you please merge this PR? If there are any other suggestions, I can create another PR for it.
Thanks!
author_association: CONTRIBUTOR
user: login: openshift-ci[bot]
created_at: 2025-04-29T19:15:45Z
body: @apurvabhide17: all tests **passed!**


[Full PR test history](https://prow.ci.openshift.org/pr-history?org=openshift&repo=openshift-docs&pr=89068). [Your PR dashboard](https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:apurvabhide17).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
author_association: NONE
user: login: stevsmit
created_at: 2025-04-30T16:03:20Z
body: /cherry-pick enterprise-4.19
author_association: MEMBER
user: login: stevsmit
created_at: 2025-04-30T16:03:24Z
body: /cherry-pick enterprise-4.18
author_association: MEMBER
user: login: stevsmit
created_at: 2025-04-30T16:03:28Z
body: /cherry-pick enterprise-4.17
author_association: MEMBER
user: login: stevsmit
created_at: 2025-04-30T16:03:36Z
body: /cherry-pick enterprise-4.16
author_association: MEMBER
user: login: stevsmit
created_at: 2025-04-30T16:03:39Z
body: /cherry-pick enterprise-4.15
author_association: MEMBER
user: login: stevsmit
created_at: 2025-04-30T16:03:42Z
body: /cherry-pick enterprise-4.14
author_association: MEMBER
user: login: openshift-cherrypick-robot
created_at: 2025-04-30T16:04:07Z
body: @stevsmit: new pull request created: #92801

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068#issuecomment-2842488865):

>/cherry-pick enterprise-4.19


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-30T16:04:11Z
body: @stevsmit: new pull request created: #92802

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068#issuecomment-2842489102):

>/cherry-pick enterprise-4.18


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-30T16:04:14Z
body: @stevsmit: new pull request created: #92803

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068#issuecomment-2842489500):

>/cherry-pick enterprise-4.17


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-30T16:04:23Z
body: @stevsmit: new pull request created: #92804

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068#issuecomment-2842490079):

>/cherry-pick enterprise-4.16


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-30T16:04:29Z
body: @stevsmit: new pull request created: #92805

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068#issuecomment-2842490267):

>/cherry-pick enterprise-4.15


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-30T16:04:33Z
body: @stevsmit: new pull request created: #92806

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/89068#issuecomment-2842490428):

>/cherry-pick enterprise-4.14


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: apurvabhide17
created_at: 2025-04-30T17:42:28Z
body: > This looks really good overall, and nothing I've commented should hold up a merge. I've left a few comments for you to consider in a future PR. One thing I've noticed is that, in our docs, we sometimes either capitalize 3scale Operator and in your PR you do not. Maybe the official name isn't capitalized, or maybe it is. Generally for OCP we require Operator to be capitalized, but there needs to be some consistency between what's in the docs now (whether that requires changed it to a capital O or lowercase o).
> 
> Overall, good work!

Thanks @stevsmit for reviewing and merging this PR. 
Since this user story focuses on 3scale, their team suggested to use "operator" instead of "Operator" along with other guidelines for using the official product name for 3scale 
author_association: CONTRIBUTOR