IBM E16RMLL-I - Tivoli Storage Manager, Руководство по внедрению

Страница: 64 / 828

34
IBM Tivoli Storage Manager Implementation Guide
faster I/O subsystem increases. Separate controllers or adapters for disk and
tape devices become essential as the load increases.
Memory is used to cache database entries, among other things. As the number
of files being managed increases (and thus the database size increases), the
amount of memory that Tivoli Storage Manager requires increases. zSeries
users note that Tivoli Storage Manager likes to keep a large part of its address
space in real storage. Since memory is relatively cheap, and you will never regret
having too much memory, we recommend starting with a minimum of 1 GB and
increasing from there.
2.6 Multiple Tivoli Storage Manager servers
When first setting up a Tivoli Storage Manager environment, we recommend
implementing a single server. Once experience has been gained, and the
implementation has grown enough to be reaching the capacity of the current
server model family, a second server may be considered. We recommend
upgrading your current server hardware to its next larger model before
considering a second server, because this will keep the management overhead
smaller. Tivoli Storage Manager can handle very large amounts of data or clients
in one implementation. Currently, we have seen implementations with Tivoli
Storage Manager internal server databases of 80 GB and larger (admittedly on
very powerful, large platforms).
2.6.1 Reasons to consider multiple servers
Multiple Tivoli Storage Manager servers can be configured to provide some
redundancy and disaster recoverability in the event of a Tivoli Storage Manager
server outage. For example, a company with two well-connected sites, A and B,
may decide to install a Tivoli Storage Manager system at each site. The system
at site A would back up the client data from site B and vice versa. The loss of site
A would mean that the Tivoli Storage Manager system at site B (which holds the
backup data for site A) could immediately start restoring the client systems onto
replacement equipment. The server at site A (which was lost) could be recovered
to the server at site B.
The virtual volumes and Enterprise Administration capabilities of Tivoli Storage
Manager make managing multiple servers easier by centralizing some
administration functions and allowing changes to be replicated on some or all
systems.
For very large or critical clients such as a large, enterprise-wide business
intelligence complex, a dedicated Tivoli Storage Manager server (either on the
same system or a different one) might be the best solution.