
130 Sun StorageTek SAM Archive Configuration and Administration Guide • Version 4, Update 6, 04/07
However, most situations are not this straightforward.
Assume that you want to release the largest files first. There are hundreds of small
files that are the same size, and there are several large files. Eventually, the releaser
releases all the large files. If weight_age = 0.0 is specified, the releaser then
releases the small files in essentially random order because they are all the same size
and have the same release priority.
In this scenario, you could set weight_age = 0.01 in order to release the oldest of
the equally sized small files first.
Alternatively, you might set weight_size = 1.0 and weight_age = 0.01.
These directives violate the largest-first policy by counting smaller, less recently
accessed files as better candidates than larger, more recently accessed files. However,
you can reduce this effect by making weight_age smaller than weight_size.
For example, with the previous settings, a 4-kilobyte file that was staged 100 minutes
ago and an 8-kilobyte file that was just staged both have the same release priority
However, if you set weight_age = 0.001, a 4-kilobyte file must have been staged
1,000 minutes ago to have the same priority as the 8-kilobyte file that was just
staged.
For assistance in adjusting priority weights, you can use the no_release and
display_all_candidates directives and run the releaser manually to obtain a list
of candidates in priority order.
Running the Releaser Manually
From time to time, you might want to run the releaser manually. For this, you need
to know the mount point of the file system and the low-water mark that you want
the releaser to reach.
CODE EXAMPLE 4-6 Directives to Release Oldest Modified Files First
weight_size = 0.0
weight_age_access = 0.0
weight_age_modify = 1.0
weight_age_residence = 0.0
Kommentare zu diesen Handbüchern