H06.27 Software Installation and Upgrade Guide

11 Backing Out the DSM/SCM Revision
This chapter describes:
• Products that might have fallback implications. Before falling back or backing out the revision,
review the appropriate product softdocs.
• Using DSM/SCM to back out the revision.
NOTE:
• You cannot revert a NonStop NS16200 system to the H06.11.03 RVU or to an RVU prior to
H06.11.01.
• You cannot revert a NonStop NS1200 system to an RVU prior to H06.12.
• You cannot revert a NonStop NS14200 system to an RVU prior to H06.13.
Products That Might Have Fallback Implications
Review the H06.nn Release Version Update Compendium for this RVU and product softdocs to
make sure that your installed products do not have migration implications.
Open System Services (OSS)
• Back up the OSS configuration database files before falling back. For more information, see
the Open System Services Management and Operations Guide.
• OSS Large Files support, introduced in the H06.07 RVU, has created fallback issues. For more
information, see“OSS Large Files” (page 44) .
Storage Management Foundation (SMF)
The record format of the system configuration database sometimes changes between RVUs and is
automatically converted to the new format the first time the system is loaded. To ensure system
configuration integrity, always:
1. Save the system configuration after SMF configuration changes are made.
2. Reload the system from the current system configuration file or the latest version with SMF
changes.
CAUTION: Create a saved version of the configuration before loading a new RVU or revision.
If this step is omitted, you cannot fall back to a previous RVU or revision.
For more information, see the Storage Management Foundation User’s Guide and the required
SMF softdocs.
Safeguard
The following Safeguard features have fallback considerations.
Password Encryption
A new password encryption algorithm was introduced in H06.06. This change has fallback
implications when falling back to a pre-H06.06 RVU, because new passwords will not be valid
on the RVU to which you are falling back. The new passwords must be expired and users must
revert to their previous passwords. For a detailed fallback procedure, see “Safeguard: Changed
Attribute Defaults” (page 46).
Products That Might Have Fallback Implications 131