Bogotá – Cundinamarca, David Puerta: (Ver video 35)

On Solaris and MP-RAS, you can use the pkgadd program to perform an unattended installation of the NVBU Server and Client software. In a

non-interactive mode the pkgadd program gets input from a response file which is created using the pkgask program. Additionally, the program uses an

administration file, which specifies the default installation actions.

7.3.1 pkgask

A response file is a text file which provides answers for the questions that would be asked during the installation process. The pkgask command performs a dummy installation of the package, and records all answers in a response file. Each answer is stored as a value for a variable identified in the response file. To run the pkgask command, type:

pkgask -r <response file> <package>

„ response file – Name of the response file. Full path must be specified if you do not want to create the file in the current directory. The response file will contain values for the following variables:

™ PKG_BASE – The installation directory for NVBU.

™ DB_DIR – The location for the NVDB.

™ PASSWORD – The password for NVBU Server or Client.

™ CHOSEN_CLASSES – The NVBU components that are to be installed. The standard components include the following:

™ core

™ dataplugin

™ devicectl

™ gui

™ online help

For NVBU Server installation, the following component is also included:

™ server

™ LOGICAL_NAME – The name for the NVBU Server or Client.

™ NVLANGUAGE – The language settings for NVBU. This variable will take one of the following values:

™ ChineseSimp (for Chinese Simple)

™ English

™ French

™ JapaneseEUC

™ Korean

These values are case-sensitive.

„ <package> – The name of the package that is to be installed.

7.3.2 pkgadd

To perform am unattended installation using the pkgadd command, type:

pkgadd -n -a <admin file> -d <device> -r <response file> <package>

„ -n – Performs the installation in a non-interactive mode. The default mode is interactive.

„ -a <admin> – The installation administration file to use. An administration file specifies the default installation actions by assigning values to installation parameters. For example, it allows administrators to specify whether to perform an interactive or a non-interactive installation, or how to proceed when the package being installed already exists on the system, and so on.

„ -d <device> – full path to the directory or the identifiers for fixed or removable device that contains the package to be installed.

„ -r <response file> – Full path to a response file that was created from a previous pkgask session.

„ <package> – The name of the package that is to be installed.

7.3.3 Installation Procedure

For a silent installation on Solaris/MP-RAS UNIX, use the following steps: 1. Log on to the target machine with root-level account.

2. Extract the binary file if the file was downloaded from the Web site. The following command will extract the files:

tar -zxvf <filename>

3. Create a response file using pkgask. You can assign any file name and store the response file in any directory. A sample response file for Server and Client installation is provided in the following section.

4. Navigate to the directory that contains the extracted files for NVBU. 5. Copy the administration file from /var/sadm/install/admin/default to the

current directory. Edit this file to perform a non-interactive installation. A sample administration file is provided in the following section.

6. To start the installation procedure, type:

pkgadd -n -a <admin file> -d <path to the package> -r <response file> netvault

7.3.4 Examples

This section provides some sample files.

Sample Response File for NVBU Server Installation

Sample Response File for NVBU Client Installation

Important: For an NVBU Client installation, do not include the server component when setting the CHOSEN_CLASSES variable.

PKG_BASE="/usr/netvault" DB_DIR="/usr/netvault/db" PASSWORD="abcxyz12"

CHOSEN_CLASSES="core server dataplugin devicectl gui onlinehelp" LOGICAL_NAME="NVBU-Server" NVLANGUAGE="English" PKG_BASE="/usr/netvault" DB_DIR="/usr/netvault/db" PASSWORD="abcxyz12"

CHOSEN_CLASSES="core dataplugin devicectl gui onlinehelp" LOGICAL_NAME="NVBU-Client"

Sample Administration File

mail=

instance=overwrite #allows upgrades

partial=nocheck #no check for partially installed packages runlevel=nocheck #no check for run level errors

idepend=nocheck #no check for package dependencies rdepend-nocheck #no check for package dependents space=quit #quit if install runs out of disk space setuid=nocheck #no check for setuid errors

conflict=nocheck #no check for conflicting files during install

action=nocheck #do not ask for install confirmation basedir=default #do not set the basedir variable networktimeout=60

networkretries=3 authentication=quit

keystore=/var/sadm/security proxy=

Chapter 8:

U

PGRADING

NVBU

„ NVBU Upgrade Considerations

„ Preparing for an Upgrade

™ Backing up the Existing NVDB

™ Stopping NVBU Processes

™ Disabling Anti-Virus Software

„ Upgrading NVBU on Linux/UNIX

„ Upgrading NVBU on Mac OS X

„ Upgrading NVBU on Solaris and MP-RAS

„ Upgrading NVBU on Windows

„ Post-Upgrade Procedures

™ Rebooting the System After an Upgrade

™ Post-Upgrade Requirements for Plug-in for FileSystem

„ Known Upgrade Issues

„ Installing NetVault Backup Plug-ins