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

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

Chapter 12. Scheduling
381
database backup expiry, but if you have not licensed it, you must delete the
volume history yourself. Use the
delete volhistory command to do this. We
recommend deleting any database backups that are older than seven days. The
delete volhistory command will never delete the current database backup, so we
use “today-6” when specifying the “TODate” option.
The two recommended schedules are DELETE_VOLHIST and
BACKUP_VOLHIST.
DELETE_VOLHIST
We define a schedule to delete volume history, called DELETE_VOLHIST,
specifying a type of TYPE=DBBACKUP, as shown in Example 12-6.
Example 12-6 Defining the DELETE_VOLHIST schedule
tsm: LOCHNESS_SERVER1>
define schedule delete_volhist type=admin cmd="delete
volhistory type=dbbackup todate=today-6" description="Delete volume history
information for database backups" starttime=07:00 active=yes
ANR2577I Schedule DELETE_VOLHIST defined.
tsm: LOCHNESS_SERVER1>
q sched delete* t=a
* Schedule Name Start Date/Time Duration Period Day
- ---------------- -------------------- -------- ------ ---
DELETE_VOLHIST
02/20/2006 07:00:00 1 H 1 D Any
BACKUP_VOLHIST
Some operations, like the
delete volhistory
command, do update the volume
history in the server database, but do not update the external volume history
files. To ensure that the external volume history data is current, you should
schedule a daily volume history backup using the
backup volhistory
command.
Example 12-7 shows how to create the schedule.
Example 12-7 Defining the BACKUP_VOLHIST schedule
tsm: LOCHNESS_SERVER1>
define schedule backup_volhist type=admin cmd="backup
volhistory" description="Backup volume history file" starttime=07:05 active=yes
ANR2577I Schedule BACKUP_VOLHIST defined.
tsm: LOCHNESS_SERVER1>
q sched backup* t=a
* Schedule Name Start Date/Time Duration Period Day
- ---------------- -------------------- -------- ------ ---
BACKUP_VOLHIST
02/20/2006 07:05:00 1 H 1 D Any