Home » All posts

18 September 2014

How to make dsmcad service startup automatic during system reboot in Linux OS (32 bit and 64 bit)

 ANIL K Y OMMI   Share  Print  Android APP  Save in Dropbox

Automatic TSM scheduler (dsmcad service) should be enabled in order to take the backup of the client systems automatically, and this service should be able to restart itself even when the system reboots. In Linux systems until TSM V5, we have to make an entry in the /etc/inittab as follows

 cad::once:/opt/tivoli/tsm/client/ba/bin/dsmcad >/dev/null 2>&1 # TSM scheduler

 You can use the same settings for both 32-bit and 64-bit Linux operating Systems.

Automatic dsmcad service startup from TSM V6

But, starting with TSM V6 the BA client package comes with a default dsmcad script which can be used to make the dsmcad service automatic during system reboot. 

Automatic dsmcad service startup in Linux 64-bit systems

On a Redhat linux 64-bit system, adding corresponding scripts for the Tivoli Storage Manager client acceptor daemon, dsmcad, is a standard way to perform necessary administrative tasks like starting, stopping or restarting dsmcad and/or dsm scheduler using standard linux service start/stop/restart for automatic or manual operations.

  • The default dsmcad script will be added into the /etc/init.d directory during BA client installation. You can check by using 
          # cd /etc/init.d
          # ls -ltr

  • Next, we have to run the script to start the service.
          # service dsmcad start
      
           You can check the status of the service by using ps -ef | grep -i dsm command

  • Now to make the service automatic during reboot, run the following command.
         # chkconfig --add dsmcad

         Next time when your server reboots, dsmcad service also starts automatically.

Automatic dsmcad service startup in Linux 32-bit systems

On 32-bit systems, the dsmcad script doesn't work properly, I dont know why but I know the work around. You need to do some extra steps to make the dsmcad service automatic. There might be other methods to make this possible too, this is just one of them.

 1) Copy rc.dsmcad script from another 64bit machine to 32 bit machine to 

     /opt/tivoli/tsm/client/ba/bin

 2) Then create a soft link as shown below

      # ln -s /opt/tivoli/tsm/client/ba/bin/rc.dsmcad /etc/init.d/dsmcad

 3) Now run the following commands, using the /sbin/chkconfig command

     Add dsmcad
    # /sbin/chkconfig --add dsmcad

     Start dsmcad in runlevels 3 and 5 only
    # /sbin/chkconfig --level 35 dsmcad on

     Verify what runlevels are enabled for dsmcad
    # /sbin/chkconfig --list dsmcad

 4) After the above step you can start the service 

     To start dsmcad manually run:
    # service dsmcad start

     To stop dsmcad run:
    # service dsmcad stop
   To restart dsmcad (for example to refresh daemon after dsm.sys or dsm.opt modification) 
    # service dsmcad restart

     To check if dsmcad is running run
    # service dsmcad status
    -or-
    # ps -ef | grep dsmcad

 5) Finally run this command to make it automatic restart during reboot.

      # chkconfig --add dsmcad 

 Note: It is a good practice to add the errorlogname parameter in dsm.sys file to run the dsmcad service automatically. Sometimes this might cause a problem too.

Read More


17 September 2014

How to install BA Client on Ubuntu OS and run automatic dsmcad service during system startup

 ANIL K Y OMMI   Share  Print  Android APP  Save in Dropbox

IBM doesn't provide the TSM BA client software package for the Ubuntu Operating System but we have the work around for it. If you want to install BA client on Ubuntu systems and schedule a backup follow the below steps. In this post I will share the steps to install TSM BAclient software and then steps to start automatic dsmcad service during system startup. It is recommended to first check it on a test machine and then go for production.

Procedure to install TSM BA client software on Ubuntu Systems

  • Since ubuntu is one of the Linux flavor, we have to download the suitable BA client software for Linux (32 bit or 64 bit). Download them and copy them into one folder.
  • Next, we have to install alien (rpm2deb converter tool) packages by running the below command. For this we need to have internet connection with firewall disabled. This tool is used to convert the Linux RPM packages to Ubuntu Debian package.
          apt-get install alien libstdc++5 ia32-libs
  • Now, we have to create the .deb install packages by converting .rpm to .deb packages. Use the --scripts to convert the inbuilt scripts into .deb package. Please double check the package names you have downloaded, they might have different names.


         alien -k --scripts gskcrypt64-8.0.14.14.linux.x86_64.rpm
         alien -k --scripts gskssl64-8.0.14.14.linux.x86_64.rpm
         alien -k --scripts TIVsm-API64.x86_64.rpm
         alien -k --scripts TIVsm-BA.x86_64.rpm
  • Now you can check by using ls -ltr comand if they are successfully converted to .deb   package.
  • Now we have to finally install all the .deb packages. You can install the packages one by one or all together by using the below command.
          dpkg -i *.deb

         The above command will install all the .deb packages in that particular directory
  • Finally, we have to manually link the Libraries to the right places as shown below so that the TSM client can find them. These linking process is automatically done on the Linux systems. Here we have to do it manually.       

ln -s /opt/tivoli/tsm/client/api/bin64/libgpfs.so /lib/ 
ln -s /opt/tivoli/tsm/client/api/bin64/libdmapi.so /lib/ 
ln -s /usr/local/ibm/gsk8_64/lib64/libgsk8cms_64.so /lib/ 
ln -s /usr/local/ibm/gsk8_64/lib64/libgsk8ssl_64.so /lib/ 
ln -s /usr/local/ibm/gsk8_64/lib64/libgsk8sys_64.so /lib/ 
ln -s /usr/local/ibm/gsk8_64/lib64/libgsk8iccs_64.so /lib/
ln -s /opt/tivoli/tsm/client/lang/EN_US /opt/tivoli/tsm/client/ba/bin/



  • From this step you can use the same procedure as we use to configure the linux clients. Configure dsm.sys and dsm.opt files and you can start taking the backup.

How to make automatic dsmcad service startup during Ubuntu system starttup

Generally on linux machines, we use /etc/init.d/dsmcad script to enable automatic dsmcad service during system startup. But this script doesn't work in Ubuntu machines. The work around for this is shown below.

1) First, create /etc/event.d/dsmcad or /etc/init/dsmcad.conf  with the following content:

$ vi dsmcad.conf 

     # dsmcad

    # This service starts the Tivoli Storage Manager "dsmcad"

    start on runlevel [2345]
    stop on runlevel [!2345]

    script
            export LANG=en_US
            export LC_MESSAGES=en_US
            export LC_CTYPE=de_DE
    exec /opt/tivoli/tsm/client/ba/bin/dsmcad  >/dev/null 2>&1
    end script

    # end of dsmcad

2) If you did not gave errorlogname parameter in dsm.sys file, dsmcad service will not run. make sure you update dsm.sys file with 

errorlogname=/opt/tivoli/tsm/client/ba/bin/dsmerror.log

3) Now You can start the dsmcad service with following command

    $ start dsmcad
Read More


26 August 2014

Latest TSM Interview Questions - August 2014

 ANIL K Y OMMI   Share  Print  Android APP  Save in Dropbox

  • Tell about yourself and work experience ?
  • Which ticketing tool are you using in your company ?
  • How do you assign tickets to yourself ?
  • What is Runbook  & SLA ?
  • Tell me about your TSM setup details ?
  • What are your daily activities ?
  • How do you check TSM Server health ?
  • What are the copy group parameters ? explain ?
  • How to Install & Configure BA client in AIX /Unix ?
  • What are the differences between TSM V5 and TSM V6 ?
  • What is Policy Domain & Policy Set ?
  • How many policy set and management classes can be defined ?
  • What are the default copy group parameters ?
  • Do we have to validate & activate policy set if we do any modifications to copy group parameters ?
  • What is the command to take incremental & selective backup ?
  • How to restore a file from particular date and time ?
  • How to find if a file is archived on a particular date ?
  • How do you retrieve a file from point time ?
  • What is expire inventory ?
  • What is reclamation ?
  • Difference between reclamation & collocation ?
  • How to move data ?
  • What is node decommissioning ?
  • During migration, what will you do if next storage pool is also full ?
  • What is migration ?
  • What is the difference between Backup & Archive ?
  • Difference between admin schedules & client schedules ?
  • How to check read and write errors in tape volumes ?
  • What is the difference between Physical Library & Virtual Tape Library ?
  • What is Library Manager and Library Clients ?
  • How do you check drive serial number in windows & Unix ?
  • How do you scan tape drives in OS level ?
  • How to configure storageagent/Lanfree  backup on AIX ?
  • How to configure Tape Library ?
  • Tell me the commands to checkin & checkout tape volumes ?
  • What will you do if you have no scratch volumes and no storage slots available in the library ?
  • What will you do if you need scratch tapes immediately and you have no new tapes ?
  • What will you do if TSM DB size gets full ?
  • How to increase TSM DB size on TSM V6 ?
  • What is the maximum value of Activelog ?
  • How do you increase active log size ?
  • How to check if last TSM DB backup is successful or failed ?
  • If my disk storage pool is full, what will you do ?
  • How to update migration to a disk storagepool ?
  • How do you restore oracle db backup from production system to another test system using TDP Oracle ?
  • How to configure TDP Domino, TDP SQL and TDP Oracle clients ?
  • How to link library files during TDP oracle configuration ?


Read More


13 May 2014

Troubleshooting TDP SAP backup error "BKI4008E: File cannot be opened. Reason: errno(22) A system call received a parameter that is not valid"

 ANIL K Y OMMI   Share  Print  Android APP  Save in Dropbox

The following error will be seen while trying to take the SAP Oracle database backup using Tivoli Data Protection (TDP) for SAP with Oracle software through brtools and backint interface.

BR0280I BRCONNECT time stamp: 2014-05-08 17.10.09
#BEGIN /oracle/QDI/sapdata1/sysaux_1/sysaux.data1
#BEGIN /oracle/QDI/sapdata1/system_1/system.data1
BR0315I 'Alter tablespace SYSAUX begin backup' successful
BR0315I 'Alter tablespace SYSTEM begin backup' successful
BR0280I BRCONNECT time stamp: 2014-05-08 17.10.09

BKI4008E: File '/oracle/QDI/sapdata1/sysaux_1/sysaux.data1' cannot be opened. Reason:  errno(22)  A system call received a parameter that is not valid.

BR0280I BRCONNECT time stamp: 2014-05-08 17.10.13
#END /oracle/QDI/sapdata1/sysaux_1/sysaux.data1
#END /oracle/QDI/sapdata1/system_1/system.data1
BR0317I 'Alter tablespace SYSAUX end backup' successful
BR0317I 'Alter tablespace SYSTEM end backup' successful
BR0280I BRCONNECT time stamp: 2014-05-08 17.10.13

BKI1208W: The object '/oracle/QDI/sapdata1/sysaux_1/sysaux.data1' will be retried [3].
BKI1208W: The object '/oracle/QDI/sapdata1/system_1/system.data1' will be retried [3]

The above error doesnt show much information about the error and it will be quite annoying if you have no idea about how SAP and AIX works together. You will see this kind of error if your SAP database filesystems are mounted with the CIO (Concurrent I/O) option enabled. Concurrent I/O (CIO) for JFS2 filesystems gains the benefits of Direct I/O without the locking serialization. It allows a process writing to a file exclusive write access to that file. 

You need to remount the filesystems with CIO option disabled to fix this problem. Apparently, this requires the downtime of your SAP system.

Follow these below steps to troubleshoot this BKI4008E error permanently

1) First, STOP your SAP system (database & application).

2) Check which filesystems have CIO enabled by using lsfs command

      # lsfs

/dev/fslv03     --         /oracle/PRD/origlogA      jfs2  1048576 rw,cio         yes  no
/dev/fslv04     --         /oracle/PRD/origlogB      jfs2  1048576 rw,cio         yes  no
/dev/fslv12     --         /oracle/PRD/oraarch        jfs2  20971520 rw              yes  no
/dev/fslv13     --         /oracle/PRD/sapreorg      jfs2  2097152 rw               yes  no
/dev/fslv14     --         /oracle/PRD/sapdata1      jfs2  41943040 rw,cio       yes  no
/dev/fslv15     --         /oracle/PRD/sapdata2      jfs2  94371840 rw,cio       yes  no
/dev/fslv16     --         /oracle/PRD/sapdata3      jfs2  4194304 rw,cio         yes  no
/dev/fslv17     --         /oracle/PRD/sapdata4      jfs2  115343360 rw,cio     yes  no
/dev/fslv21     --         /eccerp6                           jfs2  4194304 rw                   yes  no

3) After making sure that SAP is down, unmount all the filesystems which have CIO enabled one by one. I am showing only for 2 filesystems, you need to change all the filesystems which have CIO enabled.

      # umount /oracle/PRD/origlogA
      # umount /oracle/PRD/sapdata2

4) Disable the CIO option for the filesystems by using chfs command as shown below

     # chfs -a options=rw /oracle/PRD/origlogA
    # chfs -a options=rw /oracle/PRD/sapdata2

5) Then remount the filesystems. You should disable CIO option for all the SAP filesystems.

      # mount /oracle/PRD/origlogA
     # mount /oracle/PRD/sapdata2

6) Now, if you run lsfs command, the output should be somewhat like

/dev/fslv03     --         /oracle/PRD/origlogA      jfs2  1048576 rw               yes  no
/dev/fslv04     --         /oracle/PRD/origlogB      jfs2  1048576 rw               yes  no
/dev/fslv12     --         /oracle/PRD/oraarch        jfs2  20971520 rw              yes  no
/dev/fslv13     --         /oracle/PRD/sapreorg      jfs2  2097152 rw                yes  no
/dev/fslv14     --         /oracle/PRD/sapdata1      jfs2  41943040 rw              yes  no
/dev/fslv15     --         /oracle/PRD/sapdata2      jfs2  94371840 rw              yes  no
/dev/fslv16     --         /oracle/PRD/sapdata3      jfs2  4194304 rw                yes  no
/dev/fslv17     --         /oracle/PRD/sapdata4      jfs2  115343360 rw            yes  no
/dev/fslv21     --         /eccerp6                              jfs2  4194304 rw                yes  no

7) After making sure all the SAP filesystems are correctly mounted with CIO disabled, START SAP application and database.

8) Finally, now you can restart your SAP database backup using SAP brtools and backint interface and the backup should complete successfully.

Check this below IBM technote for more info

Read More


10 May 2014

Steps to restore TDP SAP for Oracle production (PRD) database to another SAP oracle database (DEV or QTY)

 ANIL K Y OMMI   Share  Print  Android APP  Save in Dropbox

You might required to restore the current SAP oracle database to another SAP database according to the clients requirement. For example, it is required to restore the SAP production database to SAP development/quality database for testing any upgrade/modifications on the existing database before making it live. It is the TSM administrators job to restore the database within the given downtime. TSM administrator should also make sure that the offline backup of SAP production database is successful before going for restoration process. In this post we will see how to restore Production (PRD) SAP database to Quality (QTY) SAP database.

How to restore SAP Oracle database backup to another SAP system ?

Step 1: First, you need to plan for a offline backup of production SAP database and it should be successful. Make sure that the tapes used for this backup are secure and are inside the library slots for immediate mounting. 

Step 2: Make all the SAP file systems on QTY server like PRD server with  same size (or +1GB % utilize). If filesystems already exist then clean or empty them. Any SAP filesystems will be in the format of 

/oracle/SID/sapdata1
/oracle/SID/orilog1
/oracle/SID/sapreorg
/oracle/SID/saparch1
/oracle/SID/saptrace/usertrace
/oracle/SID/saptrace/background
/oracle/SID/sapcheck
/oracle/SID/sapbackup

Here SID is the Oracle SID - ideally PRD for production & QTY for quality systems. You have to remove any existing data in these filesystems by using rm -rf command (command depends on OS).

Step 3: In this step you have to copy all the TDP SAP configuration files from Production system to the Quality system. The TDP SAP configuration files and their locations are 
  • /oracle/PRD/102_64/dbs/initPRD.sap
  • /oracle/PRD/102_64/dbs/initPRD.utl

You need to copy these files and paste them in the same location in the Quality System by changing their name as shown below

  • /oracle/QTY/102_64/dbs/initQTY.sap
  • /oracle/QTY/102_64/dbs/initQTY.utl
If files with the same name already exists, then rename the old files with another name before copying above files.

Step 4: In TDP SAP, after the database backup (online & offline) completes it generates the log file. For offline the log file extension is (.aff) and for online backup the log file extension is (.anf). Because we are restoring latest offline backup we need to copy the latest .aff file  from production system to quality system. The file location is shown below.

 Copy from /oracle/PRD/sapbackup/brnnfghrk.aff and paste it in /oracle/QTY/sapbackup filesystem.

Step 5: From the same location, we also have to copy the backPRD.log file to the same location in the quality system.

Step 6: Next, we need to change permissions and ownership (dba user) of all the files which are copied in the above steps.

chown oraqty:dba initQTY.sap initQTY.utl
chmod 777 initQTY.sap initQTY.utl

chown oraqty:dba brnnfghrk.aff backPRD.log 
chmod 777 brnnfghrk.aff backPRD.log

Step 7: In this step, we need to open initQTY.sap & initQTY.utl files and change the PRD to QTY. Make sure you change these below important parameters

In initQTY.sap file
util_par_file=/oracle/QTY/102_64/dbs/initQTY.utl    (PRD  → QTY)
compress_dir = /oracle/QTY/sapreorg

In initQTY.utl file
CONFIG_FILE       /oracle/QTY/102_64/dbs/initQTY.bki    (PRD  → QTY)

Step 8: Next, we need to change the node in the /usr/tivoli/tsm/client/api/bin64/dsm.sys file. use the same node name which you have used for taking the production database backup.  You have to make sure that the SERVERNAME in all the files dsm.opt, initQTY.utl and dsm.sys are same.

cd /usr/tivoli/tsm/client/api/bin64/dsm.sys
vi dsm.sys
nodename PRDnode

Step 9: Next, we need to authenticate the TDP node with TSM server. This TDP node name is nothing but the production TDP node name, we have to authenticate PRD TDP node from QTY system.To do this you have to login using oracle user

su - oraqty
cd /oracle/QTY/102_64/dbs
./backint -p initQTY.utl  -f password
or 
su - oraqty
cd /oracle/QTY/102_64/dbs
./usr/tivoli/tsm/tdp_r3/ora64/backint -p initQTY.utl  -f password

Type the TDP node password and press enter. It should successfully authenticate the password for the production node through which you have taken the offline backup.

Note: backint utility is by default located in /usr/tivoli/tsm/tdp_r3/ora64 directory. You can either make a soft link to the /oracle/PRD/102_64/dbs directory or use the whole path name for authenticating TDP node as above.

Step 10: Finally, restoring the backup data, you have to login as oracle user and run the following command to restore whole database.

su - oraqty
cd /oracle/QTY/102_64/dbs
brrestore –m full –b brnnfghrk.aff –p initQTY.sap –c

Note: You can run brrestore utility from anywhere if the environment variable setting is enabled for this utility. Otherwise you need to create soft link from /usr/sap/QTY/sys/exe/run to the /oracle/QTY/102_64/dbs directory.

Commands to restore single database and archivelog files

1) For restoring only single file use the following command

brretore –m /oracle/QTY/sapdata7/btabd_250/btabd.data250 –b brnnfghrk.aff  –p initQTY.sap  –c

2) For restoring one database file use the following command

brretore –m /oracle/PRD/sapdata38/btabd_250/btabd.data250 –b  brnnfghrk.aff   –p initQTY.sap -c

3) For restoring archive files online use below steps
  • Copy archPRD.log to QTY server  
  • Change permission and owner as above
  • su - oraQTY
3.1) Restoring one archive file
brrestore -u system/passw0rd -a 519407  (No. of archive file)

3.2) Restoring multiple archive files
 brrestore -u system/passw0rd -a '519408-519498'  (range of archive files)
Read More


24 April 2014

Quick Steps to configure TSM for Database (TDPOracle & TDPSQL) and TSM for Mail (TDPExchange & TDPDomino) Servers

 ANIL K Y OMMI   Share  Print  Android APP  Save in Dropbox

What is IBM Tivoli Data Protection (TDP) and why we need it ?

How to configure Tivoli Data Protection (TDP)
IBM Tivoli Data Protection (TDP) is one of the family products of IBM Tivoli Storage Manager (TSM) which is used specifically for application level backup and restore functions. It allows us to take the backup of the applications even when the application is in running state, it offers both online and offline application level backups. Through TSM Backup-Archive client we can take only flat file level backup but using TDP’S we can communicate directly with any of the application servers like SQL, ORACLE, R3 SAP, EXCHANGE, DOMINO thorough TSM API and configure the backup, this type of backup is generally considered as a consistent and reliable backup for restoring the application data. In addition, we can also configure TDP clients to take the archive log backups for database and mail applications for point in time restore. You need a separate licenses from IBM to use these TDP products.

Below steps will help you to quickly configure TDP clients and start taking the backup of your applications. It is required to install and configure TSM BAclient software on all the application servers before installing/configuring any TDP Clients.

Quick steps to configure Tivoli Storage Manager (TSM) for Database Servers

With TSM for Database software package you can protect Microsoft SQL Database and Oracle Database servers. Use the following steps to quickly configure TDP clients to protect your databases.

Steps to configure TDP for SQL Databases

  • First,we have to install the TDP SQL Software in SQL application client. After that we will get TDP SQL folder (Program Files/Tivoli/Tsm/Tdpsql). This is the default installation path for TDP SQL. In this folder we will have all the required configuration files. They are TDPSQL.CFG, DSM.SMP (dsm.smp rename it as dsm.opt).
  • Next, we have to edit these file (dsm.opt) with default parameters which are tcpserveraddress, tcpport, nodename, commmethod, include, exclude, passwordaccess generate options.
  • After installation and configuration we will go to TSM server side and we have to create  a new policy domain (or) new management class in the existing domain with the required retention settings.
  • Then we come back to client side and trigger the following command to check the status of the TDPSQL as shown below. 
                Cd C:\Program Files\Tivoli\Tsm\Tdpsql >Tdpsqlc
  • Now we have to check the communication between TDPSQL and TSM Server by using the following command. This command will show all the policy and destination setting of the SQL database backups.
          Cd C:\Program Files\Tivoli\Tsm\Tdpsql >Tdpsqlc q tsm
  • Next step is to authenticate and store the password of the TDP SQL node. You have to register two separate nodes on TSM Server, one for BA-client node and another for TDPSQL. Run the following command to authenticate and store the password for future backup schedules. It will ask old password, new password and verification password. You can skip this step if you have already authenticated it through TDPSQL GUI before.
         Cd C:\Program Files\Tivoli\Tsm\Tdpsql >tdpsqlc changetsmpassword
  • Finally,  we can take backup of the SQL application database. To take the backup you can either use GUI or commandline.  On the commandline run the following command to start the SQL DB backup.
         Cd C:\Program Files\Tivoli\Tsm\Tdpsql>Tdpsqlc backup databasename full

Steps to configure TDP for ORACLE Databases

  • First,we have to install the TDP ORACLE software in Oracle application client. After that we will get TDP oracle folder (Program Files/Tivoli/Tsm/AgentOba). This is the default TDP Oracle installation path in windows OS. In this folder we will have all the required configuration files. They are TDPOCONF.CFG, DSM.SMP.
  • Change to the C:\Program Files\Tivoli\TSM\AgentOBA directory and copy the tdpo.opt.smp file to tdpo.opt. Edit the tdpo.opt file to include these options:
dsmi_orc_config C:\Program Files\Tivoli\TSM\AgentOBA\dsm.opt 
dsmi_log C:\Program Files\Tivoli\TSM\AgentOBA
  • In this same directory, copy the dsm.smp file to dsm.opt. Edit the dsm.opt file to include these options:

COMMMethod TCPip 
TCPServeraddress x.x.x.x 
PASSWORDAccess generate 
NODename TDPnodename
  • Register the node to the Tivoli Storage Manager server with the following command:

REG NODE TDPnodename password maxnummp=n
  • Make sure the Oracle user has the read and write permission to the C:\Program Files\Tivoli\TSM\AgentOBA directory.
  • Change to the C:\Program Files\Tivoli\TSM\AgentOBA directory and run the tdpoconf password command as Oracle user to generate the password file. You will be prompted to enter the password from Step 4 three times.
  • Run the tdpoconf showenvironment command to confirm proper configuration.
  • As Oracle user, run your RMAN backup script with the parameter as specified.

    ENV=(TDPO_OPTFILE=C:\Program Files\Tivoli\TSM\AgentOBA\tdpo.opt) 


            For example:

run {
                             allocate channel t1 type ’sbt_tape’ parms
                                 ’ENV=(TDPO_OPTFILE=C:\Program Files\Tivoli\TSM\AgentOBA\tdpo.opt)’;
                             backup
                                filesperset 5
                                format ’df_%t_%s_%p’
                                (database);
}

Quick steps to configure Tivoli Storage Manager for Mail Servers

With TSM for Mail software package you can protect Microsoft Exchange and IBM Lotus Domino Mail Servers. Use the following steps to quickly configure TDP clients to protect your mail servers

Steps to Configure TDP for EXCHANGE

  • First, we have to install the TDP Exchange Software in Exchange application client.. After that we will get TDP Exchange folder (Program Files/Tivoli/Tsm/TdpExchange. This is the default installation path for TDP Exchange. In this folder we will have all the required configuration files. They are TDPEXC.CFG, DSM.SMP (dsm.smp rename it as dsm.opt).
  • Next, we have to edit these file (dsm.opt) with default parameters which are tcpserveraddress, tcpport, nodename, commmethod, include, exclude, passwordaccess generate options.
  • After installation and configuration we will go to TSM server side and we have to create a new policy domain (or) new management class in the existing domain with the required retention settings.
  • Then we come back to client side and trigger the following command to check the status of the TDPExchange as shown below. 
                Cd C:/Program Files/Tivoli/Tsm/TdpExchange >Tdpexcc
  • Now we have to check the communication between TDPExchange and TSM Server by using the following command. This command will show all the policy and destination settings of the Exchange backups.
          Cd C:/Program Files/Tivoli/Tsm/TdpExchange >Tdpexcc q tsm
  • Next step is to authenticate and store the password of the TDP Exchange node. You have to register two separate nodes on TSM Server, one for BA-client node and another for TDPExchange. Run the following command to authenticate and store the password for future backup schedules. It will ask old password, new password and verification password. You can skip this step if you have already authenticated it through TDPExchange GUI before
         Cd C:/Program Files/Tivoli/Tsm/TdpExchange>tdpexcc changetsmpassword 
  • Finally,  we can take backup of the Exchange mail server. To take the backup you can either use GUI or commandline.  On the commandline run the following command to start the Exchange mail server backup.
         Cd C:/Program Files/Tivoli/Tsm/Tdpexchange>Tdpexcc backup storagegroupname full
  • Three backup types which are commonly used for taking backup of SQL DB are FULL, DIFFERENTIAL and INCREMENTAL backups. 

Steps to Configure TDP for DOMINO Mail servers

  • First,we have to install the TDP Domino Software in Domino application client. After that we will get TDP Domino folder (Program Files/Tivoli/Tsm/Domino). This is the default installation path for TDP Domino.  In this folder we will have all the required configuration files. They are DOMDSM.CFG, DSM.SMP (dsm.smp rename it as dsm.opt).
  • Next, we have to edit these file (dsm.opt) with default parameters which are tcpserveraddress, tcpport, nodename, commmethod, include, exclude, passwordaccess generate options.
  • After installation and configuration we will go to TSM server side and we have to create  a new policy domain (or) new management class in the existing domain with the required retention settings.
  • Then we come back to client side and trigger the following command to check the status of the TDPDOMINO as shown below. 
                Cd C:/Program Files/Tivoli/Tsm/Tdpsql >domdsmc
  • Now we have to check the communication between TDP Domino and TSM Server by using the following command. This command will show all the policy and destination settings of the Lotus Domino backups.
          Cd C:/Program Files/Tivoli/Tsm/domino >domdsmc q adsmserv
  • Next step is to authenticate and store the password of the TDP Domino node. You have to register two separate nodes on TSM Server, one for BA-client node and another for TDP Domino. Run the following command to authenticate and store the password for future backup schedules.  It will ask old password, new password and verification password. You can skip this step if you have already authenticated it through TDP Domino GUI before and stored the         password.
         Cd C:/Program Files/Tivoli/Tsm/domino >domdsmc changetsmpassword
  • Finally,  we can take backup of the Domino Mail server. To take the backup you can either use GUI or commandline.  On the commandline run the following command to start the Domino Mail server backup.
         Cd C:/Program Files/Tivoli/Tsm/domino>Domdsmc sel mail/* -subdir=yes
Read More


Popular Posts

Recent Posts

Random Posts