Adding new mount points

Almost, create mount path on A (1), then when you are ready, share it (2) then use ‘Share mount path’ and add B (5), see here - https://documentation.commvault.com/11.40/commcell-console/sharing_mount_path.html

For second question: For the L:\ example (a new NAS presented disk)...Any input/ideas/recommendations about making a folder in L:\ like CV_DATA and “windows sharing” just that folder?  … or is that not really necessary (or desired) and therefore jsut “windows sharing” L:\ as “sharenameL” and then using that UNC share (\\server\sharenameL) as the new mount point is ok/normal/etc

Yes, create a folder under the drive and share that

sorry, lots of questions ;). I have always extended existing mount paths, never had to create any new ones…

I’ve created the paths (path points to L:\CVDATA on the server), and when I added the path it “auto shared” with the correct media agent I was going to share with.  The “auto share” set up access as “read”, and the “transport” is “Data Server - IP”.

I’ve read somewhere “Dataserver - IP” is not good to use/have in production? I’m not sure if having the shared path as “read” is good or want “read/write”

question: so it looks like I need to:

1. go to the server and share the folder via windows using a domain account

2. edit the existing auto ‘shared”  path ( er… controller? in the java UI) to be “Transport Type” to be “regular”
3. Should I edit the “Access” to be read/write?  It appears this is just a “choice”, I assume based  on “if you want to share it that way”.   I assume having it shared as read/write will more evenly balance the storage used, and “read only” will be more performance based?

update: I’ve been reading up, arlie wrangling, etc… it appears the “only real answer one probably wants to aim for” is:

• Update the auto configured “share” using “read” access and “Dataserver - IP” to use a windows network share (that you have to set up) and then you can choose to leave as “read” or change to “read/write”. meaning:  “Transport Type” to be “regular” and “read/write” is really what one probably wants to use nowadays. “read” being another option

Because: (per Arlie searches)

• “Configuring DataServer-IP for read/write access is not recommended for production workloads”. .but using “DataServer-IP” for read only is ok...BUT: the “DataServer - IP” config is deprecated as of 11.42 CU Pack 120. So basically; never use it (will be enforced as of 11.42 CU Pack 120) and (probably) try to migrate away from using it if yo have it

Some links: 

Commvault Customer Support Portal - Articles - Article Details

Sharing a Mount Path Using DataServer-IP

Deprecation Notice for DataServer-IP ← only seems to be in the Saas Docs though?

• Also: “admin shares” are deprecated as of 11.40 and are also enforced to not be able to use them (just a side note, also completely disable admin sharing on media agents too: Removing Administrative Shares from Windows Servers)

in summary: so one basically “really really should” share the mount point folder/path at the OS level and use that to share at all…I assume “once you go above 11.42 CU Pack 120” in terms of “new mount path setups. 

Correct, share local mount paths (like DAS disk, SAN LUNs) only as ‘read only’ as you don’t want MAs write backup data across the network to another MAs ‘local’ disk (it’s technically OK, just not efficient) and switch to CIFS share. If you use local storage it’s not really ‘resilient’, doesn’t matter how many MAs you have. If one of the MAs is down, due to deduplication it’s very unlikely you can restore anything (backups will still work, just cause storage/DDB blow out) that’s why up to date secondary copies are important. 
If you use shared storage, like file shares from a NAS, cloud storage, etc. share it as R/W amongst the MAs.