Configure multiple dsmc schedulers to use systemd/systemctl

neoseeker1337Leave a comment
  1. Create a shell script that would run the multiple dsmc schedulers:server1:/opt/tivoli/tsm/client/ba/bin # cat sched.sh
    #!/bin/bash
    dsmc sched -se=server_file > /dev/null 2>&1 &
    dsmc sched -se=server_db > /dev/null 2>&1 &
    dsmc sched -se=server_mly_db > /dev/null 2>&1 &
  2. Create the systemctl unit file, enable and start the service:

    server1:/etc/systemd/system # cat tsm-sched.service
    [Unit]
    Description=TSM client scheduler
    After=local-fs.target network-online.target[Service]
    Type=forking
    GuessMainPID=no
    Environment=”DSM_LOG=/opt/tivoli/tsm/client/ba/bin”
    ExecStart=/opt/tivoli/tsm/client/ba/bin/sched.sh

    [Install]
    WantedBy=multi-user.target

    #chmod 644 tsm-sched.service
    #systemctl daemon-reload
    #systemctl enable tsm-sched.service
    #systemctl start tsm-sched.service

  3. Check the service status:

    server1:/etc/systemd/system # systemctl status tsm-sched.service
    ? tsm-sched.service – TSM client scheduler
    Loaded: loaded (/etc/systemd/system/tsm-sched.service; enabled; vendor preset: disabled)
    Active: active (running) since Wed 2018-04-25 07:34:40 SAST; 5min ago
    CGroup: /system.slice/tsm-sched.service
    +-27499 dsmc sched -se=server_file
    +-27500 dsmc sched -se=server_db
    +-27501 dsmc sched -se=server_mly_dbApr 25 07:34:40 server1 systemd[1]: Starting TSM client scheduler…
    Apr 25 07:34:40 server1 systemd[1]: Started TSM client scheduler.

Configure multiple dsmcad instances to start automatically on a single Linux host

neoseeker1337Leave a comment

Under certain circumstances, it may be beneficial to use multiple dsmcad schedule services on a single Linux client host. This document describes the requirements to configure multiple dsmcad instances to run and start automatically at system startup:

1. Create two unique node stanzas in the dsm.sys file (by default, this is located in /opt/tivoli/tsm/client/ba/bin/):

# cat /opt/tivoli/tsm/client/ba/bin/dsm.sys
SErvername node1
COMMMethod TCPip
TCPPort 1500
TCPServeraddress localhost
nodename node1
errorlogname /opt/tivoli/tsm/client/ba/bin/dsmerror-node1.log
schedlogname /opt/tivoli/tsm/client/ba/bin/dsmsched-node1.log
managedservices webclient sched
httpport 1581
passwordaccess generate

SErvername node2
COMMMethod TCPip
TCPPort 1500
TCPServeraddress localhost
nodename node2
errorlogname /opt/tivoli/tsm/client/ba/bin/dsmerror-node2.log
schedlogname /opt/tivoli/tsm/client/ba/bin/dsmsched-node2.log
managedservices webclient sched
httpport 1582
passwordaccess generate

NOTE: It may be beneficial to include certain includes/excludes to differentiate these nodes. Otherwise, the same data be be backed up using the two node names.

2. Create two dsm.opt files, one for each node (by default these will be located in /opt/tivoli/tsm/client/ba/bin):

# cat /opt/tivoli/tsm/client/ba/bin/dsm-node1.opt
servername node1
# cat /opt/tivoli/tsm/client/ba/bin/dsm-node2.opt
servername node2

3. Enable passwordaccess generate by logging in with the credentials for both nodes:

# dsmc q sess -optfile=dsm-node1.opt
…
# dsmc q sess -optfile=dsm-node2.opt
…

4. Make two copies of the default rc.dsmcad init script (by default, this script is located in /opt/tivoli/tsm/client/ba/bin):

# cp /opt/tivoli/tsm/client/ba/bin/rc.dsmcad /opt/tivoli/tsm/client/ba/bin/rc.dsmcad-node1
# cp /opt/tivoli/tsm/client/ba/bin/rc.dsmcad /opt/tivoli/tsm/client/ba/bin/rc.dsmcad-node2

5. SLES distributions only: Make two copies of the dsmcad program (by default, this program is located in /opt/tivoli/tsm/client/ba/bin):

# cp /opt/tivoli/tsm/client/ba/bin/dsmcad /opt/tivoli/tsm/client/ba/bin/dsmcad-node1
# cp /opt/tivoli/tsm/client/ba/bin/dsmcad /opt/tivoli/tsm/client/ba/bin/dsmcad-node2

6. Edit rc.dsmcad-node1:

Change this line for RHEL distributions (verified with RHEL 6.4 using the 6.4.0.1 client):
daemon $DSMCAD_BIN

To be this:
daemon $DSMCAD_BIN -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node1.opt

Change these lines for SLES distributions (verified with SLES 11 SP3 using the 7.1.2.0 client):
# Provides: dsmcad
DSMCAD_BIN=$DSMCAD_DIR/dsmcad
startproc $DSMCAD_BIN
echo -n “Starting dsmcad:”
echo -n “Stopping dsmcad:”
echo -n “Checking dsmcad:”

To be these:
# Provides: dsmcad-node1
DSMCAD_BIN=$DSMCAD_DIR/dsmcad-node1
startproc $DSMCAD_BIN -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node1.opt
echo -n “Starting dsmcad-node1:”
echo -n “Stopping dsmcad-node1:”
echo -n “Checking dsmcad-node1:”

7. Edit rc.dsmcad-node2:

Change this line on RHEL distributions:
daemon $DSMCAD_BIN

To be this:
daemon $DSMCAD_BIN -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node2.opt

Change these lines for SLES distributions:
# Provides: dsmcad
DSMCAD_BIN=$DSMCAD_DIR/dsmcad
startproc $DSMCAD_BIN
echo -n “Starting dsmcad:”
echo -n “Stopping dsmcad:”
echo -n “Checking dsmcad:”

To be these:
# Provides: dsmcad-node2
DSMCAD_BIN=$DSMCAD_DIR/dsmcad-node2
startproc $DSMCAD_BIN -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node2.opt
echo -n “Starting dsmcad-node2:”
echo -n “Stopping dsmcad-node2:”
echo -n “Checking dsmcad-node2:”

8. Create new links in /etc/init.d/ to point to the 2 new rc.dsmcad init scripts. This allows the Linux init service to start the dsmcad services at system start:

# cd /etc/init.d/
# ln -s /opt/tivoli/tsm/client/ba/bin/rc.dsmcad-node2 dsmcad-node2
# ln -s /opt/tivoli/tsm/client/ba/bin/rc.dsmcad-node1 dsmcad-node1
# ls -la dsm*
lrwxrwxrwx. 1 root root 45 Aug 2 08:04 dsmcad-node1 -> /opt/tivoli/tsm/client/ba/bin/rc.dsmcad-node1
lrwxrwxrwx. 1 root root 45 Aug 2 08:04 dsmcad-node2 -> /opt/tivoli/tsm/client/ba/bin/rc.dsmcad-node2

9. Register the 2 new rc scripts with chkconfig:

# chkconfig –add dsmcad-node1
# chkconfig –add dsmcad-node2

10. Test the configuration with “service start” to make sure the scripts load and start without issue:

# service dsmcad-node1 start
Starting dsmcad-node1: [ OK ]
# service dsmcad-node2 start
Starting dsmcad-node2: [ OK ]
# ps -ef | grep dsmcad
root 2689 1 0 09:04 ? 00:00:00 /opt/tivoli/tsm/client/ba/bin/dsmcad -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node1.opt
root 2719 1 0 09:04 ? 00:00:00 /opt/tivoli/tsm/client/ba/bin/dsmcad -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node2.opt

(SLES distributions will list dsmcad-node1 and dsmcad-node2 as the program name)

11. Reboot and confirm that the two dsmcad instances started automatically:

# ps -ef | grep dsmcad
root 1830 1 0 09:14 ? 00:00:00 /opt/tivoli/tsm/client/ba/bin/dsmcad -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node1.opt
root 1856 1 0 09:14 ? 00:00:00 /opt/tivoli/tsm/client/ba/bin/dsmcad -optfile=/opt/tivoli/tsm/client/ba/bin/dsm-node2.opt

Solution to Fix External/Flash Drive Files Changed into Shortcuts

neoseeker1337Leave a comment

The good side of these viruses are that they don’t delete the actual content. It was just hide in our Flash Drive. We can easily recover all the files.

Step 1: If you are affected by Shortcut Viruses,Do not format your Flash or External Drive. If you format you can’t Recover it.
Step 2: Check your Flash Drive’s Drive Letter ( Example : I: or K:)
Step 3: Click on “Start” –>Run–>type “cmd” and click on OK
Step 4: If your Flash Drive Letter is K: then Type the below command in your “cmd” and Press “Enter”

attrib -h -r -s /s /d k: .
(Note : Replace the letter k: with your flash drive letter)