TSM 5.4 for debathena/Ubuntu: Install, Configure, Set Up, and Confirm the Scheduler for TSM
On this page: Install TSM | Configure TSM | Install
the Scheduler | Confirm Scheduled Backups | More Information
Instructions for both new installations and updates of a preexisting one assume that all TSM files have been left in their
default locations.
Please note that the dsm GUI command is no longer available in 5.4. It has been replaced by the dsmj command
which has comparable functionality.
Install TSM
- Download the Linux TSM 5.4 installation archive tsm5427lnx.tar to your
workstation from the MIT Software: Linux page. [Certificates required.]
- Extract the contents of the installation file using the command below:
tar xvf tsm5427lnx.tar
Result: The following files appear:
NOTICES.TXT
README_api_enu.htm
README_enu.htm
README_hsm_enu.htm
TIVsm-API.i386.rpm
TIVsm-API64.i386.rpm
TIVsm-BA.i386.rpm
TIVsm-HSM.i386.rpm
- Log in as root user (or use sudo -i).
- If you have an existing TSM backup installation, perform the following step; otherwise, skip to Step 5.
- cd to /opt/tivoli/tsm/client/ba/bin and add the following line to the dsm.sys file
with a text editor if it is not already present:
ERRORLOGName /opt/tivoli/tsm/client/ba/bin/dsmerror.log
- Install the following Ubuntu packages if they are not already present on your system:
sun-java6-jre
ksh
alien
libstdc++5
- Java issues:
- To use the GUI dsmj client, you will need a compatible Java runtime installed and on your path ahead
of any other Java versions you may have already installed. The one in the Java package above should be used.
-
Modify your path to add /usr/lib/jvm/java-6-sun/bin BEFORE /usr/bin.
- Newer JDK and JRE versions from Sun should also work, but you may get a warning message about using an unsupported
version.
- Use the cd command to move to the directory where the installation packages are located.
- If you are updating a prior TSM installation, perform Step A. below. If you are starting with a new installation, perform
Step B.
Step A. Updating a prior installation:
Enter the following commands to update the TSM Backup-Archive client (command-line, API and GUI), the administrative client
(command-line), and the Web client:
- aptitude remove tivsm-api
- aptitude remove tivsm-ba
- alien -i --scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm
Do not be concerned by messages like:
Warning: unable to add ownership fixup code to postint...
as this is not really a problem.
Proceed to Step 3. in the Install the Scheduler section below.
Step B. Starting with a new installation:
Enter the following command to update the TSM Backup-Archive client (command-line, API and GUI), the administrative client
(command-line), and the Web client:
- alien -i --scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm
Do not be concerned by messages like:
Warning: unable to add ownership fixup code to postint...
as this is not really a problem.
Do NOT install TIVsm-HSM.i386.rpm or TIVsm-API64.i386.rpm.
Users running 64 bit Operating Systems do not need the latter rpm and it serves no useful purpose in our configuration.
[Back to top]
Configure TSM
If you are setting up TSM on your system for the first time, perform all the steps below. If you are updating an existing
TSM installation on this machine, skip ahead to Step 3. in the Install the Scheduler section.
You'll need to download the MIT TSM sample configuration files for UNIX -- dsm.sys and dsm.opt --
and then edit the dsm.sys file as described below.
- Copy the MIT sample configuration files to this directory: /opt/tivoli/tsm/client/ba/bin
- Open the dsm.sys file in a text editor, and enter your TSM nodename in the NODename line. The sample
shown in the next step uses the nodename COMPUTER1.
- Specify your assigned TSM server by uncommenting the appropriate TCPServeraddress line. The sample below
uses the server backup-a.
If you are unsure of your TSM server, check the confirmation email sent
from the Computing Help Desk, or contact the Computing Helpdesk:
617-253-1101 or computing-help@mit.edu.
Excerpt from sample dsm.sys file
* Remove the asterisk before 'NODename' and specify your assigned
* TSM node name. If you do not include the nodename, TSM uses the
* name returned by the 'hostname' command.
NODename COMPUTER1
* Specify the TCP/IP server address for the TSM backup server that
* was assigned in your registration notice by removing the
* asterisk(*) from one of the following TCPServer address lines.
* Phone the Help Desk at 3-1101 if you have any questions.
* If your backup server is *** BACKUP-A ***, remove the asterisk(*)
* from the following line:
TCPServeraddress backup-a.mit.edu
* If your backup server is *** BACKUP-B ***, remove the asterisk(*)
* from the following line:
* TCPServeraddress backup-b.mit.edu
* If your backup server is *** BACKUP-C ***, remove the asterisk(*)
* from the following line:
* TCPServeraddress backup-c.mit.edu
* If your backup server is *** BACKUP-D ***, remove the asterisk(*)
* from the following line:
* TCPServeraddress backup-d.mit.edu
* If your backup server is *** BACKUP-G ***, remove the asterisk(*)
* from the following line:
* TCPServeraddress backup-g.mit.edu
- Reset your TSM password.
- Run the following command:
/usr/bin/dsmc set password
and enter the temporary password you were provided at the prompt.
- If you are returned to the tsm> prompt, exit by typing quit.
[Back to top]
Install the Scheduler
- Become 'root' if you are not 'root' already.
- cd to the /etc/event.d directory and create file dsm-sched with
a text editor containing the following lines:
# dsm-sched
#
# This service starts the Tivoli Storage Manager "dsmc sched" backup
# process and respawns it as the scheduled backup happens or the
# dsmc process gets killed or dies.
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on runlevel 0
stop on runlevel 1
stop on runlevel 6
respawn
exec /usr/bin/dsmc sched >/dev/null 2>&1
- After modifying your configuration, your TSM Scheduler needs to be
restarted. The easiest way to do this is to reboot. You will need to do
this again any time you make further configuration changes. You can also stop and start the scheduler manually by running as root:
/sbin/stop dsm-sched
/sbin/start dsm-sched
[Back to top]
Confirm Scheduled Backups -- Check the TSM Schedule Log Periodically
- Check the Schedule Log, /opt/tivoli/tsm/client/ba/bin/dsmsched.log
- Use a text editor to open the schedule log.
- Go to the end of the log and look for confirmation that the backup completed. Look for completion summary beginning
with the text:
SCHEDULEREC STATUS BEGIN
- You may find it helpful to create an alias on the desktop as a reminder to periodically check it.
[Back to top]
More Information
The TSM for UNIX User's Guide provides more information. [Certificates required.]
[Back to top]
 |
MIT IS&T Article #8512 |
|
