Question about ADSM Server Capacity

Tammy R. Kilgore
Barnett Bank, NA
904-464-6405
SUBJECT: Question about ADSM Server Capacity

I am currently running one ADSM for MVS server as follows:

ADSM Database:                2,340 MB  71% utilized
ADSM Recovery Log:              800 MB  (Roll Forward Recovery)
ADSM Nodes Registered:          308
Average Nightly Backup:          20 GB
Number of files managed:  3,192,964
Space managed:                  400 GB
Max hour CPU util during backup 50% (of one ES/9021-982 60 MIP engine)
Expiration runs an average of 2 hours once a week
Maximum number of simultaneous ADSM sessions averages around 30
ADSM Region Size (under MVS) 128 MB
Most all of our clients use TCP/IP for connectivity

I will be adding an additional 300 plus nodes over the next year.  I
am trying to determine at what point I should bring up an additional
ADSM for MVS server to help distribute the workload.  I am more
concerned about capacity issues specific to MVS such as virtual storage,
CPU utilization, ADSM database size, etc. as opposed to network
capacity issues.

My questions are:

1. Has anyone had to bring additional ADSM for MVS server(s) to
   handle capacity?

2. If so, what factors caused you to decide to bring up additional
   ADSM server(s)?

3. Which resources under MVS should I monitor to help me determine
   when I should bring up an additional ADSM server to handle the
   workload?

I am trying to be proactive.  I don't want to wait until I have nodes
missing scheduled backups to know I have a capacity problem.

By the way,  I have looked at the ADSM Capacity Planning Tool (Release
1 Level 0.0) and it did not provide me with any useful information.

Thanks,
Tammy Kilgore

****************************************
* IBMLink: SBTTCEU  at ELINK           *
****************************************