[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:	NetWorker
Notice:	kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:	DECWET::RANDALL.com::lenox

Created:	Thu Oct 10 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	750
Total number of notes:	3361

448.0. "How to automate (via SMS) a NetWorker NT installation" by KAHLUA::LEMONS (And we thank you for your support.) Fri Feb 28 1997 13:22

    Hi
    
    Thanks very much for providing PDF files with the Windows NT V4.3
    products.  We're beginning to use SMS here, and having working PDFs
    will speed up the deployment.
    
    Now, knowing a thing or two about InstallShield (which was used to
    create the SETUP.EXE program that runs the NetWorker NT installation),
    I noticed that the PDF supports 4 different installation types, each of
    which uses a different InstallShield Silent response file (all with the
    .ISS extension).  I noticed that, for the client and server response
    files, the third dialogue box response (the one that prompts for the
    backup server name) is 'littlebird|ried02'.
    
    And therein lies my question:  how, when using an automated
    installation, do you envision a site-specific value for server name
    getting entered?
    
    Now, in a simple world, I could just edit the .ISS files for my one
    site backup server, and all would be well.  However, I use (with joy)
    the NetWorker server network interface field, such that every one of
    our 16 IP subnets uses a different backup server.  How, then, can I
    automate the installation of NetWorker in my environment?
    
    Thanks!
    tl
    
    p.s. I noticed that, when an Update installation is run, the backup
    server is NOT prompted for.  So, when updating, this won't be an issue,
    fyi.

T.R	Title	User	Personal Name	Date	Lines
448.1	It's a simple world.	DECWET::KOWALSKI	Time's not for saving	`Fri Feb 28 1997 13:39`	8
	You must have a crufty old field test version because those strings are not in the SSB version. Yes, you have to edit the iss files and substitute your server name for string "myserver" in the section [AskText-0]. Mark
448.2		KAHLUA::LEMONS	And we thank you for your support.	`Fri Feb 28 1997 14:12`	14
	Sure enough, the _Alpha_ kit contains the string 'myserver'; the _Intel_ kit contains the string posted in .0. "Yes, you have to edit the iss files and substitute your server name for string "myserver" in the section [AskText-0]." Gak. I want to have an installation process that looks like, "SMS, go install Networker on those 34 systems". These systems might have any one of 16 server addresses. Having 16 different kits with 16 different server string values isn't much fun. Any thoughts on this? Thanks! tl
448.3		DECWET::KOWALSKI	Time's not for saving	`Fri Feb 28 1997 14:45`	4
	RFEs are cheerfully accepted by [email protected]. You could also consider down-loading uniform win32app\nsr\res\servers files to the clients. Mark
448.4		DECWET::LENOX	Why is DECdirect so out of date?	`Fri Feb 28 1997 14:52`	5
	If you send stuff to Legato, it would still be of interest to us here just what you do send and what kind of response you get (if any). Sending it yourself does insure it gets there faster than we'd get around to sending it.
448.5		SANITY::LEMONS	And we thank you for your support.	`Mon Mar 03 1997 07:28`	22
	Also re .3. Just down-loading uniform win32app\nsr\res\servers files won't solve my problem (I don't think; you tell me!). My issue is not the list of valid NetWorker servers. My issue is wanting to force the client to connect to just two of the list of 16 servers. I'm assuming that I only want those two servers in the win32app\nsr\res\servers file. The other 14 servers (actually, just different IP addresses that point to the same server) are reachable via non-optimal network routings. I believe that server-initiated backups use the value in the 'server network interface' field to specify to the client which server it will use; if this field is empty, then the server name is used. True? For restores, there is currently no way to select the 'server network interface' that will be used. That is, the data will be seen as coming from the main IP address of the network adapter. True? But for backups initiated by the client, I believe I must specify the server I want it to use as the first server in the server list. True? Thanks! tl
448.6		DECWET::MORRIS	This mind left intentionally blank	`Wed Mar 05 1997 08:04`	24
	> I'm assuming > that I only want those two servers in the win32app\nsr\res\servers > file. The other 14 servers (actually, just different IP addresses that > point to the same server) are reachable via non-optimal network > routings. Correct. > I believe that server-initiated backups use the value in the 'server > network interface' field to specify to the client which server it will > use; if this field is empty, then the server name is used. True? Also correct. > For restores, there is currently no way to select the 'server network > interface' that will be used. That is, the data will be seen as coming > from the main IP address of the network adapter. True? Correct. > But for backups initiated by the client, I believe I must specify the > server I want it to use as the first server in the server list. True? No. It defaults to the one you setup during install.
448.7		DECWET::LENOX	Beep, beep!	`Wed Mar 05 1997 08:44`	15
	In Note 448.6 Terry Morris wrote: > In Note 448.5 Terry Lemons wrote: >> But for backups initiated by the client, I believe I must specify the >> server I want it to use as the first server in the server list. True? > No. It defaults to the one you setup during install. It does use the first server in the server list. This would correspond to the first server one enters on the servers line during install. Terry Lemons is correct. However one could change the server one backs up to by using the -s option for the user gui (I generally do this because I have multiple servers I check things out on, however there is no way to automate changing the properties).