Hi @Kamil , thanks for the note!  Are you looking at the initial staging location, or where the Commserve is configured to save the file (within control Panel)?

I looked internally at our cases and the only mention of saving as a .bak file comes from backing up the database directly in SQL.

As per BOL, it should be a dmp, so any context you can provide should help:

https://documentation.commvault.com/11.24/essential/107613_performing_disaster_recovery_dr_backup.html

Thanks!

Hi @Mike Struening 

I was able to find the cause of the problem.

It turned out that DR_Backup itself was saving correctly, and the problem only occurred when generating logs by the selected "Scrub Log Files" option, which masked the CommServe database dump and changed the file extension to .bak.

An additional element recognizable for this situation is that "Masked" is added to the file name before the original CommServe name and the file name looks like this:

"Masked_CommServeName.bak"

Anyway, thank you for your reaction and help :)

Regards,
Kamil

That’s great!  thanks for sharing it (and marking the Best Answer )