Veritas-bu

Re: [Veritas-bu] install client with ssh

2008-04-17 13:24:37
Subject: Re: [Veritas-bu] install client with ssh
From: "Nardello, John" <john.nardello AT wamu DOT net>
To: <dave.markham AT fjserv DOT net>, <Mark.Donaldson AT cexp DOT com>
Date: Thu, 17 Apr 2008 10:02:41 -0700
1)      Do a normal "/usr/openv/netbackup/bin/install_client_files ftp
<client>" to some Solaris 10 box in your environment. 
2)      On the client you'll now have a /tmp/bp directory on the client
with all the needed files and stuff you need to automate future
installs. 
3)      Hack the /tmp/bp/bin/client_config script to do automatic
configuration of the CLIENT_NAME, REQUIRED_INTERFACE, other desired
bp.conf entries, exclude_list, etc. 
4)      Copy in any additional files needed to support your hacking
(i.e. exclude_list file, etc) to /tmp/bp
4)      tar up /tmp/bp and then you can use your favorite method to move
the tarball onto any client that needs to be installed, untar it, then
just run your hacked client_config script to automatically do the
install and client configuration. 

I will say you have to re-hack the client_config script at each new
NetBackup version, or at least check it to make sure they haven't
added/removed any files to/from the install, but otherwise it's been
working pretty well here. I now have install tarballs I can get loaded
onto any of our UNIX clients and Joe-SA can run a single command to do
all the needed configuration. And my favorite part, I didn't have to
start from scratch. =) 

- John Nardello


-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Dave
Markham
Sent: Thursday, April 17, 2008 8:36 AM
To: Mark.Donaldson AT cexp DOT com
Cc: Amado.Gramajo AT us.icap DOT com; richard.hale AT pegs DOT com;
veritas-bu AT mailman.eng.auburn DOT edu; jlightner AT water DOT com
Subject: Re: [Veritas-bu] install client with ssh

Yeah good call, and i have done that before. Problem is i want to 
install solaris 10 clients and i'd have to script all the service stuff 
and im not totally up on solaris10 as yet ( i know i know i should be ).

I have had some good responses and a couple of scripts passed to me so 
thanks guys and i'm sure ill get it going

D

Mark.Donaldson AT cexp DOT com wrote:
> Since it's solaris, it's really easy to just copy it from another
> working client, too.
>
> Grab the entire /usr/openv directory in a tarball and just untar it on
> the new machine.  Change the client name & other info in bp.conf.
Grab
> the "bp" entries from /etc/services & /etc/inetd.conf and add them to
> the other client.  HUP the inetd daemon.  It should work.  Verify the
> bpcd port is listening correctly with "netstat -a | grep bpcd".  You
> should see inetd listening to the bpcd port.
>
> Other than that, just finding the install script and replacing "rsh"
> with "ssh" works fine, too.  Of course, the trust relationship needs
to
> be setup first (and the first contact made & host key accepted and all
> that other normal prep work.)
>
> -M 
>
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Dave
> Markham
> Sent: Thursday, April 17, 2008 6:48 AM
> To: richard.hale AT pegs DOT com
> Cc: Amado Gramajo; veritas-bu AT mailman.eng.auburn DOT edu; Jeff Lightner
> Subject: Re: [Veritas-bu] install client with ssh
>
> Thanks dude, ill give the rsh rename a go. I know i tried this on
older 
> versions and it didnt seem to work but Im happy editing scripts so
will 
> set keys up and try.
>
> To answer some other replies :-
>
> Im not on v 6.5 and being in a large company with stupid rules and 
> customer change controls and accreditations etc i cant upgrade to 6.5
> soon.
> Im remotely managing hundreds of clients in a datacenter and putting a

> CD into a new client just is not feasible.
>
> There is nothing under the /usr/openv/netbackup/client/Solaris/ tree 
> which has sftp or ssh in it from the server install and so i assume 
> people who have these scripts have created them.
>
> I dont see any sftp or ssh install scripts under Linux or BSD client 
> directories either.
>
> If someone does have them would they mind mailing me a copy and i
could 
> then try and hack the Solaris one.
>
> Weird thing is i cant see why it doesnt work globally replacing ftp
with
>
> sftp as when i run a diff on my v5 scripts i cant see that much else
has
>
> changed.
>
> Cheers
>
>
> richard.hale AT pegs DOT com wrote:
>   
>> If you are willing to set up shared ssh keys between hosts you can 
>> modify the
/usr/openv/netbackup/client/Solaris/Solaris9/install_client
>>     
>
>   
>> script.  There is an install_client script for each OS version.  A 
>> crude hack is to replace what Netbackup discovers for RSH and RCP
with
>>     
>
>   
>> SSH and SCP.  If you don't want to modify the scripts, you could 
>> rename RSH and RCP and replace them with a link to SSH and SCP.  We 
>> don't use "R" commands anymore so that works for us. 
>>  
>>  
>> install_client:
>>  
>> <...snip....>
>> # Find the rsh and rcp commands
>> if [ -x /usr/net/rsh ] ; then
>>         RSH=/usr/net/rsh
>> elif [ -x /usr/bin/remsh ] ; then
>>         RSH=/usr/bin/remsh
>> elif [ -x /usr/bin/resh ] ; then
>>         RSH=/usr/bin/resh
>> elif [ -x /usr/bin/rsh ] ; then
>>         RSH=/usr/bin/rsh
>> elif [ -x /usr/bsd/rsh ] ; then
>>         RSH=/usr/bsd/rsh
>> elif [ -x /usr/ucb/rsh ] ; then
>>         RSH=/usr/ucb/rsh
>> else
>>         /bin/echo Cannot find rsh command
>>         exit 1
>> fi
>>  
>> if [ -x /usr/ucb/rcp ] ; then
>>         RCP=/usr/ucb/rcp
>> elif [ -x /usr/bsd/rcp ] ; then
>>         RCP=/usr/bsd/rcp
>> elif [ -x /usr/bin/rcp ] ; then
>>         RCP=/usr/bin/rcp
>> else
>>         /bin/echo Cannot find rcp command
>>         exit 1
>> fi
>>  
>> # Fix rsh and rcp commands --rhale.
>> RSH=/usr/local/bin/ssh
>> RCP=/usr/local/bin/scp
>>  
>> <...snip...>
>>  
>> As long as the shared host keys are setup, this will work for
installs
>>     
>
>   
>> from the gui and command line.  I have only used this for unix hosts 
>> so you are on your own for windows.
>>  
>> Richard H.
>>  
>>
>>     ----- Original Message -----
>>     *From:* Jeff Lightner <mailto:jlightner AT water DOT com>
>>     *To:* Amado Gramajo <mailto:Amado.Gramajo AT us.icap DOT com> ;
>>     dave.markham AT fjserv DOT net <mailto:dave.markham AT fjserv DOT net> ;
>>     veritas-bu AT mailman.eng.auburn DOT edu
>>     <mailto:veritas-bu AT mailman.eng.auburn DOT edu>
>>     *Sent:* Wednesday, April 16, 2008 6:04 AM
>>     *Subject:* Re: [Veritas-bu] install client with ssh
>>
>>     I don't see those links under Solaris8 and Solaris9 on my server.

>>     I think someone there must have manually created them?
>>
>>      
>>
>>     You might look in the original install_client they to which they
>>     are linked.  If it doesn't mention ssh or sftp in it then its
hard
>>     to see how the links would be valid.   It does occur on occasion
>>     that things are context sensitive (I've seen this in many
>>     binaries) where they decide what to do based on the name you used
>>     when you started them.   So far as I know NBU doesn't do that.
>>
>>      
>>
>>     The point in my post however was not to see what scripts you had
>>     but to tell you where you could find examples of ssh install
>>     scripts under NBU.   Using that information along with what is in
>>     your Solaris install_client you ought to be able to cobble
>>     something together that does what you need.
>>
>>      
>>
>>     On the flip side you can always install a client by inserting the
>>     CD in the client and doing the install from that rather than
>>     pushing from the master.
>>
>>      
>>
>>
>>     
>
------------------------------------------------------------------------
>   
>>     *From:* Amado Gramajo [mailto:Amado.Gramajo AT us.icap DOT com]
>>     *Sent:* Wednesday, April 16, 2008 8:53 AM
>>     *To:* Jeff Lightner; dave.markham AT fjserv DOT net;
>>     veritas-bu AT mailman.eng.auburn DOT edu
>>     *Subject:* RE: [Veritas-bu] install client with ssh
>>
>>      
>>
>>     Here's whats under the Solaris client:
>>
>>      
>>
>>      ./ftp_to_client
>>
>>     ./install_client
>>
>>     ./sftp_to_client
>>
>>     ./ssh_to_client
>>
>>      
>>
>>     They are all links to install_client.
>>
>>      
>>
>>      
>>
>>
>>     
>
------------------------------------------------------------------------
>   
>>     *From:* Jeff Lightner [mailto:jlightner AT water DOT com]
>>     *Sent:* Wednesday, April 16, 2008 8:32 AM
>>     *To:* Amado Gramajo; dave.markham AT fjserv DOT net;
>>     veritas-bu AT mailman.eng.auburn DOT edu
>>     *Subject:* RE: [Veritas-bu] install client with ssh
>>
>>      
>>
>>     On our 6.0 MP4 master we have the following under
>>     /usr/openv/netbackup/client:
>>
>>     ./HP9000-800/HP-UX11.11/install_client.ssh
>>
>>     ./Linux/RedHat2.4/install_client.ssh
>>
>>     ./INTEL/FreeBSD/install_client.ssh
>>
>>     ./INTEL/FreeBSD4.5/install_client.ssh
>>
>>     ./INTEL/FreeBSD5.3/install_client.ssh
>>
>>      
>>
>>     Don't see one for Solaris but then again we don't use Solaris
>>     here.  If you examine the above to see how they are doing it ssh
>>     in comparison with the Solaris ftp one perhaps you can figure out
>>     how to make your own Solaris ssh script.
>>
>>      
>>
>>
>>     
>
------------------------------------------------------------------------
>   
>>     *From:* veritas-bu-bounces AT mailman.eng.auburn DOT edu
>>     [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] *On Behalf Of
>>     *Amado Gramajo
>>     *Sent:* Wednesday, April 16, 2008 7:44 AM
>>     *To:* dave.markham AT fjserv DOT net; veritas-bu AT mailman.eng.auburn 
>> DOT edu
>>     *Subject:* Re: [Veritas-bu] install client with ssh
>>
>>      
>>
>>     6.5 has an install script that uses ssh beautifully.
>>
>>     ----- Original Message -----
>>     From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
>>     <veritas-bu-bounces AT mailman.eng.auburn DOT edu>
>>     To: veritas-bu AT mailman.eng.auburn DOT edu
>>     <veritas-bu AT mailman.eng.auburn DOT edu>
>>     Sent: Wed Apr 16 06:08:57 2008
>>     Subject: [Veritas-bu] install client with ssh
>>
>>     Guys has anyone written or done anything they use to install
>>     clients on
>>     Unix over ssh?
>>
>>     I found  a script a while ago someone had done replacing
>>     ftp_to_clients
>>     with sftp_to_clients for v 5.0 which has always worked a charm.
>>
>>     Now in v6.0Mp4 ftp_to_clients is a sym link to install_clients
and
>>     
> i
>   
>>     need to use SSH(sftp) to do the install instead of ftp. I tried a
>>     global
>>     replace of :-
>>
>>     :.,$s/ftp/sftp/g  but then running the script doesnt seem to work
>>     correctly.
>>
>>     Primarily dealing with Solaris here but any tips would be good.
>>
>>     Cheers
>>     _______________________________________________
>>     Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>>     http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>>
>>     
> **********************************************************************
>   
>>     This communication and all information (including, but not
limited
>>     
> to,
>   
>>     market prices/levels and data) contained therein (the
>>     "Information") is
>>
>>     for informational purposes only, is confidential, may be legally
>>
>>     privileged and is the intellectual property of ICAP plc and its
>>     affiliates
>>
>>     ("ICAP") or third parties. No confidentiality or privilege is
>>     waived or
>>
>>     lost by any mistransmission. The Information is not, and should
>>     
> not
>   
>>     be construed as, an offer, bid or solicitation in relation to any
>>
>>     financial instrument or as an official confirmation of any
>>     transaction.
>>
>>     The Information is not warranted, including, but not limited, as
>>     
> to
>   
>>     completeness, timeliness or accuracy and is subject to change
>>
>>     without notice. ICAP assumes no liability for use or misuse of
the
>>
>>     Information. All representations and warranties are expressly
>>
>>     disclaimed. The Information does not necessarily reflect the
views
>>     
> of
>   
>>     ICAP. Access to the Information by anyone else other than the
>>
>>     recipient is unauthorized and any disclosure, copying,
>>     
> distribution or
>   
>>     any action taken or omitted to be taken in reliance on it is
>>     prohibited. If
>>
>>     you receive this message in error, please immediately delete it
>>     and all
>>
>>     copies of it from your system, destroy any hard copies of it and
>>
>>     notify the sender.
>>
>>
>>     
> **********************************************************************
>   
>>      
>>
>>     ----------------------------------
>>     CONFIDENTIALITY NOTICE: This e-mail may contain privileged or
>>     confidential information and is for the sole use of the intended
>>     recipient(s). If you are not the intended recipient, any
>>     disclosure, copying, distribution, or use of the contents of this
>>     information is prohibited and may be unlawful. If you have
>>     received this electronic transmission in error, please reply
>>     immediately to the sender that you have received the message in
>>     error, and delete it. Thank you.
>>     ----------------------------------
>>
>>
>>     
> **********************************************************************
>   
>>     This communication and all information (including, but not
limited
>>     
> to,
>   
>>     market prices/levels and data) contained therein (the
>>     "Information") is
>>
>>     for informational purposes only, is confidential, may be legally
>>
>>     privileged and is the intellectual property of ICAP plc and its
>>     affiliates
>>
>>     ("ICAP") or third parties. No confidentiality or privilege is
>>     waived or
>>
>>     lost by any mistransmission. The Information is not, and should
>>     
> not
>   
>>     be construed as, an offer, bid or solicitation in relation to any
>>
>>     financial instrument or as an official confirmation of any
>>     transaction.
>>
>>     The Information is not warranted, including, but not limited, as
>>     
> to
>   
>>     completeness, timeliness or accuracy and is subject to change
>>
>>     without notice. ICAP assumes no liability for use or misuse of
the
>>
>>     Information. All representations and warranties are expressly
>>
>>     disclaimed. The Information does not necessarily reflect the
views
>>     
> of
>   
>>     ICAP. Access to the Information by anyone else other than the
>>
>>     recipient is unauthorized and any disclosure, copying,
>>     
> distribution or
>   
>>     any action taken or omitted to be taken in reliance on it is
>>     prohibited. If
>>
>>     you receive this message in error, please immediately delete it
>>     and all
>>
>>     copies of it from your system, destroy any hard copies of it and
>>
>>     notify the sender.
>>
>>
>>     
> **********************************************************************
>   
>>      
>>
>>
>>     
>
------------------------------------------------------------------------
>   
>>     _______________________________________________
>>     Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>>     http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>>     
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>   

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu