Hi

I would recommend using only 2 active instances, one on each machine. For 
example, you have server 'S' at main site and server 'T' at off-site. 'S' backs 
up to 'T' and vice versa.

I would also recommend (to speed up recovery in the event of loosing a TSM 
server) that you prepare server 'S' for housing server 'T' and vice versa. This 
can easily be done by placing server 'T's configuration files in a separate 
folder on server 'S' and the other way around. You should also make sure that 
you have some sort of routines for copying the files between the two servers so 
that the files are always updated.

A setup could look like this:

On each machine, create a separate folder for each server instance

/itsm/serverS - Holds server 'S''s configuration files. Server 'S' is 
configured to use port 1500 and 1580.

/itsm/serverT - Holds server 'T''s configuration files. Server 'T' is 
configured to use port 1600 and 1680.

This way, you can relatively quick get the lost instance up and running fast on 
the other server, without interrupting operation of the "home" instance.

Best Regards

Daniel Sparrman

-----Ursprungligt meddelande-----
Från: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] För Keith 
Arbogast
Skickat: den 22 januari 2008 16:13
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Re: 2nd TSM Instance Question

Could I ask a variation of this question?

What about the case where server 'S' at the local (to me) data center
is the source server, and server 'T' at a distant data center is the
target server for server-to-server backups from the local data
center; while server 'T' at the distant data center is the source
server, and server 'S' at the local data center is the target server
for server-to-server backups from the distant data center?  There
will be a TS3500 (3584) ATL with ALMS at each data center.

In this case, would the management be easier or harder with two TSM
server instances on both physical servers?  One for the source
functions and the other for the target functions.

With my thanks,
Keith Arbogast
Indiana University