:_mod-docs-content-type: ASSEMBLY
[id="pods-crash-or-restart-due-to-lack-of-memory-or-cpu"]
= Pods crash or restart due to lack of memory or CPU
:toc:

include::_attributes/common-attributes.adoc[]
include::_attributes/attributes-openshift-dedicated.adoc[]
:context: pods-crash-or-restart-due-to-lack-of-memory-or-cpu
:namespace: openshift-adp
:local-product: OADP
:must-gather-v1-3: registry.redhat.io/oadp/oadp-mustgather-rhel9:v1.3
:must-gather-v1-4: registry.redhat.io/oadp/oadp-mustgather-rhel9:v1.4


[role="_abstract"]
Resolve Velero or Restic pod crashes caused by insufficient memory or CPU by configuring resource requests in the `DataProtectionApplication` custom resource (CR). This helps you allocate adequate CPU and memory resources to prevent pod restarts and ensure stable backup and restore operations.

Ensure that the values for the resource request fields follow the same format as Kubernetes resource requirements.

If you do not specify `configuration.velero.podConfig.resourceAllocations` or `configuration.restic.podConfig.resourceAllocations`, see the following default `resources` specification configuration for a Velero or Restic pod:

[source,yaml]
----
requests:
  cpu: 500m
  memory: 128Mi
----

[role="_additional-resources"]
.Additional resources
* xref:../../../backup_and_restore/application_backup_and_restore/installing/about-installing-oadp.adoc#oadp-velero-cpu-memory-requirements_about-installing-oadp[Velero CPU and memory requirements based on collected data]

include::modules/oadp-pod-crash-set-resource-request-velero.adoc[leveloffset=+1]

include::modules/velero-oomkilled-large-kopia-repos.adoc[leveloffset=+1]

include::modules/oadp-pod-crash-set-resource-request-restic.adoc[leveloffset=+1]

include::modules/setting-resource-requests-for-a-nodeagent-pod.adoc[leveloffset=+1]
