In 3.1.2.41,  application limitations forced it.

1.      Recovery log max was 5 Gigs.  Some of our database transactions take
hours to complete and the server log was filling totals during a 2 hour
window.  (ie: a 40 Gigs Dbspace from and Informix client)
2.      Database buffer on each crashes the database instance when over 1
Gig.
3.      One recovery log as opposed to multiple like any current generation
database.  Multiple logs could prevent a long transaction from crashing the
ADSM server database instance.
4.      3 separate database with 2 disk arrays as the database each seem to
handle a lot more clients than 1 database instance with 6 database disk
arrays.
5.      Once we got 300 clients on a server instance, ADSM started having a
lot of internal issues ... some related to database buffer prefetching.

        If ADSM could handle it, I would have a single ADSM instance on a
single server and eliminate all hardware bottlenecks, but at 3.1.2.41, ADSM
can't handle 1000 clients on a server tracking 200 million files and getting
1 Terabyte per day.  The UNIX server built handles it fine.

        The major limitation is the ADSM database ... it needs to be
redesigned or ported to a robust database such at Informix of Oracle ...
maybe since they bought Informix they will. I doubt it though.  On those
database, you can give the database 6 gigs of memory and cache most
everything.  Eventually, I would like to put the entire database in memory.

Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.

WAL-MART CONFIDENTIAL


        -----Original Message-----
        From:   Lindsay Morris [SMTP:lmorris AT SERVERGRAPH DOT COM]
<mailto:[SMTP:lmorris AT SERVERGRAPH DOT COM]>
        Sent:   Wednesday, May 09, 2001 12:22 PM
        To:     ADSM-L AT VM.MARIST DOT EDU <mailto:ADSM-L AT VM.MARIST DOT EDU>
        Subject:        Re: Multiple TSM* Servers On Same Machine

        Well, you're right.  Server consolidation is a good thing.

        But I usually (for simplicity) try to have one machine with one TSM
server
        doing all the work.  Why do you need several different instances of
TSM on
        the same box?  Why not just have one instance?


        -----Original Message-----
        From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
<mailto:[mailto:ADSM-L AT VM.MARIST DOT EDU]> On Behalf Of
        Jeff Bach
        Sent: Wednesday, May 09, 2001 12:22 PM
        To: ADSM-L AT VM.MARIST DOT EDU <mailto:ADSM-L AT VM.MARIST DOT EDU>
        Subject: Re: Multiple TSM* Servers On Same Machine


        1.      Less hardware to manage
        2.      SCSI tape resources can be shared
        3.      DISK resources can be moved between instances without an
outage
        4.      Multiple interfaces can be shared
        5.      One TSM server license
        6.      Can be implemented in a few hours
        7.      Works around application bottlenecks
        8.      Cheaper

        DIS
        1.      Harder to upgrade
        2.      Memory allocation can be an issue


                -----Original Message-----
                From:
Robert_K_Miller/Lancaster/Corporate/Armstrong AT ARMSTRONG DOT COM
<mailto:Robert_K_Miller/Lancaster/Corporate/Armstrong AT ARMSTRONG DOT COM>
        [SMTP:Robert_K_Miller/Lancaster/Corporate/Armstrong AT ARMSTRONG DOT 
COM]
<mailto:[SMTP:Robert_K_Miller/Lancaster/Corporate/Armstrong AT ARMSTRONG DOT 
COM]>
                Sent:   Wednesday, May 09, 2001 10:42 AM
                To:     ADSM-L AT VM.MARIST DOT EDU <mailto:ADSM-L AT VM.MARIST 
DOT EDU>
                Subject:        Multiple TSM* Servers On Same Machine

                Hi all,

                Why would one put multiple TSM servers on a single machine?
                What are the advantages and disadvantages? What are the
                scenarios?

                History:
                We have one AIX system with one TSM server with two
libararies
        attached.

                Robert Miller
                Armstrong



**********************************************************************
        This email and any files transmitted with it are confidential
        and intended solely for the individual or entity to
        whom they are addressed.  If you have received this email
        in error destroy it immediately.

**********************************************************************