There are quite a few options you can look into. CNT builds protocol
converters that you can use to convert FCP <-> IP <-> FCP (fiber channel
protocol) and accomplish data mirroring via a WAN connection. Other DWDM /
Dark Fiber options exist too, and can play well with the larger disk
subsystem's software based copy services such as PPRC (IBM) and SDRF (EMC).
Collectively, these are all high cost solutions, but offer lots of
flexibility and HA type configurations. Other, less expensive methods/tools
probably exist too--

From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Offsite Mirror of TSM server
Date: Fri, 19 Apr 2002 11:02:44 -0400

Well, that is the issue/alternative/suggestion.

Just exactly how do we mirror a "volume" across an IP link, since that is
going to be the most likely connection between the "source" and the
"target"/"mirror" ? What hardware/software would I need to be able to do
this and how would the TSM server feel about this processes (it is going
to be a lot slower to mirror across a 100mbs link that physical DASD !!).






Jim Healy <James.Healy AT AXA-TECH DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/19/2002 10:48 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Offsite Mirror of TSM server


Why not mirror the TSM logs/DBs to the hotsite, when the source server
fails bring up the target server pointing to the mirrored DB/logs?




"Zoltan Forray/AC/VCU" <zforray AT VCU DOT EDU>@VM.MARIST.EDU> on 04/17/2002
01:46:11 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:  Offsite Mirror of TSM server


Let me preface this with, I am not sure how to completely ask these
questions since I don't have all of the details but hopefully someone can
give me some idea of how TSM can/will handle this, if at all possible.

Current configuration:  TSM 4.1 on OS/390 using 3590B tape drives in a
3494 ATL

Requirements as I understand them:  Setup a off-location "hot site" backup
TSM server that will have copies of everything the main server and/or
other TSM server (we are working on splitting the TSM traffic/load onto
another TSM server) has.   The "hot site" server will probably be an AIX
box with 3590E (possibly FC) drives.

I have looked into the source/target server issue but am a little confused
since the "target" server will only see things that come from the "source"
server as archive objects.

If the building with the "source" server burns down (and this same
building also houses a majority of the clients that are backed up !), how
would the "target" server be used to restore all of the client nodes ?

How about the database backups that are sent to the "target" server ? What
use are they if you have to have the "source" server to identify what is
on the "target" server ?

Should I/could I setup database mirror volumes on a remote (target ?)
server over simple IP connections or is this only possible with DASD using
XRC processes....especially since the current, main database is on OS390 ?
    If this was moved to an AIX box, how would this be handled ?  NFS ???

As you can tell, any and all guidance is greatly appreciated !!!
----------------------------------------------------------------------------------------------------

Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: zforray AT vcu DOT edu  -  voice: 804-828-4

_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com