>Does anyone run, or know someone that does, a TSM version 6 server on a 
>cluster of some sort?  There's a ton of documentation on using TSM clients 
>with clustered servers, but as far as clustering the >TSM server application 
>itself I'm drawing a blank.  It wasn't so hard with version 5 but version 6 
>doesn't seem to want to play ball - any advice sought.


We are using:
- AIX 5.3-09-05;
- HACMP 4.X before and PowerHA 5.X now;
- TSM Server 5.X and 5.4.4.1 now;
- TSM database and logs on SSA before and on SAN (IBM DS8100) now;
- primary DISK pools on SSA and SAN before (migrated to FILE pools as 
aprepation for 6.X upgrade);
- primary/copy DISK pools on SAN;
- copy pools on SCSI libraries.

Hardware configuration:
- two AIX servers as HACMP cluster nodes (active and passive);
- two HBA adapters on each server with connections via fiber optics switch;
- two SSA adapters on each server (each couple in the same SSA loop);
- a few SCSI differential adapters for tapes connected to differnt ports on 
each SCSI library.

TSM Server has been tested many times without any problems (HACMP: stop TSM 
server, release all resources on SAN/SSA/SCSI/Ethernet, activate all resourses 
on other server, start TSM Server).
Of course, all active sessions and processes are killed on the first server 
during failover, but they can be restarted after activation on the second 
server.

________________________________________

Please consider the environment before printing this Email.

"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."