I was also intrigued by the comments of an ADSM system that was managing
50TB of data.  So, I went and looked at our configuration and found:
*we manage only 500-G-B of data across multiple platforms with the
server being on MVS mainframe
*our DB (no mirror by the way) is 6.3GB
*our recovery log (no mirror) is 1.7GB
*our DASD backuppool is 17GB

We are still V2 and I know that V3 offers some performance improvements,
but we do have a concern with the fact that managing the ADSM system is
a 24hour process (in other words we don't have a great deal of idle
time) and that we use between 12-20MIPS during our peak daytime period
of 09:00-10:00.  The overview of our scheduling is:

*20:00 -> 05:30 is server backup time (at 02:00 we have a copy to our
vault copypool; unload of our DASD backuppool to cart; and incremental
DB backup)
*06:00 -> 08:00 is another copy; unload; DBbackup
*08:00 -> rest of day is the update volume, reclaims, expiration, etc.

It's inconceivable to me that 50TB of data could be managed at
all?????????

> -----Original Message-----
> From: Wendrock, Richard O [SMTP:wendrro AT TEXACO DOT COM]
> Sent: Wednesday, February 11, 1998 9:23 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Large systems
>
> We are trying to decide between Lagato and ADSM on MVS.  Although it
> appears
> that ADSM has a superior architectural design, we are concerned about
> the
> scaleability of ADSM on MVS.
>
> I was intrigued by the comments of a day ago about 50 TB ADSM systems.
> We
> are looking at supporting 10 TB. on various servers all being backed
> up by
> ADSM on MVS.
>
> Are you doing that?  if so, how much data is supported? and what does
> your
> ADSM configuration look like?(i.e. are you using more than one ADSM)
>
>
>
> Regards,