For those of you who have seen this before, I've corrected a couple of
errors in it.
I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client. Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:
1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.
$ sudo apt-get install alien
$ sudo apt-get install ksh alien
2. download the TSM client software from IBM using your web browser.
3. untar the TSM RPMs...
4. Use alien to install the appropriate RPMs.
$ sudo alien -i --scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm
如果出現缺少libgsk8cms.so,請安裝TSM Client封裝檔內的
$ sudo alien -i --scripts gskcrypt32-8.0.13.3.linux.x86.rpm
$ sudo alien -i --scripts gskssl32-8.0.13.3.linux.x86.rpm
5. Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).
6. Run a manual backup.
$ sudo dsmc incremental
7. open port 1501 to the backup server in your firewall.
8. Ubuntu uses Upstart instead of inittabs. To add dsm to the
configuration, create a /etc/event.d/dsm-sched file containing:
----------------------- /etc/event.d/dsm-sched -----------------------
# 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
----------------------- end /etc/event.d/dsm-sched ----------------------------
9. Start the dsmc sched process
$ sudo start dsm-sched
10. Check to see if the /var/log/dsmsched.log is correct.
$ tail /var/log/dsmsched.log
06/29/07 13:33:13 --- SCHEDULEREC QUERY END
06/29/07 13:33:13 Next operation scheduled:
06/29/07 13:33:13 ------------------------------------------------------------
06/29/07 13:33:13 Schedule Name: AM0230
06/29/07 13:33:13 Action: Incremental
06/29/07 13:33:13 Objects:
06/29/07 13:33:13 Options:
06/29/07 13:33:13 Server Window Start: 02:30:00 on 06/30/07
06/29/07 13:33:13 ------------------------------------------------------------
06/29/07 13:33:13 Waiting to be contacted by the server.
如果沒有inittab可以建立排程可以先把dsmc在背景執行:
root@hap:~# nohup /usr/bin/dsmc sched 2> /dev/null &
確認dsmc daemon有在執行
root@hap:~# ps -ef | grep dsmc
root 5084 4511 0 10:44 pts/1 00:00:00 /usr/bin/dsmc sched (執行)
root 5088 4511 0 10:44 pts/1 00:00:00 grep --color=auto dsmc
將這個指令寫在/etc/rc.local使其在開機時自動執行
root@hap:~# vi /etc/rc.local
在最後加入一行
nohup /usr/bin/dsmc sched 2> /dev/null &
reboot測試看看。
如果下ps -ef | grep dsmc跟上面一樣有出現
root 5084 4511 0 10:44 pts/1 00:00:00 /usr/bin/dsmc sched
就表示開機會自動執行了。
11. If you wish to use the dsmj GUI, you must also install a Java
runtime environment. There are several of these available, and JREs
are backwards compatible.
$ sudo apt-get install sun-java6-bin
Note that the dsmj seems to want to run with root permissions. To run it, use:
$ sudo dsmj
沒有留言:
張貼留言