Defining A Migration Schedule; Defining An Expiration Schedule - IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual

Implementation guide
Table of Contents

Advertisement

12.2.3 Defining a migration schedule

Migration of your primary storage pools during client backup can and will slow
down the client backup sessions and can impact the scheduling of other server
processes. We recommend scheduling primary storage pool migration outside
the client backup window. Also, make sure that the disk-based storage pools are
large enough to hold the daily backup data from the clients, to avoid a
server-triggered migration during client backups.
With Tivoli Storage Manager V5.3, migration is now a single-step process with
the introduction of the migrate stgpool command. Previously, to migrate data from
a storage pool, you had to change the storage pool high and low migration
thresholds to start the migration, wait a suitable amount of time, and then reset
the thresholds to their normal operational values. In terms of scheduling, you had
to create two schedules, one to set the thresholds to a low value, and another
some time later to reset them.
With the migrate stgpool command, you specify a temporary low migration
threshold, and a duration for which the temporary threshold is valid. At the end of
the period, the threshold is reset to its previous value. During the period that the
migrate stgpool command is active, the high migration threshold is ignored.
A single schedule is required to perform migration. Example 12-8 shows the
command required.
Example 12-8 Defining the MIGRATION schedule
tsm: LOCHNESS_SERVER1>
diskdata lo=0 duration=180" desc="Perform migration on DISKDATA storage pool"
starttime=07:00 active=yes
ANR2577I Schedule MIGRATION defined.
tsm: LOCHNESS_SERVER1>
* Schedule Name
- ---------------- --------------------
MIGRATION

12.2.4 Defining an expiration schedule

Managing the amount of space used by your database is important. When client
backup and archive data expires, the references and metadata must be removed
from the database. The client backup process handles half of the task by
marking expired data references while backing up client data. The second half of
the task is handled by the expire inventory command, which physically removes
the marked entries from the database.
382
IBM Tivoli Storage Manager Implementation Guide
define schedule MIGRATION type=admin cmd="migrate stgpool
q sched migration t=a
Start Date/Time
Duration
--------
02/21/2006 07:00:00
Period
Day
------
---
1 H
1 D
Any

Advertisement

Table of Contents
loading

This manual is also suitable for:

Tivoli storage manager

Table of Contents