The previous example shows duration that is specified in days. Another method of utilizing move policies is by using file groups.
A file group consists of all of the volumes that belong to a control group. For example, suppose that BRMS processes a control group that is called MAINBKU on Monday and uses 10 volumes. The media policy associated with the control group contains a move policy that is called VERSION. This move policy uses file group version support. BRMS considers the 10 volumes a file group and moves them together as specified by the move policy VERSION. Each time you process the MAINBKU group, BRMS creates a new file group.
Control File Group Creation
Group Relative Number Date
MAINBKU 1 5/1/05 (newest)
MAINBKU 2 4/1/05
MAINBKU 3 3/1/05
MAINBKU 4 2/1/05
MAINBKU 5 1/1/05 (oldest)
As you can see, the lowest numbered file group corresponds to the most recent creation date. The highest numbered file group corresponds to oldest creation date.
BRMS cannot predict when a volume that exists as a file group will move next. File group movement depends on when BRMS creates the next file group, not on a specific date. For this reason, you cannot use file group movement with specific date, or days type of duration in the same move policy.
The following display shows a sample move policy that is called VERSION.
Display Move Policy
Move policy . . . . . . . . . . : VERSION
Home location . . . . . . . . . : TAPELIBR
Use container . . . . . . . . . : *NO
Verify moves . . . . . . . . . : *NO
Calendar for working days . . . : *ALLDAYS
Calendar for move days . . . . : *ALLDAYS
Text . . . . . . . . . . . . . : User created move policy using file groups
Seq Location Duration
10 REMOTE_A *GRP 001
20 REMOTE_B *GRP 002
30 REMOTE_C *GRP 003
Bottom
Press Enter to continue.
F3=Exit F12=Cancel This move policy tracks the file group by file through a number of storage locations.