mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 15:46:57 +01:00
59668391b7
Reviewed modules from OADP Monitoring assembly Updated modules for timeouts, backup and restore CR issues, and restic issues Peer review Updated modules for OADP operator, OADP installation, and issues with velero and admission webhooks Apply OCP peer review suggestions Co-authored-by: Laura Hinson <lahinson@redhat.com> Suggestions from merge review Co-authored-by: Michael Peter <mipeter@redhat.com> Update migration-debugging-velero-admission-webhooks-ibm-appconnect.adoc Update migration-debugging-velero-resources.adoc Update backup_and_restore/application_backup_and_restore/troubleshooting/backup-and-restore-cr-issues.adoc Co-authored-by: Michael Peter <mipeter@redhat.com>
56 lines
1.3 KiB
Plaintext
56 lines
1.3 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
//backup_and_restore/application_backup_and_restore/troubleshooting/velero-cli-tool.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="oadp-debugging-oc-cli_{context}"]
|
|
= Debugging Velero resources with the OpenShift CLI tool
|
|
|
|
You can debug a failed backup or restore by checking Velero custom resources (CRs) and the `Velero` pod log with the OpenShift CLI tool.
|
|
|
|
.Procedure
|
|
|
|
* Retrieve a summary of warnings and errors associated with a `Backup` or `Restore` CR by using the following `oc describe` command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc describe <velero_cr> <cr_name>
|
|
----
|
|
|
|
* Retrieve the `Velero` pod logs by using the following `oc logs` command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc logs pod/<velero>
|
|
----
|
|
|
|
* Specify the Velero log level in the `DataProtectionApplication` resource as shown in the following example.
|
|
+
|
|
[NOTE]
|
|
====
|
|
This option is available starting from {oadp-short} 1.0.3.
|
|
====
|
|
+
|
|
.Example Velero log level file
|
|
[source,yaml]
|
|
----
|
|
apiVersion: oadp.openshift.io/v1alpha1
|
|
kind: DataProtectionApplication
|
|
metadata:
|
|
name: velero-sample
|
|
spec:
|
|
configuration:
|
|
velero:
|
|
logLevel: warning
|
|
----
|
|
+
|
|
The following `logLevel` values are available:
|
|
* `trace`
|
|
* `debug`
|
|
* `info`
|
|
* `warning`
|
|
* `error`
|
|
* `fatal`
|
|
* `panic`
|
|
+
|
|
Use the `info` `logLevel` value for most logs. |