Fixing protection problems

About this task

To fix most protection problems described in Causes of protection problems, use the following procedure.

Procedure

  1. Log on as a member of the administrators or Backup Operators group.
  2. If the filegroups.sd exists in the storage directory root stg-pname, run this command:

    versionvault-home-dir\etc\utils\lsacl –f stg-pname\groups.sd

    Note the supplementary group list. The following is sample output: 
    ===== stg-pname\groups.sd 
Owner: NT_WEST\bob (User) (non-defaulted)
Group: NT_WEST\usersnt (Group) (non-defaulted)
ACL (revision 2): 
0: allowed 
SID: NT_WEST\user (Group)
rights (00000000)

1: allowed    
SID: NT_WEST\tester (Group)
rights (00000000) 

===== stg-pname\groups.sd
Owner: NT_WEST\bob (User) (non-defaulted)
Group: NT_WEST\usersnt (Group) (non-defaulted)   
ACL (revision 2):
Empty ACL: all access denied   
    (Owner)
(Primary group)


(Supplementary group)



(Supplementary group)



(Owner)
(Primary group)

(No supplementary group)
  3. Remove the supplementary group list.
    Run the following command:

    versionvault-home-dir\etc\utils\fix_prot –r –root –chown owner –chgrp group stg-pname

    If you are fixing view storage, you are finished.
  4. If you are fixing VOB storage, log on as the VOB owner and continue.
  5. If the VOB has a supplementary group list, run this command:

    cleartool protectvob –add_group group-name[, ...] vob-stg-pname

  6. Remove the cleartext containers.
    Run the following command:

    scrubber –e –k cltxt vob-stg-pname

    This step must precede Step 7 because checkvob cannot fix cleartext containers.
  7. Fix the storage pools protections.
    Run the following command:

    cleartool checkvob –force –fix –protections –pool vob-stg-pname

Example

The fix_prot and lsacl utilities are installed in the versionvault-home-dir/etc/utils directory.