Hi Tim,
Basically, the problem with the right part of the clients matching a query
in 'nsradmin' appeared in our environment suddenly (after upgrading from
6.1.3 to 7.1.2). Our change scripts (basically for aliases and savesets for
a machine) were created when using our first Legato version 5.x and they
worked as expected (i.e. searching for "client1.domain" doesn't update
"controlclient1.domain").
When we found this problem (in september'2004) we opened a case with Legato
throught our HP maintenance contract. We sent tests and more tests until
Legato assumed the problem and the sent us a message and a new
'nsradmin.exe'. The message was:
BEGIN
3114367 clients that have a similar name
Hello X,
I've got response from engineering that it will not be possible to provide a
complete solution or patch fix in short term. The cause for the problem
reported is that deep in core NetWorker structure not being able to be
changed in a patch fix.
However a quick fix of nsradmin.exe has been provided doing a correct
selection to the client name. The limitation: when more than one client
resource for the same client, only the first match is reported or selected.
This means a unique selection will have to be made already resulting in a
unique selection. For example by adding group or save set to the selection.
Please let me know about your experiences using this.
Depending on this Legato engineering will decide about the next steps.
Please feel free to contact me if you have any question or concern.
Regards,
Legato Support
END
But, this new patch doesn't worked for us because of its limitations (only
the first client alphabetically was selected). For example, an incorrect
client selected:
E:\downloads>nsradmin_new.exe
NetWorker administration program.
Use the "help" command for help.
nsradmin_new> option hidden
Hidden display option turned on
Display options:
Dynamic: Off;
Hidden: On;
Resource ID: Off;
nsradmin_new> option resource id
Resource ID display option turned on
Display options:
Dynamic: Off;
Hidden: On;
Resource ID: On;
nsradmin_new> show name;aliases;client id;browse policy;retention
policy;group;save set;hostname;resource identifier
nsradmin_new> print type:NSR Client;name:foobar.ourdomain
name: controlfoobar.ourdomain;
client id: \
349e15c5-00000004-4190d4e6-4190d537-1dc50000-93532908;
browse policy: LCFIB Normal;
retention policy: LCFIB Normal;
group: LCFIB-Normal;
save set: "C:\\";
aliases: controlfoobar, controlfoobar.ourdomain;
hostname: legatoserver.ourdomain;
resource identifier: 47.0.68.6.212.153.119.65.X.Y.Z.W(5);
Or the "old problem" when 2 similar clients selected:
nsradmin_new> print type:NSR Client;name:foobar.ourdomain;group:LCFIB-Normal
name: controlfoobar.ourdomain;
client id: \
349e15c5-00000004-4190d4e6-4190d537-1dc50000-93532908;
browse policy: LCFIB Normal;
retention policy: LCFIB Normal;
group: LCFIB-Normal;
save set: "C:\\";
aliases: controlfoobar, controlfoobar.ourdomain;
hostname: legatoserver.ourdomain;
resource identifier: 47.0.68.6.212.153.119.65.X.Y.Z.W(5);
nsradmin_new> print type:NSR
Client;name:foobar.ourdomain;group:LCFIB-Historicos
name: foobar.ourdomain;
client id: \
3424e7a3-00000004-4190d4e5-4190d4e4-1dc40000-93532908;
browse policy: LCFIB Historicos;
retention policy: LCFIB Historicos;
group: LCFIB-Historicos;
save set: /, /var;
aliases: foobar, foobar.ourdomain;
hostname: legatoserver.ourdomain;
resource identifier: 46.0.68.6.212.153.119.65.X.Y.Z.W(4);
Annonying? Yes but ...
Sorry again Tim for this little discussion derivated from another question.
See you.
-----Original Message-----
From: Legato NetWorker discussion
[mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Tim Mooney
Sent: Tuesday, April 05, 2005 7:52 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] context searching in 7.1.3 nwadmin
In regard to: RE: [Networker] context searching in 7.1.3
nwadmin, Joel...:
I'm talking about not being able to hit "a" and have it jump to the
first entry starting with an "a" in the "Clients"/"Groups"/"Index"
windows of the 7.1.3 windows GUI. This is a lame bug... has anyone
reported it to Legato? I'm a Sun user, so I'm not sure how
effective my
complaints will be.
I understand what you're talking about, and I agree that it seems like
an unfortunate regression. What I was commenting on is the phenomenon
that Manel and Davina mentioned in `nsradmin'. That
particular phenomenon
is not new and is working as designed and documented.
Did anyone test this interface before it was released?!?! Such an
obvious bug!!!
I think not being able to recover from >2 GB savesets done
from a pre v6
client is a much worse bug.
That too made it out the door.
Tim
--
Tim Mooney
mooney < at > dogbert.cc.ndsu.NoDak.edu
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
--
Note: To sign off this list, send a "signoff networker"
command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu
Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu
