Background:
Running on Commvault 11.28.x
I have a folder that basically like this that is needing to have all files and folders in it backed up and its not backing up anything, even though there are files/folders inside it.
The path is: \\folder1\folder2\Some Folder [1010-00909]
NOTE: This folder is a Windows file share, not *nix
Currently I have this in the ‘Content’ configuration in the subclient, which just has a \ at the end of the path: \folder1\folder2\Some Folder [1010-00909]\
Question 1: I was under the impression that you had to put a ‘\’ at the end of a file share path and this would cause all files/folders to be backed up inside the folder. Looking at the online docs: Wildcards for the Windows File System Agent (commvault.com) It does not list using ‘\' at the end, but does show (in a roundabout way) that you need to use 3 asterisks ‘***’ at the end of a folder to backup up all files/folders? Is this ‘the correct way” to so this or is using ‘\’ at the end ok (maybe this is deprecated)? We have been using ‘\’ at the end of several of these and it appears to be working… but maybe there is a caveat to doing it this way?
Question 2: The backup probably is having an issue with the [1010-00909] in the folder name. Looking at the docs (link above) it seems to indicate that the way to handle the []’s is specifying a wildcard character to escape each [], which I have chosen the tilde ‘~’ character:
<P:e=~>\\folder1\folder2\Some Folder ~[1010-00909~]\
If I choose this, Commvault will not accept it as input and says its invalid. I cannot add this path to the content as the java UI refuses to save it.
What is the proper syntax to handle the []s? is the dash also causing an issue (as data inside [] is handled in special ways apparently)?
