Migration of data one storage to the other using commvault

Hi ​@Mubaraq ,

Considering the failure of “Multiple disk”, there is an uncertainty about the state of all data chunks, I believe that using the "Move mount" path isn't a viable option.

Instead, I recommend we proceed with a full DDB verification first. After ensuring the integrity of the data, we can then run an Auxcopy to the new storage pool. During this process, we should skip the "Data verification" failed job and subsequently promote the secondary storage to primary.

Please note that the duration of this entire migration will depend on a few key factors:
- Read speed from the Source Storage
- DDB Disk performance
- Write speed to the new storage

The other option is 

1. **Run Full DDB Verification**: This will help us break the corruption chain that we are currently experiencing.

2. **Enable “Prevent Data Block References for New Backup” on the Old Mount Path**: This action will help us disable any write operations that may be contributing to the problem. You can find more details on this process [here](https://documentation.commvault.com/11.40/expert/disabling_write_operations_on_mount_path.html).

3. **Add New Mount Path**: On the existing library, we need to add a new mount path from the new storage which will allow us to continue backup operations without further issues.

4. **Delete Old Mount Path**: Once the old jobs have expired and all the volumes associated with that mount path have aged off, we can proceed to delete the old mount path.

Regards,

Wasim

Hello, ​@Wasim 

Thank you so much for your response.

I have done further checks on the mount paths and I can already pinpoint the online mount paths and offline mount paths. We will be adding the mount path to existing libraries and move the previous mount paths to the new one.

We will be focusing on online mount paths only, hence the suggestion of move mount paths.

This kind of give visibility into the data we are able to move and we can track what has been moved.

What do you think?

Hi ​@Mubaraq,

Since the library has mixed "offline and online" mount paths, and you would like to proceed with moving data only from the online mount path as planned. 

However, I would like to remind you that in order to update the CS DB regarding the corruption, a full DDB verification is mandatory. If there are any offline mount paths, the full DDB verification process will fail. 

To mitigate this issue, we should create a dummy path, label the mount path, and enable the "Prevent Data Block References for New Backup" option before initiating the full DDB verification.

I suggest that we raise a Commvault support ticket to help us achieve this smoothly. 

Regards,

Wasim

Dear ​@Wasim 

We will run the ddb verification and check with support to advise, where needed.

Thank you for the help, thus far. Will update.