Skip to content

Commit 00e8537

Browse files
authored
Merge pull request #85615 from shdeshpa07/OADP-5268-Use-velero-io
Rename oc commands to use velero.io
2 parents b32a8f6 + 6da334c commit 00e8537

22 files changed

+29
-29
lines changed

backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-creating-backup-cr.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You back up Kubernetes resources, internal images, and persistent volumes (PVs)
3232
+
3333
[source,terminal]
3434
----
35-
$ oc get backupStorageLocations -n openshift-adp
35+
$ oc get backupstoragelocations.velero.io -n openshift-adp
3636
----
3737
+
3838
.Example output
@@ -84,5 +84,5 @@ spec:
8484
+
8585
[source,terminal]
8686
----
87-
$ oc get backup -n openshift-adp <backup> -o jsonpath='{.status.phase}'
87+
$ oc get backups.velero.io -n openshift-adp <backup> -o jsonpath='{.status.phase}'
8888
----

cloud_experts_tutorials/cloud-experts-deploy-api-data-protection.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -528,8 +528,8 @@ $ oc delete ns hello-world
528528
+
529529
[source,terminal]
530530
----
531-
$ oc delete backup hello-world
532-
$ oc delete restore hello-world
531+
$ oc delete backups.velero.io hello-world
532+
$ oc delete restores.velero.io hello-world
533533
----
534534

535535
. To delete the backup/restore and remote objects in s3:

modules/backup-hosted-cluster-virt.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ Replace `<backup_file_name>` with the name of your file.
8282
+
8383
[source,terminal]
8484
----
85-
$ watch "oc get backup -n openshift-adp <backup_file_name> -o jsonpath='{.status}' | jq"
85+
$ watch "oc get backups.velero.io -n openshift-adp <backup_file_name> -o jsonpath='{.status}' | jq"
8686
----
8787
+
8888
** To monitor the Velero logs, enter the following command:

modules/cleanup-a-backup-oadp-aws-sts.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ $ oc delete ns openshift-adp
6060
+
6161
[source,terminal]
6262
----
63-
$ oc delete backup hello-world
63+
$ oc delete backups.velero.io hello-world
6464
----
6565

6666
. To delete backup, restore and remote objects in {aws-short} S3, run the following command:

modules/cleanup-a-backup-oadp-rosa-sts.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ $ oc delete ns openshift-adp
6060
+
6161
[source,terminal]
6262
----
63-
$ oc delete backup hello-world
63+
$ oc delete backups.velero.io hello-world
6464
----
6565

6666
. To delete backup, restore and remote objects in {aws-short} S3 run the following command:

modules/hcp-dr-oadp-backup-cp-workload.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ $ oc apply -f backup-control-plane.yaml
136136
+
137137
[source,terminal]
138138
----
139-
$ oc get backup <backup_resource_name> -n openshift-adp -o jsonpath='{.status.phase}'
139+
$ oc get backups.velero.io <backup_resource_name> -n openshift-adp -o jsonpath='{.status.phase}'
140140
----
141141
142142
.Next steps

modules/hcp-dr-oadp-observe.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,14 @@ When using {oadp-first} to backup and restore a hosted cluster, you can monitor
1414
+
1515
[source,terminal]
1616
----
17-
$ watch "oc get backup -n openshift-adp <backup_resource_name> -o jsonpath='{.status}'"
17+
$ watch "oc get backups.velero.io -n openshift-adp <backup_resource_name> -o jsonpath='{.status}'"
1818
----
1919

2020
. Observe the restore process by running the following command:
2121
+
2222
[source,terminal]
2323
----
24-
$ watch "oc get restore -n openshift-adp <backup_resource_name> -o jsonpath='{.status}'"
24+
$ watch "oc get restores.velero.io -n openshift-adp <backup_resource_name> -o jsonpath='{.status}'"
2525
----
2626

2727
. Observe the Velero logs by running the following command:

modules/oadp-backup-restore-cr-issues.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ $ oc -n {namespace} exec deployment/velero -c velero -- ./velero \
4545
+
4646
[source,terminal]
4747
----
48-
$ oc delete backup <backup> -n openshift-adp
48+
$ oc delete backups.velero.io <backup> -n openshift-adp
4949
----
5050
+
5151
You do not need to clean up the backup location because a `Backup` CR in progress has not uploaded files to object storage.
@@ -79,7 +79,7 @@ time="2023-02-17T16:33:13Z" level=error msg="Error backing up item" backup=opens
7979
+
8080
[source,terminal]
8181
----
82-
$ oc delete backup <backup> -n openshift-adp
82+
$ oc delete backups.velero.io <backup> -n openshift-adp
8383
----
8484

8585
. If required, clean up the stored data on the `BackupStorageLocation` to free up space.

modules/oadp-creating-backup-cr.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ To back up Kubernetes resources, internal images, and persistent volumes (PVs),
2727
+
2828
[source,terminal]
2929
----
30-
$ oc get backupStorageLocations -n openshift-adp
30+
$ oc get backupstoragelocations.velero.io -n openshift-adp
3131
----
3232
+
3333
.Example output
@@ -79,5 +79,5 @@ spec:
7979
+
8080
[source,terminal]
8181
----
82-
$ oc get backup -n openshift-adp <backup> -o jsonpath='{.status.phase}'
82+
$ oc get backups.velero.io -n openshift-adp <backup> -o jsonpath='{.status.phase}'
8383
----

modules/oadp-creating-restore-cr.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ spec:
4646
+
4747
[source,terminal]
4848
----
49-
$ oc get restore -n openshift-adp <restore> -o jsonpath='{.status.phase}'
49+
$ oc get restores.velero.io -n openshift-adp <restore> -o jsonpath='{.status.phase}'
5050
----
5151

5252
. Verify that the backup resources have been restored by entering the following command:

0 commit comments

Comments
 (0)