The case of the missing numeric ip format in TSM TCPCLIENTADDRESS

As part of the DB2 clustering solution using Tivoli Storage Automation(TSA) there were some customisations required to make the monitoring and backup procedures “cluster aware”. One of the customisations was to facilitate TSM scheduler to point to the active DB2 node. Read more on How to customise TSAMP start and stop scripts to make monitoring ... Therefore if there is a DB2 failover from Server 1 to Server 2 , with all the associated resources failing over, such as ip address, DB2 instance and storage , TSM scheduler can point to the current active node and continue with backups as... Read more →

How to add Virtual IP address to existing Tivoli Storage Automation via db2haicu

Question: I have a Failover solution set up for Shared Disk Storage using Tivoli Storage Automation (TSA). DB2 instances & mount points are set up in the correct resource groups and failing over to another node in the same cluster with success. The one missing piece of the TSA solution is the virtual ip address failover. How can I add a virtual ip that will broadcast the ip address from whichever is the Primary Server? Answer: If you already have a TSA set up , then setting up a Virtual IP address can be configured via DB2 using the db2haicu... Read more →

How to view harvested user defined storage resources for TSAMP

When troubleshooting a db2haicu adding a mountpoint operation , it was necessary to review the resources harvested. This is the first step in trying to figure how TSAMP is viewing the online resources To view the online user defined storage resources harvested use this command: lsrsrc -Ab IBM.AgFileSystem When reviewing the output you'll notice the mount point information. This information is harvested by default from the /etc/fstab details . If a new resource has been added to the system and you want to refresh the IBM.AgFileSystem output use the force method to refresh the list refrsrc IBM.Disk The alternative to... Read more →

How to remove a TSA peer domain

I was installing TSA for a shared storage DB2 clustering , and there were some disk error issues. Rather than spending time troubleshooting dealing with a half installed installation, it was easier to drop the peer domain and start the TSA install again. Making the decision on whether you reinstall or troubleshoot, will depend on your circumstances. It's worth highlighting the TSA uninstall procedure is easy . It then gives you the opportunity to complete any due diligence, bug fixing or other preparatory steps Once the disk error was fixed , these were the steps I completed to delete the... Read more →

How to customise TSAMP start and stop scripts to make monitoring agents cluster aware

I’ve integrated Tivoli Storage Automation (TSA) and DB2 . The solution is based around a two node TSAMP solution which is “automation software”, running as part of a clustered Reliable Scalable Cluster Technology (RSCT) environment. (RSCT is the “cluster software”) Read More on Tivoli Storage Automation for Multiplatforms(SA MP) and the shared disk approach TSAMP uses a set of automation scripts to manage DB2 that is, start, stop and monitor them. TSAMP responds to an unexpected change in state for individual resources (eg DB2 instance failure), a server failure/crash, a network/NIC related outage To confirm the TSA integration with DB2... Read more →