Hello again,
I've tried the suggestion sent by Patricio Mora about a similar client ID
but they DON'T have the same ID. Here is the output of these commands on
'nsradmin':
E:\>nsradmin
NetWorker administration program.
Use the "help" command for help.
nsradmin> option hidden
Hidden display option turned on
Display options:
Dynamic: Off;
Hidden: On;
Resource ID: Off;
nsradmin> show name; client id
nsradmin> print type:NSR Client;name:zone.mydomain
name: zone.mydomain;
client id: \
2584a9f7-00000004-3e50e8a3-3e526096-045c0000-XXXXXXXX;
name: controlzone.mydomain;
client id: \
f3bc1866-00000004-3be7adc2-3be7adc1-03e10000-XXXXXXXX;
nsradmin> print type:NSR Client;name:controlzone.mydomain
name: controlzone.mydomain;
client id: \
f3bc1866-00000004-3be7adc2-3be7adc1-03e10000-XXXXXXXX;
As soy can see, when I query 'zone.mydomain' I get 2 different entries, 2
different names and 2 different client ID. When I query for
'controlzone.mydomain' I only get its entry. Why I don't get only the entry
for 'zone.mydomain' when querying for it?
I suppose that this problem with selecting a client in a query has bad
results when doing the backups, because when updating the attributes for
'zone.mydomain' we're changing those of 'controlzone.mydomain' too.
I've opened this morning a case with my Legato representative to see if this
is a bug of the 7.1.2 release.
You can test it in your 7.1.2 server doing the following:
- Open %WINDIR%\System32\drivers\etc\hosts on the Legato Server
- Add 2 fake machines like these:
192.168.10.10 fake fake.yourdomain
192.168.10.11 controlfake controlfake.yourdomain
- Create these 2 machines in Legato NetWorker
- Do the same 'nsradmin' commands that me and see the output. When querying
for 'fake.yourdomain' you get 2 entries (including
'controlfake.yourdomain'). If you query only for 'fake' without the domain
then you get only the correct one.
I don't why this is happening in 7.1.2 after the upgrade.
Any idea?
Thank you very much!
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] On Behalf Of Patricio Mora
> Sent: Monday, September 20, 2004 10:12 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: Re: [Networker] Problems with clients with a similar
> name, why? (zone vs controlzone)
>
>
> Excuse me please. Didn't pay ayttention on to whom was I
> sending email.
>
> Try on nsradmin :
> option hidden
> show name; client id
> print type:NSR Client;name:zone
> print type:NSR Client;name:controlzone
> And make sure the 'client ID' are trully different. Legato
> can get confused if in the past (even after having deleted
> and recreated the clients) both clients have been aliases, or
> a client rename has taken place.
>
>
> Patricio Mora wrote:
>
> >Prueba en nsradmin :
> >option hidden
> >show name; client id
> >print type:NSR Client;name:zone
> >print type:NSR Client;name:controlzone
> >Y comprueba que los client ID son en verdad distintos. He
> visto a legato
> >liarse si alguna vez han sido aliases o han cambiado de
> nombre los clientes.
> >
> >Manel Rodero wrote:
> >
> >
> >
> >>Hello again,
> >>
> >>More info. I've deleted the client definitions. Then
> 'nsradmin' command
> >>doesn't return any results. I've created first client and
> 'nsradmin' =
> >>outputs
> >>one client.
> >>
> >>After creating second one (controlzone) then a query for
> 'zone' returns =
> >>both
> >>clients. The problem is that an update for a client updates
> the other =
> >>client
> >>too. And, when doing a backup, NetWorker does some kind of
> query that
> >>matches both clients and then results in the error explained in my =
> >>previous
> >>messge.
> >>
> >>Any idea? If you have a server under Windows 2000 (version
> 7.1.2) can =
> >>you
> >>try to recreate this problem?
> >>
> >>If I query using FULL NAME then the query returns both
> clients (is an
> >>error). If I query using ONLY NAME then the query returns only one =
> >>client
> >>(ok). So I suppose that NetWorker is doing a matching
> starting from the =
> >>end
> >>of the string to the left. Why?
> >>
> >>nsradmin> show name;aliases;save set
> >>nsradmin> print type:NSR Client;name:zone
> >>
> >> name: zone.mydomain;
> >> save set: /, /data01, /data02, /data03,
> /data04, =
> >>/home,
> >> /home2, /logs, /usr, /var;
> >> aliases: zone, zone.mydomain;
> >>
> >>nsradmin> show name;aliases;save set
> >>nsradmin> print type:NSR Client;name:zone.mydomain
> >> name: controlzone.mydomain;
> >> save set: "C:\\", "E:\\", "F:\\", "SYSTEM DB:\\",
> >> "SYSTEM FILES:\\", "SYSTEM STATE:\\";
> >> aliases: controlzone, controlzone.mydomain;
> >>
> >> name: zone.mydomain;
> >> save set: /, /data01, /data02, /data03,
> /data04, =
> >>/home,
> >> /home2, /logs, /usr, /var;
> >> aliases: zone, zone.mydomain;
> >>
> >>Please, any help would be very appreciated!
> >>
> >>
> >>
> >>
> >>
> >>>-----Original Message-----
> >>>From: Legato NetWorker discussion=20
> >>>[mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] On Behalf Of Manel Rodero
> >>>Sent: Monday, September 20, 2004 9:02 AM
> >>>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> >>>Subject: [Networker] Problems with clients with a similar=20
> >>>name, why? (zone vs controlzone)
> >>>=20
> >>>=20
> >>>Hello,
> >>>=20
> >>>I'm finishing the process of upgrading all my clients to=20
> >>>7.1.2 (the server
> >>>was upgraded some weeks ago) but I have some problems with=20
> >>>clients that have
> >>>a similar name. Is something like Legato is confused!
> >>>=20
> >>>Sample clients with problems: zone and controlzone.
> >>>=20
> >>>During a backup we get messages like these ones (these
> have no sense):
> >>>=20
> >>>* zone:/ 3 retries attempted
> >>>* zone:/ save: File index error: permission denied, `root' on=20
> >>>`controlzone'
> >>>must have remote access privilege to client zone.
> >>>* zone:/ save: Cannot open save session with legato_srv
> >>>* zone:/data01 3 retries attempted
> >>>* zone:/data01 save: File index error: permission denied, `root' on
> >>>`controlzone' must have remote access privilege to client zone.
> >>>=20
> >>>If we use nsradmin to see the client definitions we can
> see that after
> >>>querying for this client, the second one is matched too! Why?
> >>>=20
> >>>nsradmin> show name;aliases;save set
> >>>nsradmin> print type:NSR Client;name:zone
> >>> name: controlzone;
> >>> save set: "C:\\", "E:\\", "F:\\",
> "SYSTEM DB:\\",
> >>> "SYSTEM FILES:\\", "SYSTEM STATE:\\";
> >>> aliases: controlzone;
> >>>=20
> >>> name: zone;
> >>> save set: /, /data01, /data02, /data03,=20
> >>>/data04, /home,
> >>> /home2, /logs, /usr, /var;
> >>> aliases: zone;
> >>>=20
> >>>Any idea about why 'controlzone' matches 'zone'?
> >>>=20
> >>>Thank you very much!
> >>>=20
> >>>_________________________________________________________________
> >>>=20
> >>>o o o Manel Rodero | LCFIB - UPC
> >>>o o o Systems Manager & HelpDesk | Campus Nord - Modul B6
> >>>o o o Laboratori de Calcul | Jordi Girona, 1-3
> >>>U P C Facultat Informatica Barcelona | 08034 Barcelona (Spain)
> >>> |
> >>>Mail : manel AT fib.upc DOT es | Tel: +00 34 93 401 6940
> >>>Web : http://www.fib.upc.es/~manel | Fax: +00 34 93 401 7040
> >>>_________________________________________________________________
> >>>=20
> >>>--
> >>>Note: To sign off this list, send a "signoff networker"=20
> >>>command via email
> >>>to listserv AT listmail.temple DOT edu or visit the list's Web site at
> >>>http://listmail.temple.edu/archives/networker.html where you can
> >>>also view and post messages to the list.
> >>>=
> >>>
> >>>
> >>>
> >>>
> >>=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*
> =3D*=3D*=3D*=3D=
> >>*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
> >>
> >>
> >>
> >>
> >>>=20
> >>>
> >>>
> >>>
> >>>
> >>--
> >>Note: To sign off this list, send a "signoff networker"
> command via email
> >>to listserv AT listmail.temple DOT edu or visit the list's Web site at
> >>http://listmail.temple.edu/archives/networker.html where you can
> >>also view and post messages to the list.
> >>=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*
> =3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >--
> >Note: To sign off this list, send a "signoff networker"
> command via email
> >to listserv AT listmail.temple DOT edu or visit the list's Web site at
> >http://listmail.temple.edu/archives/networker.html where you can
> >also view and post messages to the list.
> >=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
> >
> >
> >
> >
> >
>
> --
> Note: To sign off this list, send a "signoff networker"
> command via email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|