Defining different TSM options for multiple DB2 instances
I had been struggling with an obscure problem recently. I needed to set up several DB2 instances on a Microsoft Cluster Server and configure them for TSM backup and log archiving. That would have been a relatively easy task if it were not for the fact that those instances belonged to different cluster resource groups. Each group had its own virtual IP address and host name, and could be brought online or moved to another cluster node independently. For this reason each resource group required a separate TSM node defined for it, which, in turn, called for a separate set of TSM configuration options.