ADSM-L

deployment of 35,000 ADSM clients

1995-08-28 13:40:25
Subject: deployment of 35,000 ADSM clients
From: Greg Tevis <gtevis AT VNET.IBM DOT COM>
Date: Mon, 28 Aug 1995 10:40:25 PDT
A couple more thoughts on deploying large numbers of ADSM clients.
Use of multiple servers would certainly be reasonable with this
number of clients.  You may even choose to deploy ADSM servers in
different locations within your network to handle communities of
clients.  This would be driven by your network, server I/O and CPU
capacities, geographic locations of clients/servers (preferably your
clients and their server should be geographically separated by
room, bldg,...etc).  Having multiple servers will also help keep
your ADSM database size down which helps server performance.

For servers with large numbers of clients you may also wish to
exploit multiple policy domains and multiple storage pool hierarchies
to facilitate control.  For example, you
may want to designate priority clients (eg, file servers) which go to a
special policy domain and storage pool hierarchy...these clients could
get priority scheduling and use colocation to help recovery.  For the
workstation masses...Bill Colwell's suggestion of turning colocation
off is definitely the way to go.

One final thought is that you want to make sure you carefully consider
your client options file...this should be set up generically so
each new client can just modify the nodename and start running.
In particular, the include/excludes should be used effectively...you
want to exclude backup (by thousands of clients) of operating system
and standard application code.  These should be excluded, backed up
once, and then made available to all clients through a generic
grant access.

Greg Tevis
ADSM Technical Support
<Prev in Thread] Current Thread [Next in Thread>
  • deployment of 35,000 ADSM clients, Greg Tevis <=