ADSM-L

Re: Multiple instance of TSM running on the same server with its own binaries?>

2005-08-29 12:25:41
Subject: Re: Multiple instance of TSM running on the same server with its own binaries?>
From: William Colwell <bcolwell AT DRAPER DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 29 Aug 2005 12:25:09 -0400
Hi Tae,

I install multiple copies of the software for the reasons you listed.
But I am running on Solaris and the needed tweaks to the process aren't that
hard.
I don't know what is involved with tweaking the install on aix.

I have been doing this for 2+ years and installed versions 5.1, 5.2 and 5.3
Without any complications, plus many interim fixes.

As far as being supported goes, that is not clear;  The relevant text in the
Quick start manual is -"Do not attempt to install the server executable
files
in more than one directory."  Some may say that means it is unsupported, but
Since there is no explicit "this is not supported" phrase I think it is
unclear.

In any case, what would be unsupported - the install process or the
execution of the
Servers after successfully installing it this way?

I have called in many problems and this has never been an issue.

Hope this helps,

Bill Colwell

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
> On Behalf Of Tae Kim
> Sent: Thursday, August 25, 2005 2:03 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Multiple instance of TSM running on the same
> server with its own binaries?>
>
> Was looking to do this because of
>
> 1. Upgrade of the TSM binary will not upgrade all of TSM
> servers at Once.
> If I want to apply a patch I can try it on one TSM server that is less
> critical and run it for couple of days before applying it to
> other servers
> (don't have QA box with 100's of clients and a separate .
>
> 2. Down time can be managed more efficiently. It is hard to coordinate
> shutdown of TSM server for a extended amount of time because
> of TDP domino
> and oracle backs ups (backing up archive and recovery logs).
>
> 3. Less experienced Admins might do something funky to the
> directory or
> files that TSM instance is running off of.
>
>
> but its not IBM supported so I guess I have no choice
>
>  =(
>
>
>
>
>
>
>
> "Allen S. Rout" <asr AT UFL DOT EDU>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 08/25/2005 12:08 PM
> Please respond to
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> Re: [ADSM-L] Multiple instance of TSM running on the same
> server with its
> own binaries?>
>
>
>
>
>
>
> ==> On Thu, 25 Aug 2005 10:41:20 -0400, Tae Kim <Tae_Kim AT MCKINSEY DOT COM>
> said:
>
>
> > I am in a process of splitting up my TSM 5.2.2.4 server on
> AIX 5.2 ML5
> and I
> > was wondering if anyone uses separate binaries for each TSM
> instances
> that
> > are on the same physical server.  I know that multiple TSM
> instances can
> > share the same binary but I would like to use different binaries for
> > different TSM instance.
>
> Why?
>
> In order to accomplish this, you're going to have to install
> a set of TSM
> BFFs, and then copy things somewhere else, then install a
> different set.
> I'll
> bet you my whole $.02 that IBM regards this as an "unsupported
> configuration".
> I don't know exactly where you'll see problems with it, but I bet you
> will.
>
> Furthermore, when you encounted even a normal problem, I'd
> anticipate that
> IBM
> support would positively freak out.
>
> I've been doing multiple TSM servers on the same hardware for almost 2
> years
> now, the documented procedures work quite nicely.  My
> recommendation would
> be
> to reconsider your plan.
>
>
>
> - Allen S. Rout
>
>
>
>
> +=========================================================+
> This message may contain confidential and/or privileged
> information.  If you are not the addressee or authorized to
> receive this for the addressee, you must not use, copy,
> disclose or take any action based on this message or any
> information herein.  If you have received this message in
> error, please advise the sender immediately by reply e-mail
> and delete this message.  Thank you for your cooperation.
> +=========================================================+