You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/oadp-backup-restore-for-large-usage.adoc
+1-1
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Testing shows that increasing `NodeAgent` CPU can significantly improve backup a
9
9
10
10
[IMPORTANT]
11
11
====
12
-
It is not recommended to use Kopia without limits in production environments on nodes running production workloads due to Kopia’s aggressive consumption of resources. However, running Kopia with limits that are too low results in CPU limiting and slow backups and restore situations.
12
+
Customers can tune their OpenShift environments based on the their analysis and preference. Red Hat does not recommend using CPU limits in environments where Kopia is required.
13
13
14
14
Testing showed that running Kopia with 20 cores and 32 Gi memory supported backup and restore operations of over 100 GB of data, multiple namespaces, or over 2000 pods in a single namespace. Testing detected no CPU limiting or memory saturation with these resource specifications.
0 commit comments