Dunno if the 3494 can take 2 nics or not.
I like the previous poster's suggestion to use a serial connection, that
will get you around the firewall problem.

But even so, that doesn't get you drive sharing, only robot sharing.
Buying drives for the 3494 is $$painful.

Still think you will come out cheaper to look at partitioning the 3583 or
3584, LTO drives cost much less.



-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:zforray AT VCU DOT EDU]
Sent: Monday, February 09, 2004 3:51 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Configuration and Expansion questions


Well, I think we sorta figured we would have to "break the rule" by
connecting the "isolated TSM server" to the 3494 LM. However, will the
3494LM handle multiple, different network connections (i.e. from two
different networks/subnets since the existing TSM AIX system is already
connected via a private subnet) !

Will I need to buy additional features/connection to the 3494 ?





"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/09/2004 02:01 PM
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Configuration and Expansion questions


Hi Zoltan...

That's a stumper.   I'll throw out a guess for people to stab at.

Appears to me that the 3494 is not an option.

Your Windows TSM server will need to communicate with the 3494 via LAN
(TCPIP), just as your AIX box does.  Or with TSM  library sharing, it has
to
communicate with the other AIX TSM server (the library master) via TCPIP.
I
don't see how that would work if the Windows TSM server is outside the
firewall?

I believe you could make it work by physically sharing the 3494, if you
added NIC cards to the AIX & Windows box and set up a "3494-net", where
only
the AIX host and the Windows host and the 3494 were on that network
segment,
but that would require more E1A drives dedicated to the Windows host, in
addition to the NICS ....(very costly).

Maybe I'm making this more complicated than it has to be, but I would look
into physical partitioning of the 3583, available on the later 3583
models.
That would give you a solution that doesn't require TCP/IP, avoiding the
firewall issues.

Also beware, make sure you will have sufficient cartridge capacity in the
3583 - the "(and growing)" in your post makes me think 72 slots might not
be
enough for TWO systems of indeterminate size.  You may need to go to the
3584.

OK, somebody else shoot it down...





-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:zforray AT VCU DOT EDU]
Sent: Monday, February 09, 2004 1:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Configuration and Expansion questions


We are working on expanding our TSM systems with additional TSM servers,
libraries, etc.

Here is what we have right now and where we are heading....

(1) TSM on ZOS using IBM 3494 ATL
(2) TSM on AIX sharing the 3494 but using its own 3590E1A drives attached
to a SAN via FC

New system #3

TSM on AIX (primarily for IMAGE and mail systems/Notes/Domino backups)
with a 3583-L72 LTO2 library

New system #4

The need has arisen for a new TSM server, dedicated to backing up 17 (and
growing) systems/servers (sizes unknown......don't ask). The reason for a
new, separate TSM server is due to firewall issues/requirements. The TSM
server is going to be behind the firewall with NO outside access (I will
have to physically walk to and directly access the TSM server. No internet
access....no dual-heading......).

To make things simpler/cheaper, we are proposing #4 to be an x86 box with
WINDOWS 2003 server (thought about Linux but I think the issue was the
availability of an FC card for it). We want to access/share the 3590E1A
drives and/or the LTO2 library.

What are you thoughts on this ?

Anyone have this kind of configuration ?

Is this possible/workable ?

What will I need, software wise from TSM ?  Library Sharing (never done
one of these !).