I need a sanity check, here. I've got this INCLUDE list on a policy for a series of NFS mounts: INCLUDE NEW_STREAM INCLUDE /etc/passwd INCLUDE /gollum/vol/[qr]* INCLUDE /gollum/vol/[0-9]* INCLUDE /go
If I can reply to my own posting, I pulled the [A-Z] reference and it just backed up the expected filesystems. Could it be that NB is doing a case-insensitive match? Hmm. Too much time in bed with Mi
Author: "Bobby Williams" <bobbyrjw AT comcast DOT net>
Date: Tue, 5 Feb 2008 06:00:03 -0500
Where are you putting this include list? I think that you are using syntax for your data mover, not NetBackup. Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 --Original
I had the lower-case letters covered in other NEW_STREAM sections. The [A-Z]* part was just to cover if somebody made a new volume with a capital letter starting the name. What I did to compensate fo
That's part of the policy setup, the bpplinclude setup. It should use standard unix file matching patterns. Where are you putting this include list? I think that you are using syntax for your data mo
Not sure of the context you intended, but AFAIK, the pattern-matching/wildcarding characters in selection lists, exclude lists and include lists are interpreted by the client, running on the client