2–40
INITIALIZE
DESTROY(Default)
NODESTROY
The
NODESTROY
switch instructs the controller not to overwrite the user data and forced
error metadata during the initialization. Only use the
NODESTROY
switch when you want to
create a unit out of devices that have been reduced from mirrorsets. This allows the data
on the container to be reused for a disk, stripeset, or mirrorset unit. (The
NODESTROY
switch is ignored for RAIDsets.)
SAVE_CONFIGURATION
NOSAVE_CONFIGURATION (Default)
The
SAVE
_
CONFIGURATION
switch instructs the controller to keep a copy of the controller
configuration on the disk devices that are being initialized. Should you replace the
controller in a single-controller configuration, the configuration information will be read
from a device and loaded into the new controller.
Specify
SAVE
_
CONFIGURATION
when initializing any disk device or container on which you
want to store a copy of the controller configuration. If you use the switch for a multi-
device storageset, such as a stripeset, the complete information is stored on each device in
the storageset.
___________________________ Note ____________________________
DIGITAL recommends that the SAVE_CONFIGURATION switch only be used
for single controller configurations. (Use the SET FAILOVER COPY=
command to save configuration information for dual-redundant configurations.)
____________________________________________________________
Specify
NOSAVE
_
CONFIGURATION
for devices and storagesets on which you do not want to
store a copy of the controller configuration.
A device that is initialized with the
SAVE
_
CONFIGURATION
switch has slightly less storage
space than an identical device that is not used to store the controller configuration.
S
AVE
_C
ONFIGURATION
only requires one disk be initialized with this option, but more may
be used, if desired. DIGITAL does not recommend initializing all disks with the
S
AVE
_C
ONFIGURATION
switch, because every update to nonvolatile memory causes writes
to all disks and can affect performance adversely.
S
AVE
_C
ONFIGURATION
is not available for upgrades of software or hardware, and will not
perform inter-platform conversions. For example, you cannot use S
AVE
_C
ONFIGURATION
to upgrade from HSOF V3.1 to V5.1 or from an HSZ40 array controller to an HSZ50 array
controller.
Summary of Contents for HSZ40
Page 6: ......
Page 24: ...2 12 ADD RAIDSET See also ADD UNIT DELETE SET RAIDSET SHOW RAIDSET INITIALIZE ...
Page 101: ...HSZ40 Array Controller CLI Reference Manual Glossary ...
Page 112: ......