Noobaa Support Cases Help Guide for ODF

Support Docs Links

Noobaa performance tuning
In many cases, the default resource limits\requests allocated for noobaa pods in ODF are not sufficient for the actual use of noobaa. You can check noobaa CR to see if the defaults have changed (e.g., the default for the DB is 0.5 CPU) and recommend increasing it if not. many times, this is not the root cause of the issue, but it can help in further diagnostic of the system by eliminating other issues.
How to rebuild Noobaa in ODF
This should be used carefully since it will result in a new empty system and cause loss of all existing data in Noobaa. It is useful when the customer is not using Noobaa, but it interferes with the ODF use (e.g.: upgrade issues, irrelevant alerts, etc.).
In some cases, this can be used as a last resort when there is no other way to restore the system. in that case, if there is a backup of noobaa it is possible to try and restore from backup (see backup and restore support case).
Backup and Restore

Debugging Postgres CPU issues
When the DB is maxing its CPU allocation, you can try using Postgres pg_stat_statements extension to check which queries take the most time to run. By also enabling query logging, you can identify the exact code that produce this query