Caldera Specific Instructions

As mentioned in a previous section, the Caldera version of BACKUP.UNET is supplied "pre-installed" in RPM format. To install it, mount you CDROM and run

rpm -ivh /mnt/cdrom/Packages/RPMS/cbu-3.0-2.i386.rpm

The exact version number in the file name may vary.

Installing this RPM creates files in /var/nbk and /usr/nbk. It also adds a startup "rc" file in /etc/rc.d/init.d. The group "unet" is added to /etc/group. It also automatically initializes the BACKUP.UNET database tables and adds the local host to the system.

After installing the RPM, you still need to run autoconf to configure your local tape drive and other parameters.

Note that with the Caldera version of BACKUP.UNET, full hosts names must be used when specifying a particular host. This is due to the fact that Caldera Linux uses fully qualified domain names for the hostname. To check the full name, run

hostname

Several shell variables need to be set to use BACKUP.UNET. After installing the RPM, the are added to both /etc/profile and /etc/csh.cshrc. You will need to manually "source" these variables the first time you install the package:

source /etc/profile

To start the BACKUP.UNET daemons run:

/etc/rc.d/init.d/cbu start

To stop the BACKUP.UNET daemons run:

/etc/rc.d/init.d/cbu stop

If the machine yor are installing is a second or subsequent machine to an existing BACKUP.UNET system, there is a new program that must be executed on this new host ("nbkaddhost"). This program is unique to the Caldera version of BACKUP.UNET and is not yet in the on-line documentation. Currently this utility does not prompt for BRP/IOP type and defaults to both BRP and IOP.

If you install /mnt/cdrom/Packages/RPMS/cbu-3.0-2.src.rpm, you will find the original "tar" file to which the standard MTI BACKUP.UNET installation proceedure applies. This tar file will be located in /usr/src/SOURCES/unet-linux-1.9.tgz.

Also note that BACKUP.UNET only works with tape devices that fully support the Linux tape ioctl functions. This includes SCSI tape devices but does not include the "ftape" (floppy tape) device.

This chapter describes the procedures for unloading the BACKUP.UNET software to a host directory and installing BACKUP.UNET.

The section Installing the BACKUP.UNET Software concludes with a complete example of an installation, showing the prompts and messages you would see.

Note: Please review Chapter 1, Pre-Installation Instructions in its entirety before you begin the installation procedure.

Unloading the BACKUP.UNET Software

Before you begin this procedure, be sure that you have completed the steps in Chapter 1, Pre-Installation Instructions.

Note: The time required to unload the BACKUP.UNET software from the distribution media onto the host that will be used to perform the installation depends on the device. A slower device may take as long as 45 minutes; a faster device may take only 15 minutes or less.

Perform these instructions from the installation source host.

Using the UNIX tar or cpio command, unload the BACKUP.UNET software from the distribution media to the temporary unload directory you created in step 6 of Pre-Installation Instructions.

Note: Your unload device must be a rewind-on-close device. For Linux SCSI tape devices, this is /dev/st0. Check the label on the installation media for the correct format, prior to inserting it into the drive. To begin, enter one of the following commands:
For tar format, enter:
```
 tar xvpf /dev/st0 
```
For cpio format, enter:
```
cpio -icvduBm < /dev/st0
```
Note: st0 represents the device from which the software is being unloaded. Your device name may be different.
After you unload the software, continue to Installing the BACKUP.UNET Software.

Installing the BACKUP.UNET Software

The BACKUP.UNET installation command, nbkinstall, installs the software for one host at a time. nbkinstall provides you with a prompt for each step of the installation process.

By default, BACKUP.UNET automatically creates two directories: the home directory and the binary directory. The home directory includes the configuration database, online catalog, and log files. The binary directory includes programs for the GUI and command line interfaces.

Note: You can automate the process of installing the BACKUP.UNET software on multiple hosts of the same architecture by specifying a list of hosts using the -f option of the nbkinstall command. This type of installation is intended to be invoked by a more experienced user (for example, someone who has been running BACKUP.UNET with a small number of systems and wants to install a second group.) During this installation method, you can also determine the level of prompting.

For information about using this method, refer to Appendix A, Using the Automated Installation Procedure.

Install the BACKUP.UNET software on each system in your network that will be a BACKUP.UNET host. If your network includes several different types of machines, perform the installation on one machine architecture at a time. For example, in a network of Sun 4 machines and DEC machines, install the software on all of the Sun 4 machines, and then all of the DEC machines.

Perform the following instructions from the installation source host.

Change to the temporary unload directory and, at the system prompt, enter the following command:
```
 ./nbkinstall                  
```
The version of BACKUP.UNET, the machine type, and the operating system level is displayed.
All output from the nbkinstall command is logged to a file. The name of the log file is displayed. (You may want to read this file after the software is installed to check for errors or other installation information.)
The installation continues, and the screen shows:
```
If you want to drive the installation process from an 
input file, enter the name of the input file now. If 
you want to do an interactive installation, simply 
press <RETURN>:                 
```

Press <Return>.

You are prompted for the BACKUP.UNET group name.

Enter the name of the account group that all 
BACKUP.UNET hosts on your network will use:

Enter the name you used when you created the group in step 5 of the Steps in Installation Preparation on page 1-6.

The next prompt concerns the configuration information needed for the installation:

If BACKUP.UNET is installed and running on your net
work, enter the name of a currently running host that 
this host can talk to. If you are installing your 
first host, press <RETURN>:

Respond with either of the following, depending on whether or not this is your first host:
- If this is the first host on which you are installing BACKUP.UNET, press <Return>.
- If this is not the first host, enter the name of another host on the network that has a BRP or IOP daemon currently running. (For example, if this is the second host, you would enter the name of the first host.)
  You are prompted to select the appropriate syntax for sending mail on your network:
```
Specify the syntax to send mail on your network. If 
your mail syntax is "mail user@host" enter 0               
If your mail syntax is "mail host!user" enter 1                
```

Enter either 0 or 1.

You are prompted to specify if you wish root on an already-installed host to have permission to automatically perform BACKUP.UNET administrative tasks on all hosts installed by nbkinstall:

If you would like to configure the hosts you are 
installing so that they may be administered from 
"root" on a single host, enter that administrative 
host name now. If not, press <RETURN>.

Enter the appropriate host name to select this option, or press <Return>.

The system prompts:

Please enter your 8 character SERIAL NUMBER from the 
supplied information sheet.
Enter Serial Number (99999999)

Enter your unique BACKUP.UNET serial number.

The system prompts:

Please enter your 12 character ACTIVATION CODE from 
the supplied information sheet. It does not matter if 
you use upper or lower case letters and you may omit 
the separator characters if you wish.                  
Enter Activation Code (XXXX-XXXX-XXXX)

You are prompted for the name of the host on which you want to install the software:

 Enter name of system to install software on.

Enter the host name. This can be any valid host anywhere on your network.
You are prompted for the name of the binary directory:
```
Enter the fully-qualified directory path where the 
BACKUP.UNET executables will be kept.                 
```
Enter the full path name of the directory that is to contain the BACKUP.UNET executable programs, such as '/usr/local/nbk/bin'.

You are prompted for the name of the home directory:
```
Enter the BACKUP.UNET home directory path on host <hostname>.                  
```
Enter the full path name of the directory that is to contain the BACKUP.UNET configuration database, online catalog, and log file, such as '/usr/local/nbk/nbk'.

Note: The home directory should not be on an NFS-mounted file system. You are prompted for the host attributes:
```
Will <host> have its files backed up? (y/n)                  
```
Enter Y if you plan to back up files residing on the host being installed. (The host will be designated as a BRP.) Otherwise, enter N.
The system prompts:
```
Does <host> have devices that will be used for back ups? (y/n)                 
```
Enter Y if there are tape drive devices on the host being installed that will be used for backups. (The host will be designated as an IOP.) Otherwise, enter N.
The display shows:
```
Will <host> be an administrative reporting station?   (y/n)                  
```
Enter Y if you intend to use the host being installed as an administrative reporting station. (The host will be designated as a reporting station.) Otherwise, enter N.
If this is the first host being installed, you are notified that it will be automatically defined as a syncro-server. Otherwise you are asked if you want this host designated as a syncro-server.
```
Will <host> be a syncro server host? (y/n)                 
```
Enter Y if you want this host designated as a syncro-server. Otherwise, enter N.
The BACKUP.UNET binaries are installed, the home directory is created, and the tables are created. The installation process automatically starts the BRP and IOP daemons.
While the installation progresses, the screen shows status messages similar to those in Figure 2-3 at the end of the chapter. (The status messages are also written to the log file that was automatically created when you ran nbkinstall; however, your responses to the prompts are not included.)

Note: During the installation, the nbkinstall command generates messages that describe the processing. For a description of these messages, refer to Appendix B, Installation Troubleshooting. When the installation is complete, the following message is displayed:
```
Leaving the BACKUP.UNET installation procedure                  
```

Modify your '/etc/rc.d/rc.local' script to start the BACKUP.UNET daemons.

The installation procedure automatically starts the BRP and the IOP daemons. They remain active until you manually shut them down via the nmaint command or until your system is shut down.

The BACKUP.UNET installation procedure generates a default 'rc.nbk' file in the '$NBK' directory. ('rc.nbk' is also copied to the '/etc' directory.) To ensure that the BRP and IOP daemons are restarted automatically whenever your system is brought up, you can append this default 'rc.nbk' file to your local 'rc.local' startup script.

Figure 2-1 below shows the contents of the default 'rc.nbk' file provided with BACKUP.UNET.

#
# Start BACKUP.UNET BRP and IOP Daemons
#
(
  echo Starting BACKUP.UNET...
  NBK="/usr/local/nbk/sun" export NBK
  NBKBIN="/usr/local/bin/sun" export NBKBIN
  if [ -d $NBK -a -d $NBKBIN ]
  then echo BACKUP.UNET directories found.
    PATH=$NBKBIN:$PATH export PATH
    nmaint -startbrp
    for i in 1 2 3 4 5 6
    do
      sleep 5
      ntest -brpactive > /dev/null 2>&1
      stat1=$?
      if [ $stat1 -eq 0 ]
      then
        break
      fi
   done
    if [ $stat1 -ne 0 ]
    then
      echo
      echo "Cannot start BRP daemon within 30 seconds."
      echo "Check LOG file for startup progress..."
      echo
    fi
    nmaint -startiop
    for i in 1 2 3 4 5 6
    do
      sleep 5
      ntest -iopactive > /dev/null 2>&1
      stat2=$?
      if [ $stat2 -eq 0 ]
      then
        break
      fi
    done
    if [ $stat2 -ne 0 ]
    then
      echo
      echo "Cannot start IOP daemon within 30 seconds."
      echo "Check LOG file for startup progress..."
      echo
    fi
   
    echo BACKUP.UNET startup complete
else echo Directory not found
    echo \$NBK = $NBK - \$NBKBIN = $NBKBIN
fi
)>/dev/console 2>&1

Ensure that the script is executed from the system startup file.

If you will not be using the GUI to run BACKUP.UNET, skip to step 17.

If you will be using the GUI, ensure that the 
maint.unet program is installed. The BACKUP.UNET GUI 
uses the maint.unet program to start daemons remotely 
and read the log file remotely. Depending on your sys
tem type, the maint.unet command may or may not have 
been added during installation. You will need to add a 
maint.unet statement to your system's startup file. 
Append the following entry to your system's startup 
file. For IBM systems, the file is 'etc/rc'. For most 
other systems, the startup file is 'etc/rc.local'.                
maint.unet -b dirname1 -h dirname2

In the above statement, dirname1 is the directory name where the executables are kept (for example $NBIN), and dirname2 is the BACKUP.UNET home directory (for example, $NBK).

Set the BACKUP.UNET environment variable in the '.profile' file or '.cshrc' file of each participating BACKUP.UNET user to the BACKUP.UNET home directory.
You must also append the BACKUP.UNET binary directory to your search path. The BACKUP.UNET installation procedure generates a default Bourne shell script ('.profile') and a C shell script ('.cshrc') that are saved in the '$NBK' directory. These scripts add the BACKUP.UNET binary directory to your path and set the BACKUP.UNET environment variable ('NBK'). Be sure to append these scripts to your current '.profile' or '.cshrc' script.

Note: In the following examples, both '/usr/local/nbk /bin' and '/usr/local/nbk/nbk' in the default scripts would have been replaced with the names of the BACKUP.UNET binary and home directories you chose in steps 9 and 10.
Default '.profile' Bourne Shell Script
```
NBK=/usr/local/nbk/nbk export NBK                   
NBIN=/usr/local/nbk/bin export NBIN                   
PATH=$PATH:/usr/local/nbk/bin export PATH                   
```
Default '.cshrc' C Shell Script
```
setenv NBK /usr/local/nbk/nbk                   

setenv NBIN /usr/local/nbk/bin                   

set path=($path /usr/local/nbk/bin)                   
```
The installation procedure automatically starts the BRP and the IOP daemons; however, to verify that the BRP daemon and IOP daemon are running, use the nmaint command. Ensure that your environment has been correctly established by logging off and back onto the system.
The nmaint command lists all participating hosts currently on the network. Figure 2-2 below shows sample results of the nmaint command. The Status field should indicate "Ok" for the host just installed.
If the Status field displays "Fault", one or both daemons are not running. You should check that the NBK environment variable is set and the executable directory is in your path, and then manually start the BRP and IOP daemons, using the following command:
```
nmaint -startbrp -startiop                  
```
Execute the nmaint command again to verify that the daemons are running. If a host still has a status of "Fault," contact MTI Customer Support.
You have completed the installation of BACKUP.UNET on one host.
To install BACKUP.UNET on another host, repeat steps 1 through 18 for each system you identified in the Configuration Checklist. A new log file is created each time you run the nbkinstall command.

After you have installed the BACKUP.UNET software on all of the hosts in your network, you can begin configuration procedures.

Note: In Figure 2-3, shown below, both '/usr/local/nbk/bin' and '/usr/local/nbk/nbk' replace the names of the directories you chose in steps 9 and 10. See the BACKUP.UNET Getting Started Guide for instructions on BACKUP.UNET configuration.

# nbkinstall

Caldera BACKUP.UNET Installation Procedure.

Beginning installation of BACKUP.UNET 3.00.28 for Linux System.
This output is being logged to the file "./inst.log.0".

If you want to drive the installation process from an input file, enter the name of the input file. If you want to do an interactive installation, press <Return>.

Enter the name of the account group that all BACKUP.UNET hosts on your network will use:
unet

If BACKUP.UNET is installed and running on your network, enter the name of a currently running host that this host can talk to. If you are installing your first host, just press <Return>:

Specify the syntax to send mail on your network:

If your mail syntax is "mail user@host", enter 0.
If your mail syntax is "mail user!host", enter 1.

If you would like to configure the hosts you are installing so that they may be administered from "root" on a single host, enter that administrative host name now. If not, just press <Return>.

Please enter your 8 character SERIAL NUMBER from the supplied information sheet.

Enter Serial Number (99999999)
ABCD1234

Please enter your 12 character ACTIVATION CODE from the supplied information sheet. It does not matter if you use upper or lower case letters and you may omit the separator characters if you wish.

Enter Activiation Code (XXXX-XXXX-XXXX)
1234-5678-0000

*** Activation Codes + Serial Number are OK ***

Enter the name of system to install software on
ravin

Enter the fully-qualified directory path where the BACKUP.UNET executables will be kept.
/usr/local/nbk/bin

Enter the BACKUP.UNET home directory path on host ravin.
/usr/local/nbk/nbk

Will ravin have its files backed up? (y/n)
y

Does ravin have devices that will be used for backups? (y/n)
n

Will ravin be an administrative reporting station? (y/n)
n

Since this is the first host you are installing, it will be automatically defined as a syncro-server.
Installing binary directory at ravin:/usr/local/nbk/bin.
Making binary directory ravin:/usr/local/nbk/bin.
Copying initial binaries and commands to ravin:/usr/local/nbk/bin.
Copying BACKUP.UNET binaries and commands to ravin:/usr/local/nbk/bin.
Processing of the binary directory at ravin:/usr/local/nbk/bin is complete.
Installing home directory at ravin:/usr/local/nbk/nbk.
Making BACKUP.UNET home directory ravin:/usr/local/nbk/nbk.
Shared memory key 5 is in use, key 9 will be used instead.
Shared memory key 6 is in use, key 10 will be used instead.

Table: /usr/local/nbk/nbk/nbk-TABLES/BFI
created table w/ 1 part PK
1 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/Dumpseq
created table w/ 2 part PK
2 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/Event
created table w/ 2 part PK
1 part secondary index added
1 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/Vol
created table w/ 2 part PK
2 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/Pool
created table w/ 2 part PK
1 part secondary index added
1 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/Sys
created table w/ 1 part PK
1 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/Dev
created table w/ 1 part PK
1 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/PoolDev
created table w/ 2 part PK
1 part secondary index added
1 part secondary index added

Table: /usr/local/nbk/nbk/nbk-TABLES/Link
created table w/ 1 part PK

Table: /usr/local/nbk/nbk/nbk-TABLES/Operator
created table w/ 1 part PK

Table: /usr/local/nbk/nbk/nbk-TABLES/Configure
created table w/ 1 part PK

Table: /usr/local/nbk/nbk/nbk-TABLES/Overflow
created table w/ 1 part PK

Table: /usr/local/nbk/nbk/nbk-TABLES/FileSys
created table w/ 3 part PK

Installing a BACKUP.UNET activation key.

Activation key: ABCD1234
Serial Number: 1234-5678-0000
Duration: unlimited
Maximum systems: 10

Updating network:

Done.

Adding ravin as a BACKUP.UNET host.
Starting daemon(s).
Starting brp daemon.
Starting iop daemon.
Configuring ravin to allow admin and oper commands from 2nd user "root" on host ravin.
Building of the home directory at ravin:/usr/local/nbk/nbk is complete.

Installing BACKUP.UNET man pages.
Copying man pages to /usr/local/man/cat1

Host ravin was installed successfully.
Leaving the BACKUP.UNET installation procedure.

CHAPTER 2 Installing BACKUP.UNET

Table of Contents

Caldera Specific Instructions

Unloading the BACKUP.UNET Software

Installing the BACKUP.UNET Software