They use it.
Rename the .nsr_cluster file and start save, then spy on it with the
"truss"-command. You will see, that there are a real bunch of "cmgetconf"
und "cmviecl". Than have a look at your syslog.log and there also will be
hundreds of "cmgetconf". This is also a performance problem -- use the
.nsrcluster an saving will start much faster, rename it and save will start
only after several minutes of collecting information with "cmgetconf" and
"cmviewcl".
To touch a .nsr_cluster file won't solve any problem, the file has to be
filed with real information.
Klaus
-----Ursprüngliche Nachricht-----
Von: VERHAEGHE Koen (BMB) [mailto:Koen.VERHAEGHE AT PROXIMUS DOT NET]
Gesendet: Mittwoch, 18. Juni 2003 16:26
An: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Betreff: Re: [Networker] Networker and MC/SG config problem
Thanks Klaus. I'll give that a try.
However, this still needs manual edits in the .nsr_cluster file. Networker
claims to be cluster aware, but apparently it's just to sell a license. The
manually keeping track of added file systems is not different than the
veritas clusters we have, where we list the clustered file systems in "save
set" and use "save -c <virtual client>, but at least they don't need a
cluster license (for 6.1.x)...
Why doesn't legato use cmgetconf (rhetorical question) ?
I also read somewhere on the HP site that just touch a .nsr_cluster file
would be sufficient ...
-----Original Message-----
From: Grohal Klaus [mailto:klaus.grohal AT siemens DOT com]
Sent: Wednesday, June 18, 2003 4:07 PM
To: 'Legato NetWorker discussion'; VERHAEGHE Koen (BMB)
Subject: AW: [Networker] Networker and MC/SG config problem
Hi,
you are on the right way. Fill in the saveset of the clients (phys. and
virt.)the value "All". Create the .nsr_cluster file in the way like: <virt.
node:virt-ip:filesystem1:filesystem2>. Don't create pathownerignore. The
.nsr_cluster only shows results, if saveset is "All" and there is no
pathownerignore. We're working with this configuration on over 30 clients
under HP-UX 11.0 and Networker 6.1.3 with a Linux server.
regards
Klaus
-----Ursprüngliche Nachricht-----
Von: VERHAEGHE Koen (BMB) [mailto:Koen.VERHAEGHE AT PROXIMUS DOT NET]
Gesendet: Mittwoch, 18. Juni 2003 15:28
An: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Betreff: [Networker] Networker and MC/SG config problem
Sorry, was sent with the wrong title
-----Original Message-----
From: VERHAEGHE Koen (BMB)
Sent: Wednesday, June 18, 2003 3:26 PM
To: 'Legato NetWorker discussion'
Subject: RE: [Networker] install problem
Dears,
Can someone clarify the following for me:
Facts : Networker 6.1.1 on Solaris 8 server: Networker 6.1.1 on HP 11.0
client; Clients have MC/SG
We have 2 physical nodes and 2 virtual nodes configured in MC/Serviceguard.
Networker detects this since we need a cluster license. However, I'm trying
to get Networker to detect also the filesystems that are actually attached
to the virtual nodes automatically. Now have need to manually type them in
the "save set" attribute, with the danger that, should someone change the
cluster config and add a filesystem (different department...), we would not
be backing up these.
I thought that it would be as simple as putting All as "save set" ... I've
been testing with .pathowenignore and .nsr_cluster files, but can't get it
to work.
Can someone help me. There is little of no info on the Legato or the HP web.
Cheers
Koen
**** DISCLAIMER ****
"This e-mail and any attachment thereto may contain information which is
confidential and/or protected by intellectual property rights and are
intended for the sole use of the recipient(s) named above.
Any use of the information contained herein (including, but not limited to,
total or partial reproduction, communication or distribution in any form) by
other persons than the designated recipient(s) is prohibited.
If you have received this e-mail in error, please notify the sender either
by telephone or by e-mail and delete the material from any computer".
Thank you for your cooperation.
For further information about Proximus mobile phone services please see our
website at http://www.proximus.be or refer to any Proximus agent.
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
