The authority an SFS manager has, as defined through the CA VM:Director automatic configuration, is restricted to the file space used by the user IDs that SFS manager manages.
The first user ID identified as being managed by a particular directory manager causes that directory manager to also be made an SFS manager. The limits of that SFS manager’s authority are the file pool and the user storage group in which that user ID’s file space is located.
Example:
The automatic configuration of the file pool VMLGL finds the following for user ID PMASON, who is managed by DSTREET:
|
User ID: |
PMASON |
|---|---|
|
Directory manager: |
DSTREET |
|
File pool: |
VMLGL |
|
User storage group: |
4 |
|
Space allocated: |
80 blocks |
Therefore, automatic configuration makes DSTREET an SFS manager, and authorizes DSTREET to enroll user IDs in user storage group 4 of file pool VMLGL:
|
User ID: |
PMASON |
||
|---|---|---|---|
|
Directory manager: |
DSTREET |
SFS manager: |
DSTREET |
|
File pool: |
VMLGL |
File pool: |
VMLGL |
|
User storage group: |
4 |
User storage group: |
4 |
|
Space allocated: |
80 blocks |
|
|
Further, now that DSTREET can allocate space in file pool VMLGL, user storage group 4, CA VM:Director assigns DSTREET a default allocation size (the amount of space DSTREET allocates by default to users she enrolls in VMLGL user storage group 4) and an allocation limit for that user storage group.
The default allocation size is 150 blocks, and the allocation limit is equal to the amount of space already allocated to PMASON:
|
User ID: |
PMASON |
||
|---|---|---|---|
|
Directory manager: |
DSTREET |
SFS manager: |
DSTREET |
|
File pool: |
VMLGL |
File pool: |
VMLGL |
|
User storage group: |
4 |
User storage group: |
4 |
|
Space allocated: |
80 blocks |
Default allocation: |
150 blocks |
|
|
|
Allocation limit: |
80 blocks |
All subsequent user IDs identified as being managed by that same directory manager, who is now an SFS manager, cause that SFS manager’s limits of SFS authority to be expanded. The limits are expanded by the amount of space allocated to those user IDs in the current file pool, which is being automatically configured. For example, if automatic configuration next finds that the directory manager DSTREET also manages user ID PDRAKE, and PDRAKE is using 250 blocks of space in file pool VMLGL, user storage group 4, DSTREET’s allocation authority is now expanded to this:
|
SFS manager: |
DSTREET |
|---|---|
|
File pool: |
VMLGL |
|
User storage group: |
4 |
|
Default allocation: |
150 blocks |
|
Allocation limit: |
330 blocks |
If the SFS administrator runs automatic configuration on several file pools, the limits of an SFS manager are expanded also in the number of file pools if other file pools include space owned by user IDs that are managed by this SFS manager. For example, automatic configuration of the file pool VMPROD also finds the following:
|
User ID: |
MARYR |
|---|---|
|
Directory manager: |
DSTREET |
|
File pool: |
VMPROD |
|
User storage group: |
2 |
|
Space allocated: |
500 blocks |
Because MARYR is also managed by DSTREET, DSTREET now becomes authorized to enroll user IDs in user storage group 2 of file pool VMPROD. DSTREET is assigned a default allocation size of 150 blocks in this user storage group (this is always the default allocation size for automatically configured SFS managers), and an allocation limit of 500 blocks (this is the current amount of space used by user ID MARYR):
|
SFS manager: |
DSTREET |
|---|---|
|
File pool: |
VMLGL |
|
User storage group: |
4 |
|
Default allocation: |
150 blocks |
|
Allocation limit: |
330 blocks |
|
File pool: |
VMPROD |
|
User storage group: |
2 |
|
Default allocation: |
150 blocks |
|
Allocation limit: |
500 blocks |
|
Copyright © 2014 CA.
All rights reserved.
|
|