University of Wisconsin Help Desk Knowledgebase


 ADVANCED

Bucky Backup - Installing the Bucky Backup Client for Linux


This document explains how to install and configure the Bucky Backup client for a linux server. If you already have the Bucky Backup client installed, then see the document Bucky Backup - Upgrading the Bucky Backup Client for Linux for instructions on upgrading to the latest version of the Bucky Backup client.

The Bucky Backup client installation is comprised of the following steps:

Bucky Backup Registration

In order to use the Bucky Backup service, you must register as a Bucky Backup user. During the registration process, you will create a unique node name for your computer and a password.

Preparing for the Bucky Backup Client Installation

  1. Review the latest Readme file in the Bucky Backup client repository.
  2. Confirm that your server meets the Bucky Backup client environment prerequisites.
  3. Check the list of known problems and limitations for the Bucky Backup client.

Installing the Bucky Backup Client

  1. Download the latest version of the Bucky Backup client for linux from the Bucky Backup client repository.
    • wget <bucky backup client url>
  2. Extract the client installation files into a temporary directory.
    • tar xlzf <bucky backup client>.tar.gz
  3. Change into the temporary directory and install the new Bucky Backup client.
    • For the 32 bit client enter the following commands:
      1. rpm -i TIVsm-API.i386.rpm
      2. rpm -i TIVsm-BA.i386.rpm
    • For the 64 bit client enter the following commands:
      1. rpm -i TIVsm-API.i386.rpm
      2. rpm -i TIVsm-API64.i386.rpm
      3. rpm -i TIVsm-BA.i386.rpm

Configuring the Bucky Backup Client

Before the Bucky Backup client can be used, communication, logging, processing, and scheduling options must be configured for the server.

  1. Replace the sample dsm.sys.smp client option file in the /opt/tivoli/tsm/client/ba/bin/ directory with this dsm.sys.smp file that has been customized for the Bucky Backup environment.
  2. Replace the sample dsm.opt.smp client option file in the /opt/tivoli/tsm/client/ba/bin/ directory with this dsm.opt.smp file that has been customized for the Bucky Backup environment.
  3. See IBM's creating and modifying the client system options file documentation for an overview of the configuration process.
  4. Copy the dsm.sys.smp file to dsm.sys and copy the dsm.opt.smp file to dsm.opt and customize the configuration for your server.

Configuring the Communication options

  1. Check the Bucky Backup registration response email to find out which Bucky Backup server your node connects to.
  2. Configure the Servername, Nodename, TCPPort and TCPServeraddress entries in the dsm.sys file for your node.
     
    Servername TCPServeraddress TCPPort
    bucky1 buckybackup1.doit.wisc.edu 1499
    bucky2 buckybackup2.doit.wisc.edu 1500
    bucky3 buckybackup3.doit.wisc.edu 1501
    bucky4 buckybackup4.doit.wisc.edu 1502
  3. Also configure the servername option in the dsm.opt file.
  4. See IBM's communication options documentation for more details.

Configuring Processing Options

  1. Configure the resourceutilization option in the dsm.sys file to define how many concurrent sessions the Bucky Backup server and client can use during processing.
  2. Configure the users option in the dsm.sys file to specify which users are authorized to request Bucky Backup services.
  3. Configure the passwordaccess option in the dsm.sys file to determine if you want to save the Bucky Backup node password or be prompted for it at the start of each backup session.

Configuring Backup Logs

  1. Configure the errorlogname and errorlogretention options in the dsm.sys file to specify the name of the error log and how many days to maintain the error log before pruning it.
  2. Configure the schedlogname and schedlogretention options in the dsm.sys file to specify the name of the scheduler log and how many days to maintain the scheduler log before pruning it.

Creating an Include-Exclude List

  1. Review IBM's include-exclude list documentation for an overview of excluding files or directories from backup.
  2. Configure include and exclude options in the dsm.sys file.
    • Alternatively, you can configure the inclexcl option in the dsm.sys file and store the include and exclude options in a separate config file.

Configuring the Client Scheduler

  1. Review IBM's configuring the client scheduler documentation.
  2. Select either the CAD-managed or the traditional client scheduler method.
    • If you select the CAD-managed scheduler:
      1. Configure the managedservices option for schedule in the dsm.sys file.
      2. If you elected to save the Bucky Backup client password with the passwordaccess options in the dsm.sys file, then initialize the password file by running the command:
        • dsmc query session
      3. Configure the dsmcad daemon to startup automatically at system boot.
      4. Start the CAD-managed scheduler.
        • For Redhat Linux
          • service dsmcad start
        • For SuSe Linux
          • /etc/init.d/dsmcad start
    • If you select the traditional client scheduler method:
      1. Configure the schedmode option for polling in the dsm.sys file.
      2. Configure the queryschedperiod option in the dsm.sys file.
      3. If you elected to save the Bucky Backup client password with the passwordaccess options in the dsm.sys file, then initialize the password file by running the command:
        • dsmc query session
      4. Configure the dsmc scheduler to startup automatically at system boot.
        • For Redhat Linux, add the following to the end of /etc/rc.d/rc.local
          • /opt/tivoli/tsm/client/ba/bin/dsmc schedule > /dev/null &
        • For SuSe Linux, add the following entry to the /etc/inittab
          • tsm::once:/opt/tivoli/tsm/client/ba/bin/dsmc schedule > /dev/null 2>&1 #TSM Client
      5. Start the TSM scheduler.
        • /opt/tivoli/tsm/client/ba/bin/dsmc schedule



Keywords: bucky backup tsm novell redhat red hat suse linux install installation instructions howto node registerDoc ID: 6704
Owner: Michael L.Group: Data Center & Shared Computing Services
Created: 2007-11-14Updated: 2009-08-31

Did this document help you to answer your question?