Tivoli Storage Manager V6.1 Technical Guide

172 Tivoli Storage Manager V6.1 Technical Guide

Example 9-5 QUERY PROCES command expiration record

Expiration Processed 8 nodes, examined 134746 objects,

deleting 134746 backup objects, 0 archive

objects, 0 DB backup volumes, 0 recovery plan

files; 0 objects have been retried and 0 errors

encountered.

9.2.5 Expiration restart

If an expiration process is cancelled prior to completion, a subsequent expiration process will

pick up from the same place that the last one left off.

The key difference between Tivoli Storage Manager V6.1 and earlier versions of the product

is that the expiration command allows for many variations that did not previously exists—and

as such, the restart tracking model is extended to track restart position information using the

command itself as the identifier for that information. The restart position is only honored if the

expiration commands are exactly the same.

This gives you the ability to have an expiration model that much better fits your requirements.

For example, you can do expiration of archives weekly while performing expiration of backup

data daily. In the event that the expiration of the archive data does not complete in a single

session, the next weekly run picks up where it left off without the intervening expiration of

backup data processes interfering.

As an example, you might have three different expiration commands scheduled throughout

the week. Each of the three commands would have its own restart position, if it was cancelled

prior to completion:

 If a command is re-issued and there is a matching restart position, expiration finishes

processing those in-flight nodes and then any other nodes that had not been processed

and that were candidates to be processed for that expiration run.

 If restart data exists for a given expiration and the command has not been re-executed for

two weeks (14 days), the “stale” restart data is deleted such that the next time this

expiration command is run, it will start from the beginning.

 The deletion of the stale expiration restart information happens as a part of expiration

processing itself—at the end of the process while cleaning up the existing process and

information it checks for and deletes any stale restart information.

 After all candidate nodes for that expiration have been processed, across however many

restarts that might be, the expiration process will complete and the restart tracking will be

cleaned up because there is no longer a restart position to track.

Example 9-6 shows the ANR4896I message issued in case of an expiration restart. We use the

domain parameter with the expire command to process only nodes for domain

OTHERDOMAIN.

Example 9-6 ANR4896I: expiration restart message

ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY reso=2

dom=otherdomain

ANR0984I Process 1 for EXPIRE INVENTORY started in the BACKGROUND at 08:57:04.

ANR0811I Inventory client file expiration started as process 1.

..

lines deleted

..

Chapter 9. Expiration enhancements 173

ANR2017I Administrator SERVER_CONSOLE issued command: CANCEL PROCESS 1

ANR0940I Cancel request accepted for process 1.

..

lines deleted

..

ANR0167I Inventory file expiration process 1 processed for 1 minutes.

ANR0813I Inventory file expiration process 1 canceled prior to completion:

processed 4 nodes, examined 11 objects, deleting 10 backup objects, 0 archive

objects, 0 DB backup volumes, and 0 recovery plan files. 0 objects were retried

and 0 errors were encountered.

ANR0987I Process 1 for EXPIRE INVENTORY running in the BACKGROUND processed 11

items with a completion state of SUCCESS at 08:58:05.

..

lines deleted

..

ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY reso=2

dom=otherdomain

ANR0984I Process 2 for EXPIRE INVENTORY started in the BACKGROUND at 08:59:38.

ANR0811I Inventory client file expiration started as process 2.

ANR4896I Inventory client file expiration is restarting process 1 from

06/19/2009.

..

lines deleted

..

ANR2017I Administrator SERVER_CONSOLE issued command: CANCEL PROCESS 2

ANR0940I Cancel request accepted for process 2.

..

lines deleted

..

ANR0987I Process 2 for EXPIRE INVENTORY running in the BACKGROUND processed

5893 items with a completion state of SUCCESS at 09:00:23.

ANR2017I Administrator SERVER_CONSOLE issued command: QUERY PROCESS

ANR2017I Administrator SERVER_CONSOLE issued command: EXPIRE INVENTORY reso=2

dom=otherdomain

ANR0984I Process 3 for EXPIRE INVENTORY started in the BACKGROUND at 09:00:48.

ANR0811I Inventory client file expiration started as process 3.

ANR4896I Inventory client file expiration is restarting process 2 from

06/19/2009.

ANR2369I Database backup volume and recovery plan file expiration starting

under process 3.

..

lines deleted

..

ANR0167I Inventory file expiration process 3 processed for 2 minutes.

ANR0812I Inventory file expiration process 3 completed: processed 1 nodes,

examined 35003 objects, deleting 35003 backup objects, 0 archive objects, 0 DB

backup volumes, and 0 recovery plan files. 0 objects were retried and 0 errors

were encountered.

ANR0987I Process 3 for EXPIRE INVENTORY running in the BACKGROUND processed

35003 items with a completion state of SUCCESS at 09:02:57.