204
IBM Tivoli Storage Manager Implementation Guide
Tivoli Storage Manager copy volumes must have at least the same capacity as
the original volumes. If your database consists of eight volumes of 1 GB each,
you will need eight more 1 GB allocated volumes to completely mirror the
database. If you create volumes larger than necessary, Tivoli Storage Manager
gives a warning message (ANR2253W for database and ANR2273W for the log),
but still allows you to use the allocated volume. The extra capacity will be
wasted). We recommend creating all copies of each volume at the same size.
You should mirror all or none of the volumes—there is no point in only mirroring
some of them.
Use separate disks for each of the volumes in a mirrored set, so that you do not
lose data if one disk fails. Although you can technically place primary and mirror
copies on the same disk, this is also a waste of space and will probably even
decrease performance because of disk head contention.
When using two-way mirroring, we recommend using four disks for the database
and recovery log volumes to keep each set of volumes on a separate disk. If you
can, go one step further and ensure that the disks are on separate controllers. In
a SAN environment, your disks will probably be virtualized, and running separate
controllers for each LUN is not likely.
Table 5-1 shows an example of database and recovery log directories for
UNIX/Linux and Windows, respectively. We assume that the four UNIX/Linux file
systems are built on separate disks.
Table 5-1 Database and recovery log volume placement on four disks
If four separate disks for your database and recovery log volumes are not
possible, we recommend a minimum of two separate disks. In this way, you can
place primary database and mirror log volumes on one disk, and primary log and
Type of volume
UNIX file system
mount points
Windows location
Database volumes
/tsm/database/primary
D:\TSMDATA\DBP
Mirrored database volumes
/tsm/database/mirror
E:\TSMDATA\DBM
Log volumes
/tsm/log/primary
F:\TSMDATA\RLP
Mirrored log volumes
/tsm/log/mirror
G:\TSMDATA\RLM
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: ......