Manualshelf

H06.08 Release Version Update Compendium

ManualsBrandsHP ManualsServerHP Integrity NonStop Release and Migration
21222324252627282930
Manageability Products
H06.08 Release Version Update Compendium—543560-001
6-4
Migration in a Safeguard Environment
the existing AUDIT-CLIENT-SERVICE attribute and is used in all SAFECOM and
SAFEART display outputs.
In the G06.29 RVU, the Standard Security (T6533) and Safeguard (T9750) were
enhanced to support the OSS ACL feature. SECURITY-OSS-ADMINISTRATOR
security group and Safeguard configuration attribute AUDIT-CLIENT-OSS were the two
new features included in Safeguard. The OSS ACL feature is migrated to the H06.08
RVU from the G06.29 RVU.
Migration in a Safeguard Environment
The RVUs eligible for migration to the H06.08 RVU are H06.06 and H06.07. Migration
to the H06.08 RVU does not require any special action. However, a migration
procedure exists to support any unexpected failures that might occur during migration.
This procedure preserves the user or password database that is necessary to restore
the original system user or alias database.
To migration:
1. Use VPROC to determine the current versions of:
•
OSMP
•
OSMON
•
SAFEART
•
SAFECOM
1. Back up current Safeguard files ($*.SAFE.*, $SYSTEM.SYSTEM.USERID, and
$SYSTEM.SYSTEM.USERAX).
2. Use SAFECOM to build an obey file to save the current policy.
To create an obey file, perform these steps in SAFECOM:
TACL> safecom/out $system.safe.safevalu/
=display as commands on
=info safeguard, detail
The output from the preceding commands is retained in the SAFEVALU file located
at $SYSTEM.SAFE.
3. After the new version of Safeguard is installed, if you want to retain your original
Safeguard values, run the SAFEVALU obey file created in Step 3 in SAFECOM,
which restores the original Safeguard values.
If you do not follow the preceding migration steps and you do not want to accept the
new default values, then once the new version is installed, use SAFECOM to modify
the appropriate attributes.
You can restore the files backed up in Step 2 in case any unexpected failures occur
during migration.
For more information, see Section 10 of the Safeguard Administrator's Manual.