Remove outdated docs (#1895)

* I will remove the outdated OADP 1.1.x and 1.2.x documentation.

* restore upgrade notes from 1.1 through

* keep restic troubleshooting

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

Author: weshayutin

docs/TROUBLESHOOTING.md

@@ -12,7 +12,6 @@ If you need help, first search if there is [already an issue filed](https://issu
 1. [Debugging OpenShift Virtualization backup/restore](virtualization_troubleshooting.md)
 1. [Debugging OADP Self Service](self-service_troubleshooting.md)
 1. [Deleting Backups](#deleting-backups)
-1. [Debugging Data Mover (OADP 1.2 or below)](https://github.com/migtools/volume-snapshot-mover/blob/master/docs/troubleshooting.md)
 1. [OpenShift ROSA STS and OADP installation](https://github.com/rh-mobb/documentation/blob/main/content/docs/misc/oadp/rosa-sts/_index.md)
 1. [Common Issues and Misconfigurations](#common-issues-and-misconfigurations)
     - [Credentials Not Properly Formatted](#credentials-secret-not-properly-formatted)
@@ -36,10 +35,6 @@ If you need help, first search if there is [already an issue filed](https://issu
     ```
     oc logs -f deploy/velero -n openshift-adp
     ```
-    - If Data Mover (OADP 1.2 or below) is enabled, check the volume-snapshot-logs
-    ```
-    oc logs -f deployment.apps/volume-snapshot-mover -n openshift-adp
-    ```
     
 1. Velero commands
     -  Alias the velero command: 
@@ -77,10 +72,6 @@ This section includes how to debug a failed restore. For more specific issues re
     ```
     oc logs -f deployment.apps/velero -n openshift-adp
     ```
-    If Data Mover (OADP 1.2 or below) is enabled, check the volume-snapshot-logs
-    ```
-    oc logs -f deployment.apps/volume-snapshot-mover -n openshift-adp
-    ```
     
 1. Velero commands
     - Alias the velero command: 
@@ -250,40 +241,11 @@ oc delete backuprepository <backupRepositoryName> -n openshift-adp
 
 ### Issue with Backup/Restore of DeploymentConfig with volumes or restore hooks
 
--  (OADP 1.3+) **Error:** `DeploymentConfigs restore with spec.Replicas==0 or DC pods fail to restart if they crash if using DC with volumes or restore hooks`
-
-    **Solution:**
-
-    Solution is the same as in the (OADP 1.1+), except it applies to the use case if you are restoring DeploymentConfigs and have either volumes or post-restore hooks regardless of the backup method.
-
--  (OADP 1.1+) **Error:** `DeploymentConfigs restore with spec.Replicas==0 or DC pods fail to restart if they crash if using Restic/Kopia restores or restore hooks`
-
-    **Solution:**
-    
-    This is expected behavior on restore if you are restoring DeploymentConfigs and are either using Restic or Kopia for volume restore or you have post-restore hooks. The pod and DC plugins make these modifications to ensure that Restic or Kopia and hooks work properly, and [dc-post-restore.sh](../docs/scripts/dc-post-restore.sh) should have been run immediately after a successful restore. Usage for this script is `dc-post-restore.sh <restore-name>`
-
--  (OADP 1.0.z) **Error:** `Using Restic as backup method causes PartiallyFailed/Failed errors in the Restore or post-restore hooks fail to execute`
+- **Error:** `DeploymentConfigs restore with spec.Replicas==0 or DC pods fail to restart if they crash if using DC with volumes or restore hooks`
 
     **Solution:**
 
-    The changes in the backup/restore process for mitigating this error would be a two step restore process where, in the first step we would perform a restore excluding the replicationcontroller and deploymentconfig resources, and the second step would involve a restore including these resources. The backup and restore commands are given below for more clarity. (The examples given below are a use case for backup/restore of a target namespace, for other cases a similar strategy can be followed).
-
-    Please note that this is a temporary fix for this issue and there are ongoing discussions to solve it.
-
-    Step 1: Initiate the backup as any normal backup for restic.
-    ```
-    velero create backup <backup-name> -n openshift-adp --include-namespaces=<TARGET_NAMESPACE>
-    ```
-
-    Step 2: Initiate a restore excluding the replicationcontroller and deploymentconfig resources.
-    ```
-    velero restore create --from-backup=<BACKUP_NAME> -n openshift-adp --include-namespaces <TARGET_NAMESPACE> --exclude-resources replicationcontroller,deploymentconfig,templateinstances.template.openshift.io --restore-volumes=true
-    ```
-
-    Step 3: Initiate a restore including the replicationcontroller and deploymentconfig resources.
-    ```
-    velero restore create --from-backup=<BACKUP_NAME> -n openshift-adp --include-namespaces <TARGET_NAMESPACE> --include-resources replicationcontroller,deploymentconfig,templateinstances.template.openshift.io --restore-volumes=true
-    ```
+    This is expected behavior on restore if you are restoring DeploymentConfigs and have either volumes or post-restore hooks. The pod and DC plugins make these modifications to ensure that Restic or Kopia and hooks work properly, and [dc-post-restore.sh](../docs/scripts/dc-post-restore.sh) should have been run immediately after a successful restore. Usage for this script is `dc-post-restore.sh <restore-name>`
 
 ### New Restic Backup Partially Failing After Clearing Bucket
 

docs/config/plugins.md

@@ -18,7 +18,6 @@ installing Velero:
    - `OpenShift` [OpenShift Velero Plugin](https://github.com/openshift/openshift-velero-plugin)
    - `CSI` [Plugins for CSI](https://github.com/vmware-tanzu/velero-plugin-for-csi)
    - `kubevirt` [Plugins for Kubevirt](https://github.com/kubevirt/kubevirt-velero-plugin)
-   - `VSM (OADP 1.2 or below)` [Plugin for Volume-Snapshot-Mover](https://github.com/migtools/velero-plugin-for-vsm)
 
    Note that only one of `AWS` and `Legacy AWS` may be installed at the same time. `Legacy AWS` is intended for use with certain S3 providers that do not support the V2 AWS SDK APIs used in the `AWS` plugin.
 

docs/credentials.md

@@ -10,7 +10,6 @@
     1. [BSL and VSL share credentials for one provider](#backupstoragelocation-and-volumesnapshotlocation-share-credentials-for-one-provider)
     2. [BSL and VSL use the same provider but use different credentials](#backupstoragelocation-and-volumesnapshotlocation-use-the-same-provider-but-use-different-credentials)
     3. [No BSL specified but the plugin for the provider exists](#no-backupstoragelocation-specified-but-the-plugin-for-the-provider-exists)
-5. [Creating a Secret: OADP with VolumeSnapshotMover](#creating-a-secret-for-volumesnapshotmover)
 
 ### Creating a Secret for OADP
 
@@ -214,22 +213,3 @@ spec:
 If you don't need volumesnapshotlocation, you will not need to create a VSL credentials.
 
 If you need `VolumeSnapshotLocation`, regardless of the `noDefaultBackupLocation` setting, you will need a to create VSL credentials.
-
-
-### Creating a Secret for volumeSnapshotMover (OADP 1.2 or below)
-
-VolumeSnapshotMover requires a restic secret. It can be configured as so:
-
-```
-apiVersion: v1
-kind: Secret
-metadata:
-  name: <secret-name>
-type: Opaque
-stringData:
-  # The repository encryption key
-  RESTIC_PASSWORD: my-secure-restic-password
-```
-
-- *Note:* `dpa.spec.features.dataMover.credentialName` must match the name of the secret. 
-  Otherwise it will default to the name `dm-credential`.