12.07.2015 Views

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Enabling <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> Web client access in aCluster EnvironmentIf the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> Web client access is needed during a failovercondition, you must configure the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> Web client acceptordaemon (CAD) associated with the cluster to failover along with the clusterresource.After you have completed the configuration steps described in the Configuring thebackup-archive client in a cluster environment section, per<strong>for</strong>m the additional stepsdescribed below to complete the Web client access setup:1. Set up the CAD to manage the Web client <strong>and</strong> scheduler. <strong>Tivoli</strong> <strong>Storage</strong><strong>Manager</strong> CAD should be set up to manage schedulers as well as Web clientaccess. This reduces the number of daemons that need to be configured ascluster applications <strong>and</strong> thus simplifies the configuration <strong>and</strong> administration.When a failover occurs, the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> CAD starts on the nodethat is managing the takeover.2. Update the managedservices option in the system options file dsm.sys on eachnode <strong>for</strong> each server stanza, as shown below <strong>for</strong> NodeAServername clinton_NodeAnodenameNodeAcommmethod tcpiptcpp 1500tcpsclinton.sanjose.ibm.comtcpclientaddres nodeA.sanjose.ibm.compasswordaccess generatepassworddir /A1/tsm/pwdschedlogn /A1/tsm/dsmsched.logerrorlogname /A1/tsm/errorlog.logmanagedservices webclient schedule3. Set up the CAD to use a known http port. By default, the CAD uses http port1581, when available, <strong>for</strong> the Web client access. If this port is not available, theCAD finds the first available port, starting with 1581. In a failover condition ofan active-active cluster configuration, a failover cluster host system will likelybe running multiple instances of the CAD. If default settings are used <strong>for</strong> thehttp port, the failover node will use any available port <strong>for</strong> the CAD being failedover, since the default port will likely be in use by the failover host’s currentCAD processes. This causes problems <strong>for</strong> the Web client associated with theCAD that failed over, as the new http port will not be known to the Web clientusers. You might use the httpport option to specify the specific ports <strong>for</strong> theWeb client access <strong>for</strong> each resource. This allows you to always use the sameport when connecting from a web browser, independent of the node servingthe cluster resource. Add the httpport option in the system options file(dsm.sys) on each node <strong>for</strong> each server stanza as follows, making sure that eachstanza uses a unique value:76 <strong>IBM</strong> <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> <strong>for</strong> <strong>UNIX</strong> <strong>and</strong> <strong>Linux</strong> <strong>Backup</strong>-<strong>Archive</strong> Clients Version 6.1: Installation <strong>and</strong> User’s Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!