[PCA 3.x] Loki data from a BRS (Backup and Recovery Service) backup contains no data even after M3.8 upgrade (Doc ID 3027004.1)

Last updated on SEPTEMBER 04, 2024

Applies to:

Symptoms

A BRS (Backup and Recovery Service) backup can be found in this location in PCA, on one of the management nodes : /nfs/shared_storage/backups

Inside the backups directory there will be other directories for each scheduled backup. An example of the contents of the /nfs/shared_storage/backups directoy is this one:

The fact that there was no loki data in the backup directories was reported in:
Bug 36086216 - PCA 3.0.2 BRS Daily Backup Cronjob Reports Failure for Loki

The cause of it was the fact that there was a transport message header issue. Problem is documented in the document below and already solved in 3.0.2-M3.8. Under normal situations, we should now see loki data in the backup directories on a system with M3.8 PCA version.
[ PCA 3.0.2 ] Daily Brs Backup Fails For Loki (Doc ID 2996914.1)

However, in some cases even after an upgrade to M3.8, the loki backup directory (/nfs/shared_storage/backups/ocid1.brs-job.AK*.hostname.*/loki) can still be empty.
This problem is reported in Bug 36522536 - Loki data from a BRS backup is empty (directory exists but the contents of it are empty).

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.