ADSM-L

ADSM Capacity

1997-01-16 16:55:13
Subject: ADSM Capacity
From: "Pittson, Timothy ,Corp/US" <tpittson AT HIMAIL.HCC DOT COM>
Date: Thu, 16 Jan 1997 16:55:13 -0500
>Jane,
>
>1.  I have max sessions set to 60.
>
>2.  When we ran ADSM on MVS, I had 3 ADSM started tasks, 1 for 'onsite'
>backups,. 1 for 'offsite/disaster recovery' backups, and a test server for
>testing server maintenance.  We were an early implementer of ADSM and the
>lack of d/r tools in version 1 forced me to create a separate 'offsite' ADSM
>server since, at the time, most of our servers only needed weekly offsite
>backups.  By the time version 2 came along, the decision had already been
>made to migrate to AIX so I kept things the way they were, even after
>upgrading to ADSM Version 2 on MVS.   There are a couple of other reasons I
>could think of for creating separate ADSM servers...
>
>       - Workload - ADSM can only run on one processor under MVS.. we had 
> basically
>maxed out our 'onsite' server (ran at 100%
>          CPU all night) and, if we were to have stayed on MVS, I would've had 
> to
>split it up into multiple servers.  At that time, our
>          database was about 8 GB and we were backing up 20-30 GB per night.
>       - Critical/Non-critical workload - I could see making a case for 
> creating a
>separate ADSM server for critical clients (servers,
>         database backups, etc.) versus one for less critical clients
>(workstations, test servers, etc.)  This would also help facilitate
>         disaster recovery as the 'critical' ADSM server could be recovered 
> much
>more quickly, especially if you're backing up many
>         workstations and tracking millions and millions of workstation files 
> in
>your database.  This could also allow you to prioritize
>         one ADSM server over another (via dispatching priority, performance 
> group,
>etc.)
>
>3.  Very subjective... not sure if there's a cut and dry answer to this
>
>Hope this helps...
>
>Tim Pittson
>tpittson AT himail.hcc DOT com
>
>----------
>From:  Jane Dagostino-Snyder[SMTP:j-dago AT ngwmail.ais.umn DOT edu]
>Sent:  Thursday, January 16, 1997 3:54 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       ADSM Capacity
>
>This is a grab bag of questions and how are the other ADSM folks
>environment look like:  Thanks to those that responded to my file restore
>question today.
>
>1) The Max session is set in the server options file for multitasking so
>multiple clients can backup while other server tasks are running,  The
>default is 25, although documentation states this is only limited by
>available virtual memory size or communications resources, I am
>wondering what is the overall setting for this, what at range is used and
>what range is used most?  What is yours set to?
>
>2) I have read on this list that some sites run more than one ADSM task
>on MVS, like say 2 or 3.  Why would one do this?   I have an idea but
>wondering how close I am.  My thoughts are that one, you want to keep
>your database a certain size,   2), maybe different types of data, critical
>verses non-critical are being backed up to separate ones?   Please could
>someone respond as to the reasons why you run more than 1 server on
>MVS host?
>
>3) If in number 2 question, statement number one is correct, how big
>should you allow your database to get before you 'put up' a second
>ADSM on MVS?   Is this when you reach a certain number of nightly files
>equal to ?? or when a database reaches a certain size or what?
>
>Thank you to any one that can answer any part or all of these questions.
>Jane Dagostino-Snyder
>
>
<Prev in Thread] Current Thread [Next in Thread>
  • ADSM Capacity, Jane Dagostino-Snyder
    • ADSM Capacity, Pittson, Timothy ,Corp/US <=