jbconfig man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]



JBCONFIG(8)							   JBCONFIG(8)

NAME
       jbconfig - jukebox resource configuration tool

SYNOPSIS
       jbconfig [ -s server ] [ -l ]

DESCRIPTION
       The  jbconfig  program provides an interactive script for configuring a
       jukebox (Media Autochanger Device) for use  with	 a  NetWorker  server.
       The script pauses periodically for you to enter a response to a prompt.
       If you want to accept the default choice	 displayed  in	braces,	 press
       [RETURN] or [ENTER].

       Starting with NetWorker 7.2.1 and above; the support of LUS was discon‐
       tinued for Solaris 10 and above.	 If jbconfig reports  that  it	cannot
       find  any  autochangers after installation, run inquire to make sure it
       is able to see the devices.  Please refer to the	 inquire(8)  man  page
       for  more  information.	 Sometimes  in	an  ill-configured  server, an
       autochanger is seen but its drives are not  mapped  to  the  '/dev/rmt'
       path  but  only to the '/dev/scsi/sequential' path.  jbconfig will con‐
       figure the autochanger using this path.	The problem  here  is  that  a
       drive using the '/dev/scsi/sequential' path is assumed to be standalone
       drive.  This means the autochanger will not work correctly.

       After the jukebox is configured, use the nsrcap(8) command or the  Reg‐
       istration  window  to enter the enabler code for your Autochanger Soft‐
       ware Module. You must have a separate enabler code for each jukebox you
       want to use with NetWorker.

OPTIONS
       -s server
	      Specifies	 the  controlling  server, when jbconfig is being used
	      from a storage node.  To define a jukebox resident on a  storage
	      node,  the jbconfig command must be run on the storage node. See
	      nsr_storage_node(5) for additional information on storage nodes.

       -l     Performs a complete LUN search for all SCSI adapters in the sys‐
	      tem when performing Autodetection.  This argument is accepted on
	      all systems, but does not have any effect on HP-UX systems.  Due
	      to  the  method used to scan for available devices on HP-UX sys‐
	      tems, all accessible devices are always shown, and the -l option
	      has  no  additional  effect.   On	 all other systems, the normal
	      behavior is to start checking at LUN 0 for  SCSI	devices.   The
	      first empty LUN found will end the search for a given target ID.
	      With the -l option, all LUNS present on all target IDs  for  all
	      SCSI  busses  in the system will be checked for jukeboxes.  This
	      can take a very long time and should therefore only be used when
	      necessary.  For example, a Fibre Channel adapter can support 126
	      target IDs, each of which may have 80 or	more  LUNs.   Checking
	      all LUNs on this single adapter may take over 10 minutes.

CONFIGURATION DIALOG
       The  first question jbconfig will ask you, is to select a type of juke‐
       box to install.

		   1) Configure an AlphaStor Library.
		   2) Configure an Autodetected SCSI Jukebox.
		   3) Configure an Autodetected NDMP SCSI Jukebox.
		   4) Configure a SJI Jukebox.
		   5) Configure a STL Silo.

	      What kind of Jukebox are you configuring? [1]

       Enter the number corresponding to the jukebox type you are  installing.
       The default selection is 1.

       An  AlphaStor  Library is any jukebox that is controlled by EMC AlphaS‐
       tor.  It is configured in NetWorker as  a  logical  jukebox,  with  the
       actual jukebox operations carried out by AlphaStor.

       An  Autodetected SCSI Jukebox is any SCSI (Small Computer System Inter‐
       face) based jukebox connected to a system that NetWorker can  automati‐
       cally detect.

       Autodetected  NDMP  SCSI	 Jukebox  is  any  SCSI (Small Computer System
       Interface) based jukebox connected directly to a Network	 Data  Manage‐
       ment  Protocol (NDMP) Server, that NetWorker will automatically detect,
       with the provided NDMP hostname, user-id,  user-password,  and  jukebox
       handle. (See example).

       An SJI Jukebox is a Standard Jukebox Interface compliant jukebox.  This
       is a list of well known SCSI based jukeboxes, plus any additional third
       party  jukebox  devices	that  adhere to this protocol that the you may
       have added to the system.

       If you select the second choice (Install an Autodetected SCSI Jukebox),
       jbconfig will print out a list of jukeboxes it detects on the system.

       For example:
	    These are the SCSI Jukeboxes currently attached to your system:
		   1) scsidev@0.2.0: other, Vendor <AIWA>, Product <AL-17D>
		   2) scsidev@2.2.0: DLI Libra Series
		   3) scsidev@1.4.1: ARC-DiamondBack
	    Which one do you want to install?

       When  this message appears, enter the number corresponding to the juke‐
       box that you wish to configure. Note  that  if  jbconfig	 was  able  to
       detect only one SCSI jukebox on the system, it will go ahead and select
       that jukebox as the one to be configured without waiting for  the  user
       to  make the selection. This also applies to situations where there are
       multiple SCSI jukeboxes on the system and all but one are already  con‐
       figured	in  NetWorker. Even in this case jbconfig goes ahead and auto‐
       matically selects the one that has  not	yet  been  configured  without
       waiting for the user to make a selection.

       If  you choose to install an SJI compliant jukebox, jbconfig will print
       a list of known SJI Jukeboxes and will prompt you for  the  appropriate
       type that you want to configure.

       For example:
	    Enter  the	number	corresponding  to  the type of jukebox you are
	    installing:
		    1) ADIC-1200c/ADIC-1200d
		    2) ADIC-VLS
		    3) ARC-DiamondBack
		    4) Breece Hill
		    5) DLI Libra Series
		    6) Quantum DLT/Digital DLT
		    7) EXB-10e/EXB-10h
		    8) EXB-10i
		    9) EXB-60
		    10) EXB-120
		    11) EXB-210
		    12) EXB-218
		    13) EXB-400 Series
		    14) HP-C1553A/Surestore 12000e
		    15) Metrum (SCSI)
		    16) Qualstar
		    17) Spectralogic
		    18) STK-9704/Lago 340
		    19) STK-9708/Lago 380 (SCSI) Datawheel
		    20) IBM 7331/IBM 9427
		    21) ATL/Odetics SCSI
		    22) HP-Optical 630MB/1.3GB
		    23) other
	    Choice?

       When this message appears, enter the number corresponding to the appro‐
       priate  model, for example, if you are installing an HP optical jukebox
       select the number "22".

       For all jukebox types, jbconfig prompts you for the name	 you  want  to
       call  this  jukebox.  This  is a convenient way for you to identify the
       jukebox	for  yourself  and  NetWorker,	 for   example,	  'Engineering
       Autochanger'.  NetWorker	 will  store this name as a NetWorker resource
       (see nsr_resource(5)).  When defining a jukebox attached to  a  storage
       node,  jbconfig prefixes the hostname of the storage node to the begin‐
       ning of the names using the remote device syntax ("rd=hostname:").  See
       nsr_storage_node(5) for additional information on storage nodes.

       For  all	 jukebox types, jbconfig prompts you for a description of this
       jukebox. This is another convenient way for you to identify the jukebox
       for yourself, for example, 'Engineering 4 Drive DLT Autochanger on Rack
       #2'.

       For SJI jukebox types, jbconfig prompts you for the name of the control
       port  associated	 with  the  jukebox  being configured. For Silos, this
       could be the name of the host running the silo software	(for  ACSLS  &
       DAS)  or	 the  name  of	the  3494,  depending on the type of Silo. For
       Autodetected SCSI jukeboxes, jbconfig detects the correct name and goes
       ahead  with  the	 configuration.	 This  name  is in the form of libscsi
       devices (see libscsi(8)).  For SJI compliant jukeboxes, no such	detec‐
       tion  is	 done. The name you enter should either be the device name for
       the jukebox as described	 in  any  third	 party	SJI  compliant	driver
       installed,  or  the  format  used for autodetected jukeboxes. A list of
       attached autochangers can be obtained by running the  changers(8)  com‐
       mand.

       Once a control port is entered, jbconfig will check to see if the model
       selected is a SCSI or SJI based jukebox.	 If the	 jukebox  model	 is  a
       SCSI  or	 SJI based jukebox, jbconfig will attempt to query the jukebox
       about various internal parameters (for example,	number	of  slots  and
       drives).	 If  this  query  fails, it is possible that there is a device
       driver installation problem or a hardware problem.

       Next, if the jukebox contains tape devices, you are asked if  automated
       cleaning	 of  devices  in the jukebox should be turned on. If automated
       cleaning is enabled, the jukebox and all devices	 in  the  jukebox  are
       configured  for	automated  cleaning.   On successful installation, the
       information that pertains to device cleaning for the  jukebox  and  all
       its  devices are displayed. Note that with the introduction of the Com‐
       mon Device Interface (CDI), NetWorker now  has  two  events  that  will
       cause  an  automatic  cleaning  to occur: schedule-based cleaning, with
       devices being cleaned after a certain (configurable) amount of time has
       elapsed, and on-demand cleaning, where cleaning is initiated by TapeAl‐
       ert warnings issued by the devices. Schedule-based cleaning  is	always
       active  when  autocleaning is enabled.  On-demand cleaning is used when
       the CDI attribute for a tape device is set to anything other than  'Not
       Used'  in the device resource. If on-demand cleaning is being used, you
       should set the Cleaning Interval for the device itself to a large time,
       such  as 6 months, so that NetWorker does not clean the device unneces‐
       sarily.	See nsr_device.5 for  a	 more  detailed	 explanation  of  CDI,
       TapeAlert and Cleaning Interval.

       At  this point, the user has an option of either going ahead with auto‐
       matic configuration of the jukebox, accepting all detected  information
       and default choices as correct, or choosing to custom configure some or
       all aspects of the configuration, including configuring devices as NDMP
       or  shared devices, configuring drives that were not detected by jbcon‐
       fig, or changing the model type of any of  the  detected	 devices.  The
       user can choose to go the custom configuration route by answering 'yes'
       to the following question:

       Do you want to change the model(s) or configure them as shared or  NDMP
       drives? (yes / no) [no]

       If  the user chooses the custom configuration option, the user is given
       a choice of configuring	the  drives  as	 NDMP  and/or  shared  drives.
       Answering  'yes'	 to  either of the prompts will take the user to other
       relevant questions about NDMP and/or shared drive configuration.

       If the user chose 'yes' to configuring NDMP devices, jbconfig  proceeds
       to  prompt  the	user for this information. NDMP devices require a user
       name and password to be entered for each device.	  The  user  name  and
       password correspond to the entries set in the NDMP server.

       If  the	user  chose  'yes'  to	configuring shared drives, the user is
       prompted for multiple device paths for each physical drive in the juke‐
       box. These device paths would typically be located on different storage
       nodes within a data zone, under the control of  one  NetWorker  Server.
       Drives  or  device  paths  on  remote  nodes  are  to be entered in the
       "host:<device-path>" form. It's not necessary  that  all	 drives	 in  a
       jukebox	be  shared  drives;  entering  a null response to a prompt for
       additional device paths for a drive skips that drive and takes  you  to
       the  next step in the configuration. A unique 'hardware-id' of the form
       '<jukebox name> - <drive no>' is automatically assigned to each	shared
       instance	 of a drive. The 'hardware-id' is how NetWorker keeps track of
       shared devices. See nsr_device(5) for a description of the  hardware-id
       attribute.

       Next,  jbconfig prompts the user for the model of the drives being con‐
       figured. In case jbconfig has been able to detect the model type(s), it
       will display this information and ask for confirmation. If not, it lets
       the user configure the model for each drive.

       If you selected Autodetected SCSI jukeboxes, NetWorker  determines  the
       name  of	 each media device by sending inquiries for information to the
       jukebox. Not all jukeboxes support this capability, but	many  do  (for
       example,	 the  Exabyte 210).  This inquiry does not take place when the
       owning host is different than where jbconfig is running.

       If configuring devices on a remote storage node, jbconfig asks the user
       if  s/he	 wants to configure the node on which the device is being con‐
       figured as a Dedicated Storage Node (DSN). A DSN is a node which allows
       only  data  from	 the  local  host  to be backed up to its devices. See
       nsr_device(5) for more details on DSN. The question is of the form:

       A Dedicated Storage Node can backup only local  data  to	 its  devices.
       Should  helium  be  configured  as a Dedicated Storage Node? (yes / no)
       [no]

       Earlier versions of jbconfig used to prompt the	user  for  information
       about  bar  code	 readers  in jukeboxes and whether volume names should
       match bar code labels. With NetWorker 7.0 and later, jbconfig tries  to
       set  these attributes either by querying the jukebox for information or
       making intelligent guesses. For Silos, the 'bar code reader' and 'match
       bar code labels' attributes in the jukebox resource are set to 'yes' by
       default. If it is a jukebox, jbconfig  queries  the  jukebox  for  this
       information.  If	 both  features	 are supported by the jukebox, it sets
       both fields to 'yes.' If both features are not supported, it sets  both
       fields to 'no.' However, if the jukebox reports that it can handle vol‐
       ume tags, but has no bar code reader, jbconfig still sets  both	fields
       to  'yes,'  since  some	jukeboxes with bar code readers tend to report
       this way. At the end of	the  installation  jbconfig  prints  out  this
       information  and	 the user can use NetWorker Management Console to edit
       the jukebox resource to set the fields to 'No' if he so desires.

       If the above two fields are set,	 the label templates will not be  used
       by  the	jukebox,  and  each media volume must have a readable bar code
       label.  Note that on some small jukeboxes, like the  HP	1557A  or  the
       SONY  TSL_A500C, setting 'bar code reader' to 'yes'  may cause problems
       with the labeling. The solution is to set the appropriate attributes to
       'No' as described above.

       If  the	jukebox has been configured successfully you will see the fol‐
       lowing message:

	      Jukebox has been added successfully

	      The following configuration options have been set:

       followed by a list of options that have been set by default.

JBCONFIG FILE
       The file /nsr/jbconfig is the jukebox models configuration file.	  This
       file can be used to configure a non-standard list of jukebox models.
       VECTOR-TYPE  MODEL-NAME<NEWLINE>,  where VECTOR-TYPE is either SJI (the
       Standard Jukebox Interface) or ATL (RS232-based	devices	 speaking  the
       IGM-ATL	serial	communications	protocol).   The MODEL-NAME can be any
       string.

EXAMPLES
       (User entries are in italics).

       Example 1)

       # jbconfig
		1) Configure an AlphaStor Library.
		2) Configure an Autodetected SCSI Jukebox.
		3) Configure an Autodetected NDMP SCSI Jukebox.
		4) Configure a SJI Jukebox.
		5) Configure a STL Silo.

       What kind of Jukebox are you configuring? [1] 2 <RETURN>
       These are the SCSI Jukeboxes currently attached to your system:
	 1) scsidev@0.6.0: EXB-210
	 2) scsidev@3.0.0: ADIC
       Which one do you want to install?  1<RETURN>
       Installing an 'EXB-210' jukebox - scsidev@0.6.0

       What name do you want to assign to this jukebox device?	Engineer‐
       ing<RETURN>

       Turn NetWorker auto-cleaning on (yes/no) [yes]?	yes<RETURN>

       The following drives have been detected in this auto-changer:
	1> 8mm @ 1.1.0 ==> \\.\Tape0
	2> 8mm @ 1.2.0 ==> \\.\Tape1 These are all the drives that this auto
       changer possesses.

       Do you want to change the model(s) or configure them as shared or NDMP
       drives? (yes / no) [no] yes <RETURN>

       Is (any path of) any drive intended for NDMP use? (yes / no) [no] yes
       <RETURN>

       Is any drive going to have more than one path defined? (yes / no) [no]
       yes <RETURN>

       You will be prompted for multiple paths for each drive.	Pressing
       <Enter> on a null default advances to the next drive.

       Please enter the device path information in one of the following for‐
       mats:

	       \\.\Tape0 --for local path or
	       host:device-path --for remote node or
	       host:drive-letter:directory path --for Windows disk file

       Drive  1, element 82, system name = \\.\Tape0,
	      local bus / target / lun value = 1/1/0,
		  model 8mm
       Device path 1 ? [\\.\Tape0]
	    Enter NDMP user name for host 'happy'? [] user1 <RETURN>
	    Enter NDMP password (characters will not be echoed): <RETURN>
       Device path 2 ? [] helium:/dev/rmt/1cbn
	    Enter NDMP user name for host 'helium'? [] user3 <RETURN>
	    Enter NDMP password (characters will not be echoed): <RETURN>
       Device path 3 ? [] <RETURN>

       Drive  2, element 83, system name = \\.\Tape1,
	      local bus / target / lun value = 1/2/0,
		  model 8mm
       Device path 1 ? [\\.\Tape1]
	    Enter NDMP user name for host 'ableix.emc.com'? [] <RETURN>
       Device path 2 ? [] <RETURN>

       Only model 8mm drives have been detected.
       Are all drives in this jukebox of the same model?  (yes / no) [yes] yes
       <RETURN>

       A Dedicated Storage Node can backup only local data to its devices.
       Should helium be configured as a Dedicated Storage Node? (yes / no)
       [no] no <RETURN>
       Jukebox has been added successfully

       The following configuration options have been set:

       > Jukebox description to the control port and model.
       > Autochanger control port to the port at which we found it.
       > Networker managed tape autocleaning on.
       > At least one drive was defined with multiple paths.  All such drives
       are defined with a hardware identification as well as a path value to
       avoid confusion by uniquely identifying the drive.  The hardware iden‐
       tification for all drives which have one is always 'autochanger_name -
       Drive #' where "autochanger_name" is the name you gave to the
       autochanger that was just defined, and the # symbol is the drive numer.
       > Barcode reading to on.
       > Volume labels that match the barcodes.
       > Slot intended to hold cleaning cartridge to 1.	 Please insure that a
       cleaning cartridge is in that slot
       > Number of times we will use a new cleaning cartridge to 12.
       > Cleaning interval for the tape drives to 6 months.

       You can review and change the characteristics of the autochanger and
       its associated devices using NetWorker Management Console.

       Would you like to configure another jukebox? (yes/no) [no] no <RETURN>

       Example 2)

       Here is an example of an AlphaStor library configured with NDMP devices
       on a storage node.

       # jbconfig -s server
       On a storage node, the hostname is a prefix to the jukebox name.
       Enter the hostname to use as a prefix? [brown.emc.com] <RETURN>
       using 'brown.emc.com' as the hostname prefix

		1) Configure an AlphaStor Library.
		2) Configure an Autodetected SCSI Jukebox.
		3) Configure an Autodetected NDMP SCSI Jukebox.
		4) Configure a SJI Jukebox.
		5) Configure a STL Silo.

       What kind of Jukebox are you configuring? [1] <RETURN>
       Installing an AlphaStor jukebox.
       What name would you like to assign to the AlphaStor library?  myau‐
       toloader<RETURN>

       Name of AlphaStor server host machine? [brown.emc.com] <RETURN>
       Port number of AlphaStor server? [44475] <RETURN>

       How many devices are to be configured (1 to 64)? [4] 2<RETURN>
       Enter hostname that owns logical device 1: ? [brown.emc.com] <RETURN>
       Enter name of logical device 1: ?  stk1<RETURN>
       Should the drive be configured as a NDMP device? (yes/no) y<RETURN>
       Enter NDMP user name: ?	root<RETURN>
       Enter NDMP password (characters will not be echoed): password<RETURN>
       Enter hostname that owns logical device 2: ? [brown.emc.com] <RETURN>
       Enter name of logical device 2: ?  stk2<RETURN>
       Should the drive be configured as a NDMP device? (yes/no) y<RETURN>
       Enter NDMP user name: ?	root<RETURN>
       Enter NDMP password (characters will not be echoed): password<RETURN>

       Enter application name defined in AlphaStor/SmartMedia for NetWorker?
       [NetWorker@server] <RETURN>
       Enter application key defined in AlphaStor/SmartMedia for NetWorker?
       [<none>] <RETURN>

       The barcode reader is enabled and volume labels are set to match bar‐
       code labels.

       Jukebox has been added successfully
       Would you like to configure another jukebox? (yes/no) no<RETURN>

       Example 3)

       Here is an example of configuring a jukebox attached to NDMP Tape
       Server.

       # jbconfig

		1) Configure an AlphaStor Library.
		2) Configure an Autodetected SCSI Jukebox.
		3) Configure an Autodetected NDMP SCSI Jukebox.
		4) Configure a SJI Jukebox.
		5) Configure a STL Silo.

       What kind of Jukebox are you configuring? [1]
       3<RETURN>
       Enter NDMP Tape Server name: ?
       molokai<RETURN>
       Enter NDMP user name: ?
       root<RETURN>
       Enter NDMP password (characters will not be echoed):
       password<RETURN>
       Communicating to devices on NDMP Server 'molokai', this may take a while...

       These are the SCSI Jukeboxes currently attached to your system:
	   1) scsidev@0.2.0: Exabyte Jukebox
	   2) scsidev@0.3.0: Standard SCSI Jukebox, QUANTUM / Powerstor L200

       Which one do you want to install?
       1<RETURN>

       Installing an 'Exabyte Jukebox' jukebox - scsidev1027.2.0.

       What name do you want to assign to this jukebox device?
       netapp_jb<RETURN>
       Turn NetWorker auto-cleaning on (yes/no) [yes]?
       yes<RETURN>

       The drives in this jukebox cannot be auto-configured with the available
       information. You will need to provide the path for the drives.

       Is (any path of) any drive intended for NDMP use? (yes / no) [no]
       yes<RETURN>
       Is any drive going to have more than one path defined? (yes/no) [no]
       no<RETURN>

       Please enter the device path information in one of the following formats:

	     \.Tape0 --for local path or
	     host:device-path --for remote node or
	     host:drive-letter:directory path --for Windows disk file

	  After you have entered a device path, you will be prompted for an NDMP
       user name for that path's host. If this device path is not an NDMP device,
       press the enter key to advance to the next device path.	For NDMP devices,
       you need to enter the user name and password the first time we encounter
       that NDMP host. Pressing the enter key for the NDMP user name for any
       subsequent device path on the same host will set the user name and password
       to those defined the first time. You will not be prompted for the password
       in such a case.

       Drive  1, element 82
       Drive path ?
       molokai;nrst2l<RETURN>
	    Enter NDMP user name for host 'molokai'? []
       root<RETURN>
       Enter NDMP password (characters will not be echoed):
       password<RETURN>

       Please select the appropriate drive type number:
	 1) 3480	  18) 9840	    34) optical
	 2) 3570	  19) 9840b	    35) qic
	 3) 3590	  20) 9940	    36) SD3
	 4) 4890	  21) adv_file	    37) sdlt
	 5) 4mm		  22) dlt	    38) sdlt320
	 6) 4mm 12GB	  23) dlt1	    39) SLR
	 7) 4mm 20GB	  24) dlt7000	    40) tkz90
	 8) 4mm 4GB	  25) dlt8000	    41) travan10
	 9) 4mm 8GB	  26) dst (NT)	    42) tz85
	10) 8mm		  27) dtf	    43) tz86
	11) 8mm 20GB	  28) dtf2	    44) tz87
	12) 8mm 5GB	  29) file	    45) tz88
	13) 8mm AIT	  30) himt	    46) tz89
	14) 8mm AIT-2	  31) logical	    47) tz90
	15) 8mm AIT-3	  32) LTO Ultrium   48) tzs20
	16) 8mm Mammoth-2 33) LTO Ultrium-2 49) VXA
	17) 9490

       Enter the drive type of drive 1?
       16<RETURN>

       Jukebox has been added successfully

       The following configuration options have been set:
	  > Jukebox description to the control port and model.
	  > Autochanger control port to the port at which we found it.
	  > Networker managed tape autocleaning on.
	  > Barcode reading to on.  Your jukebox does not report that it has a bar
	    code reader, but it does report that it can handle volume tags.  Some
	    jukeboxes that have barcode readers report this way.
	  > Volume labels that match the barcodes.
	  > Slot intended to hold cleaning cartridge to 1.  Please insure that a
	    cleaning cartridge is in that slot
	  > Number of times we will use a new cleaning cartridge to 5.
	  > Cleaning interval for the tape drives to 6 months.
       You can review and change the characteristics of the autochanger and its
       associated devices using NetWorker Management Console.

       Would you like to configure another jukebox? (yes/no) [no]
       no<RETURN>

SEE ALSO
       jbexercise(8), nsr_device(5), nsr_jukebox(5), nsr_storage_node(5),
       nsr(5), nsrcap(8).

DIAGNOSTICS
       unknown model invalid choice for 'model' (35022)
	      Problem: The NetWorker system does not recognize the model cho‐
	      sen.  If you added a /nsr/jbconfig* file after starting the dae‐
	      mons, you will see this error.  Solution: Restart NetWorker.

       root on computer host is not on type: NSR's
	      administrator list
	      Problem: The user 'root' on the storage node 'host' is not on
	      the administrator list of the NetWorker server.  Solution: Add
	      such an entry to the NetWorker server's administrator list.
	      Note that the entry can be removed after this command completes.

NetWorker 7.3.2			  Aug 23, 06			   JBCONFIG(8)
[top]

List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net