Skip to main content
Question

Disk library corrupted

  • September 22, 2025
  • 1 reply
  • 45 views

Manics.mca
Forum|alt.badge.img+4

Dear Team,

 

We are currently running our CommServe (CS) and Media Agent (MA) on the same physical server with RAID-5 disks. Recently, we encountered an issue with the disk library where the mount path went offline due to data corruption. As a result, we are unable to access the mount path drive.

The affected hard disk has been removed and handed over to a third-party company for data recovery. The disk contains critical data such as email archives, file system backups, SQL, Oracle, and VM backups. Based on their assessment, the recovery process may take one to two weeks, and in some cases, it could extend beyond a month.

In the meantime, we need to ensure that backups for our critical servers continue without disruption. Could you please provide us with best practices and recommendations on how to reconfigure the backup environment during this period?

Additionally, the operating system on the server has also become corrupted. We would appreciate your guidance on the necessary steps to rebuild or reconfigure the system so we can proceed further.

Thank you for your support.

 

Regards,

Mani D

 

 

 

 

 

 

1 reply

Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • September 22, 2025

Assuming you have a DR backup of the Commserve DB.

In short I would:

Configure a server (same or new) with the necessary (CS/MA) packages and import the DR backup during installation.

Now the base config is back, but the disklibrary will need a new configuration.

As your corrupted disklibrary is expected to be back in a month, you need storage and data path configurations which is different then the currently corrupted one.

Once the disklibrary is configured you can create new primary copies for the storage policies pointing to the new disklibrary. DO NOT reconfigure data paths on the existing storage policy copies as this storage is coming back!

Then test backup and recovery, if ok then enable backup in general.

Also check if secondary, tertiary copies etc have a static source location defined, you will need to change it to the new storage if it was pointing to the corrupt storage.