Skip to main content
Solved

The media side mounted is write-protected


Forum|alt.badge.img+1

Hi

I'm not an expert user.

After the automatic upgrade job to version 11.28.8, the backup jobs failes with the following error:
Error Code: [62:308] Description: The media side mounted is write-protected. Source: backupserver, Process: cvd
Status: Mount Error
Library Name: AutoDiskLib
Drivepool: DrivePool(backupserver)1
Drive: Folder_03.28.2019_11.26
Media label: CV_MAGNETIC
Failure Reason: The media side mounted is write-protected.

Under the library all mount paths have Read/Write Access
Properties for the mount path under Allocation policies are marked Maximum Allowed Writers.

Tried manually upgrade to version 10.28.10, but nothing changed.

This is a disk library, not tape. The library is about 89% full, but still have about 7,5 TB free space on the given mount path.

 

How to enable read write?

 

Best answer by NVFD411

@JanErik - Sorry for the delay.  Try disabling and re-enabling ransomware protection, then rerun the backups. 

View original
Did this answer your question?

8 replies

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

Thanks for the post, @JanErik !  this community is a great place for non-experts (and experts)!

That’s definitely an odd message since it’s not a tape library.  It could be a simple matter of resharing the drives, though let’s start with the log files.

Can you check the cvd.log on backupserver, around the time frame you saw this error, and copy them here?


Forum|alt.badge.img+7
  • Vaulter
  • 62 replies
  • July 12, 2022

@JanErik -  Just to add to @Mike Struening request. 

 

Would you share some details on the following:

  • Are all backups jobs failing? 
  • Are the media agents Windows/Linux
  • Provide snippets from DLP.log as well

Forum|alt.badge.img+1
  • Author
  • Bit
  • 2 replies
  • July 13, 2022

Thanks for your reply.

Attached is copies from one of the failed jobs, cvd.log and dlp.log. All jobs going to the existing mount paths was the same, so all jobs is failing. I managed to do a workaround by simply create new mount paths to the same disk, but to a different folder, and then marked the old mount paths with disable mount path for new data under allocation policy. Then the backup went ok.

Media Agents are Windows Server 2016. There are two media agents.

 


Forum|alt.badge.img+7
  • Vaulter
  • 62 replies
  • Answer
  • July 14, 2022

@JanErik - Sorry for the delay.  Try disabling and re-enabling ransomware protection, then rerun the backups. 


Forum|alt.badge.img+1
  • Author
  • Bit
  • 2 replies
  • July 18, 2022

@NVFD411 - Thank you very much, that solved the issue.


Lukas3D
Byte
Forum|alt.badge.img+6
  • Byte
  • 61 replies
  • April 30, 2023

In my case it was at different layer, disk library mounted as disk drive was in read-only mode at OS side. After putting disk offline and online it went fine (reboot wasn’t enough).


Forum|alt.badge.img
  • Bit
  • 1 reply
  • November 6, 2024

We are running v11.28.126 and also having this issue.  Any assistance from the brains trust would be appreciated.


Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Vaulter
  • 1235 replies
  • November 9, 2024
SPman wrote:

We are running v11.28.126 and also having this issue.  Any assistance from the brains trust would be appreciated.

I’ve seen this before when folks thin provision mount paths. The OS side looks like there is space available but the underlying SAN sets the volume to read only because its actually full.

Can you copy files to your mountpath?


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