PBM restore physical backup with featureCompatibilityVersion

Description:

Hello team, I am facing the issue restoring the physical backup for MongoDB 5.0.26 where featureCompatibilityVersion parameter is set to “4.4” As I understand during the restore process we get a fresh database where this parameter is not set, Do we have some workaround to fix this issue?

Version:

EKS 1.30
Percona MongoDB operator 1.16.0 installed via Helm chart
PBM agent 2.4.1
MongoDB 5.0.26

Logs:

in logs I see this Fatal messages
{“t”:{“$date”:“2024-05-28T12:10:46.187+00:00”},“s”:“W”, “c”:“STORAGE”, “id”:29054, “ctx”:“initandlisten”,“msg”:“EncryptionKeyDB: Failed to start up WiredTiger under any compatibility version.”}
{“t”:{“$date”:“2024-05-28T12:10:46.187+00:00”},“s”:“F”, “c”:“-”, “id”:23089, “ctx”:“initandlisten”,“msg”:“Fatal assertion”,“attr”:{“msgid”:28559,“file”:“src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp”,“line”:177}}
{“t”:{“$date”:“2024-05-28T12:10:46.187+00:00”},“s”:“F”, “c”:“-”, “id”:23090, “ctx”:“initandlisten”,“msg”:“\n\n***aborting after fassert() failure\n\n”}
{“t”:{“$date”:“2024-05-28T12:10:46.187+00:00”},“s”:“F”, “c”:“CONTROL”, “id”:6384300, “ctx”:“initandlisten”,“msg”:“Writing fatal message”,“attr”:{“message”:“Got signal: 6 (Aborted).\n”}}
[If applicable, include any relevant log files or error messages]

Expected Result:

Actual Result:

Additional Information: