Skip to main content
commvault.com commvault.com
Solved

Disk Library Issue: Faulty Mountpath and Data Recovery Concerns

  • February 1, 2024
  • 3 replies
  • 216 views
D
Novice
Forum|alt.badge.img+12

Hello community,

 

The disk library has 4 mountpaths connected via fiber channel. 

Unfortunately, one of these has hit a snag and is beyond repair, which might cause issue when browse/recover backup data.

While we could consider running a full backup for all servers tied to this lib, but it's not exactly our top choice.
 

Question:

How to pinpoint the affected clients on the faulty mount path and find the oldest backup history for these clients?  (do need open a support case and upload CS DB ?)

Once I've got that info, I can kick off fresh full backups just for those clients and also manually age data based on the backup history findings.

 

thanks

Best answer by Collin Harper

Hello @DanC 

In this situation you would have two options.

  1. Run a Data Verification for all non-deduped copies using the library & a DDB Data Verification for all deduplicated copies going to the library
  2. Delete the mount path which will logically age all of the associated data as well as automatically run DDB Verifications for all associated DDBs

Data Verification - https://documentation.commvault.com/2023e/expert/getting_started_with_data_verification.html

Performing a Data Verification Operation on Deduplicated Data - https://documentation.commvault.com/2023e/expert/performing_data_verification_operation_on_deduplicated_data.html

Deleting a Mount Path With Backup Data - https://documentation.commvault.com/2023e/expert/deleting_mount_path_with_backup_data_01.html

 

After either option you choose, you must then delete the jobs that Failed Verification.

  1. Viewing the Data Verification Status of the Backup Jobs - https://documentation.commvault.com/2023e/expert/viewing_data_verification_status_of_backup_jobs.html
  2. Delete a Job From a Copy - https://documentation.commvault.com/2023e/expert/delete_job_from_copy.html

 

Thank you,
Collin

    3 replies

    C
    Vaulter
    Forum|alt.badge.img+14
    • Collin HarperVaulter
    • Vaulter
    • Answer
    • February 1, 2024

    Hello @DanC 

    In this situation you would have two options.

    1. Run a Data Verification for all non-deduped copies using the library & a DDB Data Verification for all deduplicated copies going to the library
    2. Delete the mount path which will logically age all of the associated data as well as automatically run DDB Verifications for all associated DDBs

    Data Verification - https://documentation.commvault.com/2023e/expert/getting_started_with_data_verification.html

    Performing a Data Verification Operation on Deduplicated Data - https://documentation.commvault.com/2023e/expert/performing_data_verification_operation_on_deduplicated_data.html

    Deleting a Mount Path With Backup Data - https://documentation.commvault.com/2023e/expert/deleting_mount_path_with_backup_data_01.html

     

    After either option you choose, you must then delete the jobs that Failed Verification.

    1. Viewing the Data Verification Status of the Backup Jobs - https://documentation.commvault.com/2023e/expert/viewing_data_verification_status_of_backup_jobs.html
    2. Delete a Job From a Copy - https://documentation.commvault.com/2023e/expert/delete_job_from_copy.html

     

    Thank you,
    Collin

    D
    Novice
    Forum|alt.badge.img+12
    • DanCNovice
    • Author
    • Novice
    • February 1, 2024

     @Collin Harper 

    thank you very much

    i think i will have to start  manual full backup for clients tied to the library coz full schedule which typically runs on a monthly basis. Or Upon successful completion of the DDB verification, jobs with failed data blocks will automatically convert to full jobs when daily backup kick off ?

    C
    Vaulter
    Forum|alt.badge.img+14

    Hello @DanC 

    Once the jobs that failed verification are deleted and data aging has been run there is no need to run Full backups. We will just add new DDB records for things that were pruned due to the deletion.

     

    Thank you,

    Collin

    D
    Terms & ConditionsCookie settingsAccessibility statement