Installing the NetBackup server software into an SRT

Article:HOWTO68861  |  Created: 2012-02-06  |  Updated: 2012-02-06  |  Article URL http://www.symantec.com/docs/HOWTO68861
Article Type
How To

Product(s)

Subject


Installing the NetBackup server software into an SRT

Installing the NetBackup server software into an SRT is similar to installing the NetBackup server software on a real system; you are given the same prompts. However, you have to respond differently than you normally would to some of the prompts.

Choose the Symantec NetBackup software to add to the SRT:
1. The Symantec NetBackup client software. This choice will create an 
SRT that can restore a system from a NetBackup server.
2. The Symantec NetBackup server software. This choice will create an 
SRT that also can restore a Symantec NetBackup media server from its 
own devices.
Enter your selection [1] : 2
Enter a [hostname:]/pathname to where the PBX installics command is 
located :
Enter a [hostname:]/pathname containing Symantec NetBackup Server 
software : /rosbuilds/NB_60/NB_60_Solaris_20050203

The following response appears.

   Processing package instance <bsVRTSnetbp> from
    </tmp/bcreateSRT.bmr.NNN.mnt/solaris>

Note:

All the path names in the following text that start with / are relative to the SRT path. Nothing in the actual system is changed by this installation process.

Note:

sol8fs is the name of the BMR file server where this sample SRT is created. Replace this name with the name of the BMR file server where you want to create the SRT.

NetBackup and Media Manager binaries will be installed in /opt/openv 
and a link will be created from /usr/openv to /opt/openv
Is this okay? (y) [y,n,?,q]

To install NetBackup server software into an SRT

  1. Type y.

    The following prompt appears.

    The Solaris clients will be loaded.
    Do you want to load any other NetBackup clients onto the server? (y) 
    [y,n,?]
  2. Type n.

    The following messages are displayed, followed by a list of files being installed:

       Using </opt> as the package base directory.
        ## Processing package information.
        ## Processing system information.
        ## Verifying disk space requirements.
        ## Checking for conflicts with packages already installed.
        Installing Symantec NetBackup and Media Manager as <VRTSnetbp>
        ## Executing preinstall script.
        Creating /opt/openv.
        Creating link from /usr/openv to /opt/openv.
        ## Installing part 1 of 1.
        .
        .
        .

    After the list of files is displayed, the following messages are displayed:

    All additional keys should be added at this time.
    Do you want to add additional license keys now? (y/n) [y]
  3. Type n.

    The original client media server license keys are used. The following messages appear.

    Use /usr/openv/netbackup/bin/admincmd/get_license_key to add, 
    delete or list license keys at a later time.
    Installing NetBackup Enterprise Server version: 5.0GA
    If this machine will be using a different network interface than the 
    default (sol8fs), the name of the preferred interface should be used 
    as the configured server name. If this machine will be part of a 
    cluster, the virtual name should be used as the configured server 
    name. 
    Would you like to use "sol8fs" as the configured
    name of the NetBackup server? [y,n] (y)
  4. Type y.

    The following prompt appears.

    Is sol8fs the master server? [y,n] (y)
  5. Type n.

    The following prompt appears.

    What is the fully qualified name of the master server?
  6. Enter the name of the machine where the SRT is created, and press Enter.

    The following messages appear.

    Checking for a bpcd entry in /etc/inetd.conf: Adding bpcd entry.
    Original /etc/inetd.conf saved as 
    /etc/inetd.conf.NBU_103102.16:42:50.
    Checking for a vnetd entry in /etc/inetd.conf: Adding vnetd entry.
    Checking for a vopied entry in /etc/inetd.conf: Adding vopied entry.
    Checking for a bpjava-msvc entry in /etc/inetd.conf: Adding
    bpjava-msvc entry.
    Checking /etc/services for the needed NetBackup and Media Manager
    services. 
    Copying original /etc/services file to 
    /etc/services.NBU_103102.16:44:03
    Editing /etc/services to update NetBackup and Media Manager 
    services.
    /etc/services will be updated to add the following entries for
    NetBackup/Media Manager.
    bprd 13720/tcp bprd
    bpcd 13782/tcp bpcd
    bpdbm 13721/tcp bpdbm
    vnetd 13724/tcp vnetd
    vopied 13783/tcp vopied
    bpjobd 13723/tcp bpjobd
    nbdbd 13784/tcp nbdbd
    visd 9284/tcp visd
    bpjava-msvc13722/tcp bpjava-msvc
    vmd 13701/tcp vmd
    acsd 13702/tcp acsd
    tl8cd 13705/tcp tl8cd
    tldcd 13711/tcp tldcd
    ts8d 13709/tcp ts8d
    odld 13706/tcp odld
    tl4d 13713/tcp tl4d
    tsdd 13714/tcp tsdd
    tshd 13715/tcp tshd
    tlmd 13716/tcp tlmd
    tlhcd 13717/tcp tlhcd
    lmfcd 13718/tcp lmfcd
    rsmd 13719/tcp rsmd
    To change these entries modify the file 
    /tmp/services.ov_edited.23505
    and enter <RETURN> when ready to continue:
  7. Do not modify any of the entries. Press Enter.

    The following messages appear.

    /etc/services has been updated to contain NetBackup and Media 
    Manager services.
    WARNING: ypwhich: the domainname hasn't been set on this machine.
    WARNING: ypcat: the domainname hasn't been set on this machine.
    Sending SIGHUP to inetd process.
    /usr/openv/volmgr/bin/update_services: usage: kill [ [ -sig ] id ... 
    | -l ]
  8. Ignore the above warnings and errors. The dialog continues as follows:

    To make NetBackup and Media Manager startup automatically
    when the system is restarted, the NetBackup script found in
    /usr/openv/netbackup/bin/goodies/netbackup has been placed in 
    /etc/init.d,
    with links to it placed in the /etc/rc2.d directory.
    To make NetBackup and Media Manager shutdown automatically
    when the system is restarted, the NetBackup script found in
    /usr/openv/netbackup/bin/goodies/netbackup has been placed in 
    /etc/init.d ,
    with links to it placed in the /etc/rc0.d directory.
    Extracting NetBackup-Java product files.
    Installing NetBackup-Java, and the Java runtime environment for 
    SunOS
    5.8.
    Configuring NetBackup-Java runtime environment.
    The installation of the NetBackup-Java product on sol8fs is 
    complete.
    Copied files to /kernel/drv and to /kernel/drv/sparcv9.
    Doing add_drv of the sg driver
    Removing old /dev/sg entries.
    Editing /etc/devlink.tab...
    Copying original /etc/devlink.tab to 
    /etc/devlink.tab.12-11-03-15:50:46.
    Added entry in /etc/devlink.tab file.
    Made links in /dev/sg
  9. Ignore the error messages, but only if they are displayed exactly as shown. Any other informative messages can also be ignored.

    The following prompt appears.

    Enter global device host (default: sol8fs):
  10. Press Enter. The following messages appear.

    Could not connect to vmd on host sol8fs (70)
    Set global device database host failed.
    The global device database version is incompatible
  11. Ignore these error messages. The following prompt appears.

    Do you want to start the Media Manager device daemon processes? 
    (y/n) [y]
  12. Type n.

    The following prompt appears.

    Enter a patch or package name to install additional software in 
    SRT, or nothing if done: []:

    This is the end of the SRT creation procedure that is specific to a NetBackup 5.0 media server SRT.

    For the rest of the SRT creation process, refer to Creating a Shared Resource Tree.

    See About creating a shared resource tree.


Legacy ID



v53728311_v71529406


Article URL http://www.symantec.com/docs/HOWTO68861


Terms of use for this information are found in Legal Notices