Table of Contents
Advertisement
------------------- ----------------------------------------------------------
02/23/2006 16:22:25 ANR2017I Administrator ADMIN issued command: AUDIT VOLUME
02/23/2006 16:22:25 ANR0984I Process 35 for AUDIT VOLUME (REPAIR) started in
02/23/2006 16:22:26 ANR1199I Removable volume 031AKK is required for audit
02/23/2006 16:22:26 ANR8324I LTO volume 031AKK is expected to be mounted (R/W).
02/23/2006 16:28:13 ANR2312I Audit Volume (Repair) process started for volume
02/23/2006 16:28:13 ANR8340I Removable volume 031AKK mounted.
02/23/2006 16:28:13 ANR0512I Process 42 opened input volume 031AKK (SESSION:
02/23/2006 16:38:14 ANR4132I Audit volume process ended for volume 031AKK;
02/23/2006 16:38:14 ANR0987I Process 42 for AUDIT VOLUME (REPAIR) running in
02/23/2006 16:38:14 ANR0514I Session 110 closed volume 031AKK. (SESSION: 110)
6.5.3 Back up a storage pool
The backup stgpool command backs up a primary storage pool to a copy pool. If
the primary storage pool is a tape storage pool, two physical drives will be
required. The input volume from the primary storage pool will be mounted in one
drive, while the output volume from the copy storage pool will be mounted in the
other. The two drives can be in the same or different libraries. To back up a
random access storage pool to a copy storage pool requires only one drive.
Typically, the storage pool backup process is automated. We describe how in
12.2.1, "Defining an off-site backup schedule" on page 377.
Backing up from a disk pool is generally quicker than backing up from a tape
storage pool. However, current generation LTO3 drives on a SAN can
outperform disks when streaming. We recommend that you perform your storage
pool backups according to your tape hardware speed.
Nevertheless, we recommend that you size your disk pools sufficiently to hold all
the data from a normal night's backup operation. Sufficiently sized disk pools will
prevent migration to tape during the backup period.
Typically, you would define one copy storage pool for a primary storage pool
hierarchy. In our setup, both DISKDATA and TAPEDATA are backed up to the
248
IBM Tivoli Storage Manager Implementation Guide
031AKK FIX=YES (SESSION: 110)
the BACKGROUND at 16:38:13. (SESSION: 110, PROCESS: 42)
process. (SESSION: 110)
(SESSION: 110)
031AKK (process ID 42). (SESSION: 110, PROCESS: 42)
(SESSION: 110, PROCESS: 42)
110, PROCESS: 42)
3628380 files inspected, 911 damaged files deleted,
371 damaged files marked as damaged,
1282 objects updated. (SESSION: 110, PROCESS: 42)
the BACKGROUND processed 3628380 items with a completion
state of SUCCESS at 16:38:14. (SESSION: 110, PROCESS: 42)
Advertisement
Table of Contents
