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

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

Chapter 6. Data storage
217
6.1.1 Primary storage pools
In our example solution we set up four primary storage pools: TAPEDATA,
DISKDATA, DISKDIRS, and NONE. Storage pool TAPEDATA must be set up
before storage pool DISKDATA, because DISKDATA refers to TAPEDATA as its
next storage pool.
The examples in this chapter set up the following storage pools:
1. A primary storage pool named TAPEDATA, with device class LTO2-DC. The
pool has collocation by node, and reclamation turned off (set to 100%).
2. A primary storage pool named DISKDATA, with a device class of DISK. It has
an upper threshold of 70% that must be reached for migration to start, and a
lower threshold of 30% that is reached or surpassed before migration stops.
The pool to which data migrated goes is called TAPEDATA. The disk pool
does not cache migrated data.
3. A primary storage pool named DISKDIRS, with a device class of FILE. It has
migration turned off and no next storage pool, keeping the client directory
structure permanently on disk. The pool has collocation by node, ensuring
that clients’ directories will be stored in separate volumes. Note that only
directories from clients where the directories have extended attributes will be
stored in the storage pool. Windows and NetWare clients have extended file
attributes. On UNIX clients, the directory entries are stored directly in the
Tivoli Storage Manager database. The reason for having a separate storage
pool for directories is so that we can guarantee the directories will be stored
on disk, and not require tape mounts when files are restored. If you do not
use the DIRMC client option to specify where directories are stored, they will
be sent to whichever storage pool is pointed to by the management class with
the longest retention period, which might end up being a tape storage pool.
4. A dummy storage pool named NONE that is simply a definition. No data will
be stored in this storage pool, and there are no volumes assigned to it. It is
simply used as a migration destination to prevent warnings when activating a
policy set. See 7.1.3, “Defining management classes” on page 272, for a
further explanation.
6.1.2 Copy storage pools
The example solution has two copy storage pools:
򐂰
OFFDATA for making copies of TAPEDATA to take off-site. OFFDATA is not
collocated, and has reclamation set to 100% to avoid the reclamation process
from starting until our scheduled reclamation. Reuse delay is set to five days.