J Dodson wrote:
I would highly recommend that the moved mount path be marked as offline and set to not reference blocks. This will begin the process of aging off all of the blocks on that mount path so that it could eventually be retired.
After reading your reply, I have been checking and depending on the Feature Release used you can indeed use the option “Prevent data block references for new backups”.
Thanks @J Dodson 😀
This was introduced in V11 SP14.
Seems I need to stand corrected on my DDB seal statement.
Apologies for creating confusion by providing info related to old feature releases.
This would be a good option to phase out the mount path 😀
Instructions are here to prevent future block references:
https://documentation.commvault.com/11.24/expert/9376_disabling_write_operations_on_mount_path.html
Be aware that this still takes time as blocks on the mount path are referenced to by existing backups, these first need to be aged to delete existing reference points in the DDB before the path will be released by the DDB / CSDB and allowed to be deleted.