Chapter 2. Implementation planning
39
2.7.3 Network name resolution
The Tivoli Storage Manager server machine requires a name that clients use to
reference the Tivoli Storage Manager server. If TCP/IP is used, create a Domain
Name Server (DNS) entry for Tivoli Storage Manager itself, as well as a DNS
entry for the machine’s host names. For example, create DNS name TSMSRV1
and use it in the client option files. If Tivoli Storage Manager needs to be moved
to another machine, only the DNS entry needs to be changed, instead of editing
the Tivoli Storage Manager options file for each client. However, using DNS may
impact backup availability if for some reason the DNS service is down (the DNS
name will not get resolved unless availability has been built into the DNS setup).
2.8 Disk considerations and sizing
Tivoli Storage Manager requires disk to operate, to hold the database, logs, and
usually the primary storage pools. In this section we talk about how to choose a
disk subsystem, and how to size the required amount of disk storage capacity.
2.8.1 The disk subsystem
In general, choose the fastest disk subsystem that you can afford. Slow disks
may not be a hindrance for a small implementation, but as the site grows, disk
access becomes a large percentage of the overall elapsed time to complete a
task. Choose a scalable disk subsystem because the vast majority of Tivoli
Storage Manager implementations grow substantially. Multiple I/O paths and
hot-swappable components should also be considered, both for performance
and availability.
2.8.2 Tivoli Storage Manager database
The Tivoli Storage Manager database is critical to the operation of the entire
Tivoli Storage Manager environment. Systems with poorly designed Tivoli
Storage Manager databases tend to run very poorly and rarely meet
expectations. When planning a Tivoli Storage Manager environment, you should
plan enough instances of Tivoli Storage Manager to keep the size of each Tivoli
Storage Manager database reasonable.
The database size depends on how many files are managed with Tivoli Storage
Manager, and whether the files are in a primary storage pool or a copy storage
pool.
Summary of Contents for E16RMLL-I - Tivoli Storage Manager
Page 2: ......
Page 23: ...Figures xxi 22 6 AIX lab environment 708...
Page 24: ...xxii IBM Tivoli Storage Manager Implementation Guide...
Page 32: ...2 IBM Tivoli Storage Manager Implementation Guide...
Page 44: ...14 IBM Tivoli Storage Manager Implementation Guide...
Page 94: ...64 IBM Tivoli Storage Manager Implementation Guide...
Page 96: ...66 IBM Tivoli Storage Manager Implementation Guide...
Page 126: ...96 IBM Tivoli Storage Manager Implementation Guide...
Page 298: ...268 IBM Tivoli Storage Manager Implementation Guide...
Page 354: ...324 IBM Tivoli Storage Manager Implementation Guide...
Page 356: ...326 IBM Tivoli Storage Manager Implementation Guide...
Page 423: ...Chapter 12 Scheduling 393 Week of Month Expire Never tsm quit...
Page 424: ...394 IBM Tivoli Storage Manager Implementation Guide...
Page 510: ...480 IBM Tivoli Storage Manager Implementation Guide...
Page 552: ...522 IBM Tivoli Storage Manager Implementation Guide...
Page 554: ...524 IBM Tivoli Storage Manager Implementation Guide...
Page 594: ...564 IBM Tivoli Storage Manager Implementation Guide...
Page 612: ...582 IBM Tivoli Storage Manager Implementation Guide...
Page 618: ...588 IBM Tivoli Storage Manager Implementation Guide...
Page 720: ...690 IBM Tivoli Storage Manager Implementation Guide...
Page 752: ...722 IBM Tivoli Storage Manager Implementation Guide...
Page 758: ...728 IBM Tivoli Storage Manager Implementation Guide...
Page 780: ...750 IBM Tivoli Storage Manager Implementation Guide...
Page 802: ...772 IBM Tivoli Storage Manager Implementation Guide...
Page 823: ...Index 793 Z z OS tape management 58 zOS 200...
Page 824: ...794 IBM Tivoli Storage Manager Implementation Guide...
Page 825: ...IBM Tivoli Storage Manager Implementation Guide...
Page 826: ......
Page 827: ......