Author: Venkat Tudi <venkat.tudi AT GMAIL DOT COM>
Date: Tue, 29 Apr 2008 10:12:59 -0400
Hi, I am looking to find out how to use wild cards in NSRADMIN. for example . type: NSR client; group: oradbs-*; print -venkat To sign off this list, send email to listserv AT listserv.temple DOT edu
Venkat, as I'm preparing to upgrade to 7.4 sp2 (windows) I just found this in the new release notes (300-0050511_a04_elccnt_0.pdf): Querying with wildcards in the nsradmin program With NetWorker rel
There is a 'nsr_regex' man page. But the main thing is that you'll need to use regular expressions, not globs. So instead of '*' for zero or more characters, it would be '.*'. There's another trick.
Author: Venkat Tudi <venkat.tudi AT GMAIL DOT COM>
Date: Tue, 29 Apr 2008 12:07:59 -0400
Darren, I am totally not getting this. I am using 7.3.3. this is the querey i am typing Current query set No resources found for query: name: ntrs'*'; type: NSR client; I used it \, $, ^ all of them
Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>
Date: Tue, 29 Apr 2008 12:20:15 -0400
Venkat, The ability to use regex's is brand new in 7.4.2... since you are running 7.3.3, you can't use wildcards in your queries. It is not supported. Frank Current query set No resources found for q
The man page is in 7.3, so I don't know why it wouldn't be supported. In fact, I have no problems using regex expressions in nsradmin on my 6.1.3 machine. -- Darren Dunham ddunham AT taos DOT com Sen
I said earlier: The quotes are to show what should be entered, not that you'd use literal quotes in the query. In other words, replace '*' with '.*'. You didn't add the period (but you did add quotes
Hm.. strange stuff.. ..From the 7.4.2 windows release notes from powerlink - we upgraded today : With NetWorker release 7.4 Service Pack 2, regular expression queries have been enabled for the nsrad
Author: Peter Viertel <Peter.Viertel AT MACQUARIE DOT COM>
Date: Wed, 30 Apr 2008 11:09:15 +1000
The history of regexp in nsradmin in a nutshell: all versions before 7.3 supported using regexp's. Then in 7.3 they dropped support. Those of us with scripts that used them all rewrote our code, mour
Amazing. (I'm not using 7.3). Do you know when 'nsr_regex' was added as documentation? I don't see it on my 6.x boxes, but I do see it in the 7.3 documentation set. -- Darren Dunham ddunham AT taos D
Author: Peter Viertel <Peter.Viertel AT MACQUARIE DOT COM>
Date: Wed, 30 Apr 2008 12:34:54 +1000
When we discussed this on the list sometime about a year ago - most of us were pretty surprised it existed at as a feature in nsradmin too. I've just had a comparitive look at the various versions of
Author: Hrvoje Crvelin <hcrvelin AT GMAIL DOT COM>
Date: Wed, 30 Apr 2008 06:23:05 +0200
name: Indexed Archive; name: Indexed Archive Clone; That's fine because that's what you asked for. See following examples: name: Default; name: Indexed Archive Clone; name: Default Clone; name: Inde
Author: Hrvoje Crvelin <hcrvelin AT GMAIL DOT COM>
Date: Wed, 30 Apr 2008 06:27:44 +0200
Actually, that would be "<anything before>de<anything after>". It is just like grep where last character may also be ignored :) name: Indexed Archive; name: Indexed Archive Clone; That's fine because