ADSM-L

Re: ADSM system scaling

1999-12-16 11:10:16
Subject: Re: ADSM system scaling
From: Mahesh Tailor <MTailor AT CARILION DOT COM>
Date: Thu, 16 Dec 1999 11:10:16 -0500
My two cents worth . . .

1) You state that your clients are connected via 100BT or TR.  Are the
clients and server in the same physical location?  Or are they at locations
that are ATM attached to the location where the ADSM server is located?  If
they are what would the chances be of converting the clients to ATM?  Once
you get them connected via ATM, create a separate ELAN for backups only.
Configure the ELAN for IP traffic only (assuming all your clients are using
IP to the server) - so you can eliminate all other protocols and unnecessary
broadcasts.  Make the server and the clients members of the backup-only
ELAN.  This should give you better network throughput.  (You also eliminate
the traffic going through a router - 100BT/TR -> router -> ATM reducing your
router utilization.)

2) I agree with Steve, Add another server.  Increase your disk storage pool
on your existing server.  Also, how are your filesystems setup?  Move your
database and log files onto separate filesystems that exist on different
PV's (preferably on a separate controller).  Also, increase the memory on
your existing server.

Hope this helps.

Mahesh Tailor
WAN Administrator
Carilion Health System
Voice: 540-224-3929
Fax: 540-224-3954

>>> Steven Thornhill <steve_thornhill AT UK.IBM DOT COM> 12/16 10:44 AM >>>
Personal opinion is to double up on the number of ADSM servers. Split the
tape
drives across two machines will increase the data throughput. Also this
will
give you a little more resiliance.

Steve Thornhill - IBM ETC
Int       - 255104
Ext      - 01705 565104
Mob   - 0378 289770
Email - steve_thornhill AT uk.ibm DOT com


"Patten, Stacy H." <shpatten AT SAINTFRANCIS DOT COM> on 16/12/99 15:18:22

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Steve Thornhill/UK/IBM)
Subject:  ADSM system scaling




Having never scaled an ADSM setup I would appreciate input for our
situation:

Current Hardware:
        1 - H50  -512MB / 1-300MHz
        24GB disk pool
        1 - 3494 Library w/ 3 3590 drives
        1 - ATM NIC (emulating token ring)
        1 - 100BT NIC (not currently in use)

Current Backup:
        148GB

We expect that by Dec 2000 we will be at 542GB a night.  We barely make
the
current backup routines, and this number will increase to 223GB with the
addition of Exchange, SQL, and ORACLE clients.  Our backup window 10:00pm
to
6am so we should have plenty of time to perform this, with the exception
of
migration consuming our tape drives twice a night.  Our servers are on
different subnets, so the backup traffic goes across our ATM backbone and
back before it hits the ADSM server.  Also, most of our servers are
running
100BT ether with some on 16MB token ring.  We have (over?)estimated the
following hardware setup to hopefully solve our capacity issues until at
least the end of 2000.

Proposed Hardware:
        1 - H50 - 1GB / 2-300MHz
        150GB disk pool
        1 - 3494 Library w/ 8 3590 drives
        2 - ATM NIC (emulating token ring & ethernet)

Is this enough machine?
Is this enough disk pool?
Is this enough tape drive?
Is this enough bandwidth?



Stacy Patten

Senior Network Engineer
St. Francis Hospital
phone- 918-494-9465
pager- 918-646-8497
email- shpatten AT saintfrancis DOT com
<Prev in Thread] Current Thread [Next in Thread>