Unsolved

This post is more than 5 years old

21 Posts

9650

March 8th, 2010 15:00

Do you CLI ? Would you prefer not to...

All,

  Hello again. I have been reading serveral sources for NetWorker feedback and one theme keeps coming up...there are

several CLI tools for NetWorker that we all know and love...well okay we know them but "Love" is a strong word.

  My questions to you are:

  1. Which NetWorker CLI tools do you use most often (scanner, mminfo etc.) ?

  2. Would you prefer these tools be available in NMC ?

  As always I am looking for honest feedback here. I understand the frustrations of CLI's...that is why I gave them up years ago.

  You can respond here or use our usability alias at: networker_usability@emc.com

Cheers,

Skip Hanson

NetWorker Usability

10 Posts

June 4th, 2010 08:00

Hi Skip,

Happy to share..

1) is an instance of the Client resource in a group? (don't want to miss client that have temporarily been removed from their group....)

2) is an instance of the Client resource in the group INDEX_ONLY (runs daily at mid-day to sweep up the indexes on to tape)

3) Are the browse & retention policy set to "4_Weeks"?

4) Are "save operations: VSS:*=off" if the client type is "Windows NT Server on Intel"? (now obsolete, but still there!)

5) Does the "Owner Notification" attribute start with the name of our custom notification script?

If the code that enforces NetWorker's rules for attributes isn't too dirty, it might be possible to slip a custom filter (regex?) in front of it so that you'd get a "Local configuration rules won't allow this" message if you tried to enter something that had been "ruled out"

Interesting to see where that leads you!

From

Will

21 Posts

June 4th, 2010 11:00

Good morning. In 7.6 we added a Find capability to NMC. It will allow you to find items in tables. It is not a filtering mechanism yet but it will help you locate things faster. Check it out, I think it will help you in your day-to-day operations.

Some interesting features of find.

1. It can search across multiple tables. For example the new monitoring layout contains a number of panels. Find can locate all occurrences of given string

2. It has a Sort-selected function that groups everything it finds and then auto-scrolls them into view. This is particularly helpful when you find a lot of entries in a table but several of them are not in view.

Here some screen shots to get you started.

find_panel.png

Show/Hide Find panel

highlight_all.png

Highlight All

sort_selected.png

Sort Selected

15 Posts

June 24th, 2010 11:00

Hi Skip,

Another thought and area that i seem to find myself having to do regular scripts for, are the painful users who two days after a backup say - lets keep that for much longer than initially specified.

In our environment where all tapes are stored in specific retention pools, and there is a distinct lack of spending (and even space in the library), we need to make sure that all of our tapes rotate when we want them to.

Thus we have to spend lots of effort scripting - mminfo's to find the particular savesets to change browse/retention periods for - plug those into nsrmm.

Oh and then just to add to the fun, plug the same ssid's into nsrstage to put them into a more appropriate pool.  OK staging from tape to tape doesn't clear the initial saveset from the first tape, but at least it means that the first tape will expire when I expect it to, so I can reuse it shortly afterwards.

Easyish for some of us to script, and script it has to be - I can't imagine being able to put that into a gui.

Oh yes, and lots of communication back to the user in question to tell them to let us know about it in advance of the backup, as the change would take only a couple of minutes using the gui.

Felix

2 Intern

 • 

326 Posts

November 13th, 2011 15:00

hi guys

any cheat sheet for commonly used commands

334 Posts

November 14th, 2011 06:00

Hi Thierry,

Yes, there is a command reference guide.  Do you have access to Powerlink?  It is located here.

I hope this helps.

Allan

10 Posts

November 14th, 2011 06:00

Hi Therry,

In this area I'd politely term the EMC command reference guide as "concise"!

I've just downloaded and flicked through a rather more comprehensive guide to nsradmin (your main tool for automation) from here: (you need to provide an e-mail address)

http://nsrd.info/micromanuals.html

It seems to have a good run through of all the features and should give you a strong leg-up to being productive with your scripts.

Happy scripting.

Will

2 Intern

 • 

205 Posts

 • 

6 Points

November 18th, 2011 13:00

CLI is more or less mandatory to see correlations between for instance which tapedrives belong to which pool. Yes, you can see in every pool which tapedrive belongs to it in the GUI, but stumbling though a large number of pools to find out if drives from multiple systems are correctly assigned to the correct pools is much easier scripted. One of things I use it for is when deleting a jukebox device, to be sure I already removed it from all the pools it is assigned to. NW always only reported one of the pools it was assigned to, but not all. If you had to use GUI only, it would be cumbersome deleting dozens of devices for dozens of systems in a migration from one large library type to another (this environment is so large, and also uses much tapedrive sharing that we even reached the limit of 512 defined devices in the middle of the migration).

what would be helpfull indeed is to be able to create your own queries using NSR types and their values, being able to cross reference them to other NSR types/values. You know, like a real database (what pools does this drive belong to?, show me clients that are not in any of the index backups only savegroups?) And what's up with nsradmin that it shows entries when a wildcard did not find any hits? A big no-no in the real world of regular expressions.

And CLI does not mean that scripting capabilities was at the base of the conception of the CLI. scripting the creation of a jukebox using jbconfig comes to mind. We've build a script in the past that could do that with jbconfig under NW6 using multiple input files thus being able to create a jukebox with dozens of drives shared by dozens of systems. Its so easy for support or manuals to say "delete and recreate jukebox" but the practice is always much more complicated in envs with hundreds of defined tapedrives and dozens of pools. This specific item has been changed ofcourse in NW7 with a much more powerfull jbedit. Was just to make a point.

in addition of being able to do everything with CLI, it would also be helpfull to determine myself what the defaults should be that currently are hardcoded into NW. FSC/Fujitsu Networker has something in place for that with /nsr/res/defaults which allows certain variables to be set in a config file instead of doing that in the NW startup script. Don't know what else it can all set, but for EMC NW it would be great to be able to define your own defaults for for example client parallelism, blocksize 256 and CDI disabled for all tapedrives being created, instead of always having to change that in the gui. That's why people always fall back to CLI when they have to create many entries, being able to set/correct the right value.

I'm curious how anyone currently would prevent any backups from being started with GUI only. Disable all savegroups one at a time. with a script that's done in a few secs. And yes, I'm all for a GUI option to be able to suspend ALL backup activitity or that service mode of a tapedrive (or jukebox) is service mode as it used to be in the past, that I as admin can still load a tape into a drive and actually test it. But I'm drifting of now...

No Events found!

Top