Filter
Top Products
3–56 Creating Storagesets
■ When you incorporate a spare into a storageset that you initialized with the
INITIALIZE SAVE_CONFIGURATION command, the controller reserves
space on the spare for configuration information. The controller updates this
information when the configuration changes.
■ To enable SAVE_CONFIGURATION on a storageset containing user data, you
must back up the data, re-initialize the storageset, and restore the user data.
■ If you previously configured storagesets with the SAVE_CONFIGURATION
option, you do not need to initialize them again after you reconfigure your
devices with a new controller. The storageset retains the option until it is re-
initialized, even if the controller is replaced or the storageset is moved to a new
subsystem.
■ When you replace a controller, make sure the replacement controller does not
contain any configuration data. If the controller is not new, initialize it with the
SET THIS_CONTROLLER INITIAL_CONFIGURATION command. If you do
not take this precaution, you can lose configuration data if nonvolatile memory
changes.
Saving Configuration Information in Dual-Redundant
Controller Configurations
If you decide to use SAVE_CONFIGURATION in a dual-redundant configuration,
keep these points in mind:
■ The controller-unique data for both controllers is saved.
■ The restore feature (holding in port button 6 and pressing the reset button on the
controller’s operator control panel) will not function in a dual-redundant
controller configuration. If the saved configuration was for a dual-redundant
controller configuration, the data will be restored to a single controller and that
controller will be set to NOFAILOVER. You must use the SET FAILOVER
COPY command to restore the configuration information to the other controller.