Defining A Copy Storage Pool - IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual

Implementation guide
Table of Contents

Advertisement

tsm: ATLANTIC>
ANR2202I Storage pool DISKFILE updated.
tsm: ATLANTIC>
Storage
Pool Name
---------- ---------- --------- ---- ----- ---- ---
DISKFILE

6.3.4 Defining a copy storage pool

A copy storage pool is used to create copies (backups) of primary storage pools.
In our example solution, we have two copy storage pools: OFFDIRS and
OFFDATA.
Reuse delay
The example copy pools have a reuse delay of five days. The reuse delay must
expire before empty off-site tape volumes are moved back to the scratch pool.
The delay allows for a period of time in which the off-site tapes, even though
"empty," may be required for a restore. For example, if your most current off-site
backups were destroyed in transit, you may need to restore from a database
backup made four days ago. The four-day-old database backup will still
reference now-empty tapes, but consider them as having data. The reuse delay
allows you to use these tapes even though they are currently considered empty.
The reuse delay is especially helpful during a long company shutdown, such as
at the end of the year, when the off-site data must remain intact in case a
disaster occurs at your main site. You should set the reuse delay equal to the
expiry period of your database backups. For example, if you are using DRM and
your DRMDBBackupexpiredays is set to 6, or you run delete volhistory
type=dbbackup todate=today-6, you should set REUsedelay on the copy storage
pools to 6 as well.
Continue Copy on Error?:
CRC Data: No
Reclamation Type: Threshold
update stg diskfile nextstgpool=tapedata
q stg diskfile
Device
Estimated
Class Name
Capacity Util
SEQF-DC
0.0 M
Pct
Pct High Low
Migr
Mig Mig
Pct Pct
0.0
0.0
90
70
Chapter 6. Data storage
Next Storage
Pool
-----------
TAPEDATA
237

Advertisement

Table of Contents
loading

This manual is also suitable for:

Tivoli storage manager

Table of Contents