Skip to main content
commvault.com commvault.com
Solved

Failed to open Magnetic Config File for writing Mount Path information for Path PATH

  • October 25, 2022
  • 3 replies
  • 261 views
E
Byte
Forum|alt.badge.img+10

A closer look at CVMA.log showed me the following error 

Failed to open Magnetic Config File for writing Mount Path information for Path [/cvault/hua/nfs/xyz_02/dat\Y66R1O_08.08.2022_13.02], ID [136], errCode [13], errorString [Failed to open file /cvault/hua/nfs/xyz_02/dat/Y66R1O_08.08.2022_13.02/CV_MAGNETIC/MountPathConfigs]. Continuing anyway

 

Commserve: 11.26.3

MA server: 11.26.3 (Linux with CVLT Ransomware protection enabled)

How to fix this issue? 

 

I tried to pause protection and wait some time but after that time I got a new error record at CVMA.log again. 

 

[root@cvault-ma-02 2022.10.25-09:16:38 ]
[ /opt/commvault/MediaAgent64 ] ./cvsecurity.py pause_protection
OS version CentOS Linux release 7.9.2009 (Core)
2022-10-25 09:16:42,432 - __main__ - INFO - start pause_protection
2022-10-25 09:16:42,439 - __main__ - INFO - exiting
[root@cvault-ma-02 2022.10.25-09:16:42 ]
 

[root@cvault-ma-02 2022.10.25-09:20:24 ]
[ /opt/commvault/MediaAgent64 ] sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   permissive
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      31
 

 

Best answer by Collin Harper

Hello @Eduardo Braga 

This Mount Path Config message is usually white noise that we see from time to time.

Regarding Ransomware Protection, it would be best to update to Maintenance Release 32 or higher seeing as you are on Feature Release 26. We do have several fixes out for Ransomware Protection issues. You can confirm if its causing an issue via the “dlpalerts.log” on the Media Agent but regardless, it would be best to patch even if you don’t see any recent alerts in that log.

 

Thank you,

Collin

View original
Did this answer your question?

Mike Struening
Vaulter
Forum|alt.badge.img+23

Hi @Eduardo Braga !

This might not be an issue with Ransomware Protection.

Can you confirm the actual mount path is available via the Media Agent Operating System first?

It could also be the mount path labels, though first step is to ensure the OS itself can see those mount paths.

https://www.linkedin.com/in/michael-struening
E
Byte
Forum|alt.badge.img+10
Mike Struening wrote:

Hi @Eduardo Braga !

This might not be an issue with Ransomware Protection.

Can you confirm the actual mount path is available via the Media Agent Operating System first?

It could also be the mount path labels, though first step is to ensure the OS itself can see those mount paths.

Hi, Mike, Thank you, You are an awesome friend.

Yes. It’s available via the MA OS first. 

 

 

 

C
Vaulter
Forum|alt.badge.img+14

Hello @Eduardo Braga 

This Mount Path Config message is usually white noise that we see from time to time.

Regarding Ransomware Protection, it would be best to update to Maintenance Release 32 or higher seeing as you are on Feature Release 26. We do have several fixes out for Ransomware Protection issues. You can confirm if its causing an issue via the “dlpalerts.log” on the Media Agent but regardless, it would be best to patch even if you don’t see any recent alerts in that log.

 

Thank you,

Collin

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings