ùISO8859-1¨ € " ±4 Ô  + 8 d } ' ž  Æ  ×  ç $  ;! [ }#  Á Ñ å ÿ8(W;€8¼#õ ( 4! A"b#r$‡%&¯' Ë( Ø)ä*ÿ+,4(-].c/v0ˆ1 ž2 «3)¹4ã5ö6þ78*%9P:b; r<=.>°?(²@ ÛA æBóC DE F)7GaHxI9—J#ÑKõL# M .N8O?PFQ ZRfSyT‹U V ³WÔXÛY îZù[ \ ]^+_ ?` La Zb ecpd‚e,‘f%¾gähøi j(kAl [min…o Šp˜q²r Ás ÌtÚu êvöw9xJy<ez¢{:»|ö}~-@F€ ‡”‚°ƒÆ„܅!ˆ5‰LŠS‹fŒz}ŽŒ ’‘ ¢’®“³”»• Ä– ΗÚ˜ñ™ š/› 5œ:V=‘ž;ÏŸ  $¡ >¢_£r¤ ‘¥²¦Χâ¨ú™–¼«»hy$ž%¾\ äˆ!A e!Ê "0 w"P "È  "çs$ò&fñ'€b(rY(ÕÂ*/**òÜ, ,ú®.È.´/}0„½1˜â2Vš39'3Ô@3ü "4=!>4`"V4Ÿ#¥4ö$’5œ%%7/&s7U'9É(#:g)Ì:‹*‹MO?QMQ@KN£AÍNïBÍO½C&P‹D:Q²EzRíF5ShG3SžHüSÒIiVÏJHW9K—W‚L,XM5XGN@X}O*X¾PµXéQjYŸRµZ S3ZÀTSZôU3[HV˜[|Wv\Xx]ŒYm_Zx`s[¬aì\ib™]àd^§hä_@iŒ`”kÍaÛlbb5m>cFmtdÆm»eàn‚fÇocgJp+h^pviÐpÕj7q¦k5qÞlurm,rŠnÏs·oƒu‡p]v qÌvirŒw6swÃt+xØuÛyvÙyàw‘zºxa|Ly}®zÖ·{@€Ž|¢Ï}«‚r~ƒ9ƒ €¾ƒÚª„™‚Á…DƒÍ†„ä†Ô…̇¹†ˆ†‡‰œˆÁŠ-‰ÔŠïŠô‹Ä‹õŒ¹Œy¯P)ŽøzEsX¹‘–‘’¼‘©“Ò’f”?“9•:“y–J“´—4”ÿ˜P–4™X–…  –Þ/–ë=——Y2—l—Ÿ —±—¿ —Ù ,—ê ˜c˜c˜‚V˜æ\™=^™šZ™ùšT]šc šÁ fšÈ ›/ ›G ¯›_*ž+ž:*žf,ž‘!ž¾!žà/Ÿ3Ÿ2$ŸfVŸ‹JŸâ9 -7 gg Ÿ,¡ ¡4L¡USSA RAID ArraysList All Defined SSA RAID ArraysList All Supported SSA RAID ArraysList All SSA RAID Arrays Connected to a RAID ManagerAdd an SSA RAID ArrayDelete an SSA RAID ArrayChange/Show Attributes of an SSA RAID ArrayEnable Use of Hot SparesList/Identify SSA Physical DisksChange/Show Use of an SSA Physical DiskSSA RAID ManagerRAID Array TypeConnection Address / Array NameSSA RAID ArrayRemove a Disk From an SSA RAID ArrayAdd a Disk to an SSA RAID ArraySwap Members of an SSA RAID ArrayList Disks in an SSA RAID ArrayIdentify Disks in an SSA RAID ArrayList Hot SparesIdentify Hot SparesList Rejected Array DisksIdentify Rejected Array DisksList Array Candidate DisksIdentify Array Candidate DisksChange Member Disks in an SSA RAID ArrayList/Delete Old RAID Arrays Recorded in an SSA RAID ManagerDelete an Old RAID Array Recorded in an SSA RAID ManagerOld SSA RAID Array Record To DeleteDisk to RemoveDisk to AddMember DisksFlash Disk Identification LightsHot Spare DisksRejected Array DisksArray Candidate DisksSSA Physical DiskMember of an SSA RAID ArrayParent ArrayCurrent UseCancel All IdentificationsUnsynced Parity StripsAllow Page SplitsList Old RAID Arrays Recorded in an SSA RAID ManagerStatePercentage RebuiltList System DisksIdentify System DisksSystem DisksSize of ArrayChange Use of Multiple SSA Physical DisksSSA Physical DisksNew UseUnbuilt Data StripsInvalid data stripList Status Of All Defined SSA RAID ArraysEnable Fast-WriteList of DevicesForce Delete Enable/Disable Fast-Write for Multiple Devices Bypass Cache In 1 Way Fast-Write NetworkStrip SizePrimary DiskSecondary DiskPrimary DisksSecondary DisksSplit Array ResolutionChoose Hot Spare only from Preferred PoolAllow Hot Spare SplitsList Status of Hot Spare PoolsList Status of Hot Spare Protection for an SSA RAID ArrayList Components in a Hot Spare PoolAdd a Hot Spare PoolChange/Show/Delete a Hot Spare PoolSSA LoopsLoop ALoop BSSA Hot Spare PoolsSpares PoolHot Spares MinimumComponents to AddComponents to RemoveComponents in PoolHot Spares Previously ConfiguredStatusHot Spares in PoolComponentsPrimarySecondaryStrip Size (KB)Initial RebuildArray Copy ServicesCoupled DiskCoupled DisksCopy StateCopy DisksPercentage CopiedCopy UncoupledCopy an hdisk by Using an Existing RAID CopyCopy an hdisk by Using free SSA DisksCopy a Volume GroupCopy File SystemsUncouple a Copy From an ArrayList all Copy CandidatesList all Uncoupled CopiesDelete a CopyVerify Copy During CreationCopyCreate a CopyDisk Drives to be CoupledUncoupled CopyCopy ArrayPV IdentifierCopy CandidatesCopy StatusPrepare a RAID Array CopyPrepare Volume Group, Logical Volumes or Filesystems CopyUncouple a RAID Array CopyUncouple a Volume Group, Logical Volumes or Filesystems CopyDelete a RAID Array CopyDelete a Volume Group, Logical Volumes or Filesystems CopyRAID Copy to be CoupledNumber of Disk Drives RequiredDisk drive size requiredVolume Group or Volume Group containing Filesystems to be CopiedVolume GroupLogical Volumes/FilesystemsNew Volume Group nameLogical Volume prefixMount point prefixMount new filesystemsSynchronize the filesystemsParent Volume GroupParent Logical VolumesActionArray to be CopiedHot Spare selectionORPrepare a CopyArrayArray TypeNoneNot CopyingGoodCopyingDegradedTimestampMount pointMount new file systemsSynchronize the file systemsList all Uncoupled Volume GroupsForceMinimum Disk Drive Size RequiredPrepare Volume Group, Logical Volumes, or Filesystems CopyUncouple a Volume Group, Logical Volumes, or Filesystems CopyDelete a Volume Group, Logical Volumes, or Filesystems CopyList All Copy CandidatesList All Uncoupled CopiesList All Uncoupled Volume GroupsArray to be copiedNumber of disk drives requiredMinimum disk drive size requiredVerify copy during creationHot spare selectionRAID copy to be coupledDisk drives to be coupledSSA RAID arrays are SSA logical disks built out of collections of SSA physical disks. Use this option to to create, delete and change SSA RAID arrays.SSA RAID arrays are controlled by SSA RAID managers. RAID managers are typically SSA RAID adapter cards. Use this option to show which SSA RAID arrays are connected to which RAID managers.Replace failing member disks in an SSA RAID array. This option allows you to remove a failing disk from an SSA RAID array, and replace it with a new disk. The data from the original disk is regenerated on the new disk. Depending on the array configuration, the swap may be done either as a single swap operation, or as the removal of the old disk followed by the addition of the new disk. NOTE Not all SSA RAID arrays support member swapping.Use this option to list SSA physical disks according to their particular usage, and to flash their identification lights.SSA physical disks can have different uses assigned to them. For example they can be system disks, members of an SSA RAID array, or be candidates to replace failing disks in a RAID array. Use this option to see the current use of an SSA physical disk, or to assign a different use to it.List all the SSA RAID arrays which are connected to the system. This lists information in five columns: the array name, its connection location (as an SSA unique ID), its operating state (whether the array is fully functional or degraded in some way), its size, and a description of the array.List all the types of SSA RAID array which are supported by the installed SSA RAID managers.Deleting an SSA RAID array removes the device from the Customized Configuration database, and breaks the array up into its member disks.This is the name of an SSA RAID manager. SSA RAID managers are devices which control SSA RAID arrays.The type of the SSA RAID array.The disks which are to be built into the SSA RAID array. An Array should be built from disks which are in the same loopThe name of an SSA RAID array.Remove a disk from an SSA RAID array prior to replacing it with a substitute disk. All information from the original disk will be regenerated on the substitute disk. This option is used when there is no spare drive bay for the replacement disk. Removing a disk from an array is known as reducing the array. The array will continue to function with degraded performance until a substitute disk is added to the array. No more than one disk can be removed from an array. NOTE Not all SSA RAID arrays support member swapping.Add a replacement disk to an SSA RAID array. Use this option after you have removed the failing disk from the array. All information from the original disk will be regenerated on the substitute disk. Once data regeneration has completed on the new disk, the array will return to its normal optimal mode of operation. NOTE Not all SSA RAID arrays support member swapping.Swap a disk out of a SSA RAID array and replace it with a new disk in one operation. This is useful if you have a free disk connected to the SSA RAID manager which is controlling the array you want to make the substitution in. NOTE Not all SSA RAID arrays support member swapping.List all the member disks which make up an SSA RAID array. Information is given in six columns: the disk name, its connection location, its use ('member'), its state within the array ('present' or 'not present'), its size, and a description.Identify the member disks which make up an SSA RAID array by flashing their identification lights.List all the hot spare disks available to an SSA RAID manager. These are disks which can be dynamically used by the SSA RAID manager to replace failing member disks in a SSA RAID array. Information is given in six columns: the disk name, its connection location, its use ('spare'), its state within an array ('n/a'), its size, and a description.Identify the hot spare disks available to an SSA RAID manager by flashing their identification lights. These are disks which can be dynamically used to replace failing disks in a SSA RAID array.List all the disks which used to belong to arrays on an SSA RAID manager, but have been automatically dropped because of drive failure. Information is given in six columns: the disk name, its connection location, its use ('rejected'), its state within an array ('n/a'), its size, and a description.Identify the rejected disks connected to an SSA RAID manager by flashing their identification lights. These are disks which used to belong to SSA RAID arrays, but have been automatically dropped because of drive failure.List all the disks connected to an SSA RAID manager which are candidates for inclusion in a SSA RAID array. Information is given in six columns: the disk name, its connection location, its use ('free'), its state within an array ('n/a'), its size, and a description.Identify the disks connected to an SSA RAID manager which are candidates for inclusion in a SSA RAID array. The drives are identified by flashing their identification lights.The name of an SSA RAID array from which to remove a disk. This becomes necessary if a disk in an array starts be unreliable. The failing disk can be removed, and then be replaced with a working disk.An SSA physical disk to be removed from the SSA RAID array. Removing this disk will cause the array to enter its degraded mode of operation. The array can brought back to its optimal mode of operation by adding new disk to replace the one which has been removed.The name of an SSA RAID array which can have a new disk added to it. This is the name of an array which is current operating in its degraded mode, because a disk has been removed from it. This could be as a result of disk failure, or the user deliberately reducing the array.An SSA physical disk to added to the SSA RAID array. The disk will have the data stored on the original disk regenerated on it, and then the array will return to its optimal operating mode.The name of an SSA RAID array which can have a member disk dynamically swapped with a replacement disk. All data on the member disk is copied to the replacement disk, which then takes the place of the member disk in the array.A member disk in the array to be exchanged with the new disk. The contents of this disk will be transferred to the new disk as part of the swap operation.The disks to be used for the operation.The SSA physical disk to have its current use viewed or changed.The use of the disk in the system.The name of the SSA RAID array which this disk is a member of.Choose whether the identification lights on the disks are to be flashed or turned off.Stop disk identification for all disks attached to a given SSA Raid manager. This will make all disks attached to the RAID stop flashing their identification lights.Enabling this option means that in the event of a member disk failing the SSA RAID manager can use any available hot spare disk to dynamically replace the failing disk. The failing disk will be rejected from the array, and the hot spare brought in in its place. Selecting exact means that only hot spares disks which exactly match the size of the failing member disk will be considered as replacements.Disks which are members of the array.Enabling page splits allows data which is being written to the array to be split up into 4096 byte pages, and these pages to be written in parallel to the member disks of the array. This enhances the overall write performance of the array at the cost of providing no guarantee of the order in which the separate page writes occur. Disabling this option causes all data to be written sequentially to the array, resulting in slower write performance for the array. The order in which the data is written to the array may be critical to the application which is using the data, in the event of an error occurring during the write.The connection address for SSA RAID arrays is a 15 byte ASCII string composed of a 14 byte unique identifier suffixed by a letter to indicate the array type.The use of the array in the system.When an SSA RAID array is disconnected from an SSA RAID manager without following the prescribed deletion methods, a record of the array remains within the RAID manager. This record is kept in non- volatile storage, and hence has to be manually deleted. This option allows you to list the serial numbers of such arrays, and also to delete them the RAID manager. Failure to delete these records will reduce the number of arrays which a RAID manager can control.List the serial numbers of SSA RAID arrays which are recorded in an SSA RAID manager, but which are no longer connected to it. This occurs when an array is disconnected from a RAID manager without following the prescribed deletion method. If it is known that an array like this is not going to be reconnected to the RAID manager then the record of the array within the manager should be deleted.Delete the non-volatile record of a RAID array which is no longer connected to an SSA RAID manager. When a RAID array is disconnected from a RAID manager without following the prescribed deletion method, a persistent record of that array is retained in the RAID manager's non-volatile memory. If it is known that the array will not be reconnected to the manager, then this record of the array should be deleted. Failure to do this will result in a reduction of the number of arrays which the manager can control.The serial number of an SSA RAID array which is no longer connected to this RAID manager.The operating state of the array. The possible values are: good The array is operating normally. exposed The array has lost one of its member disks, but is still operational. Reads from the array will still work, but may take longer than usual. Writes, if allowed in this state will work, but will be slower than usual and cause the array to enter the 'degraded' state. Loss of a further disk in this state will cause the array to go offline. degraded The array has lost one of its member disks, and has been written to. When a new member disk is added to the array a full rebuild will have to take place. Loss of a further disk while in this state will cause data loss, and the array will go offline. rebuilding A member disk has been replaced in the array, which is now in the process of reconstructing the data on the new disk. When the reconstruction has successfully completed the array will return to the 'good' state. offline The array does not have enough of its member disks present to function. unknown The array is missing many of its member disks, and as a result the RAID manager does not have enough information about the array know its state, or any other attributes. NOTE Not all SSA RAID arrays support all of these states.When an SSA array has a new member disk added to replace the old rejected member disk, the array has to rebuild itself in order to incorporate the new disk. This rebuild process can take some time, so this field shows the progress being made if the array is in the process of rebuilding.List all the disks connected to an SSA RAID manager which are being used as system disks. Information is given in six columns: the disk name, its connection location, its use ('system'), its state within an array (which will be 'n/a'), its size, and a description.Identify the system disks which are connected to an SSA RAID Manager by flashing their identification lights.The amount of storage space in the RAID array.SSA physical disks can have different uses assigned to them. For example they can be system disks, members of an SSA RAID array, or be candidates to replace failing disks in a RAID array. Use this option to assign the same use to many SSA physical disks.The SSA physical disks which you would like to assign a new use to.The use of the disks in the system.List the status of all SSA RAID arrays which are connected to the system. The status information for each array reports the number of unsynchronized parity strips and the number of unbuilt data strips. An array will have errors logged against it if any of these values are non-zero.Turns on/off the Fast-Write Cache This facility is not available on adapter cards which do not or cannot have a Fast-Write Cache installedFast-Write candidate List The Devices listed below can have Fast-Write enabled, or have it enabled already.Fast-Write Force Delete If you say yes to this option then the Fast-Write attribute will be deleted from the devices selected above, even if there appears to be data outstanding Answer yes here only if you are certain that this is what you want to do Turns on/off the Fast-Write Cache for multiple devices This option can be used to turn off Fast-Write to a device which previously had Fast-Write enabled. List the status of all raid_5 SSA RAID arrays which are connected to the system. The status information for each array reports the number of unsynchronized parity strips and the number of unbuilt data strips. An array will have errors logged against it if any of these values are non-zero. Status is not available for other array types.The maximum amount of contiguous data that is mapped to a single component.The primary disk of a RAID-1 array. An array must be built from disks that are in the same loop. A RAID-1 array must be built from two disks. The primary disk will be a mirror copy of the secondary disk.The secondary disk of a RAID-1 array. An array must be built from disks that are in the same loop. A RAID-1 array must be built from two disks. The secondary disk will be a mirror copy of the primary disk.The Primary disks of a RAID-10 array. An array must be built from disks that are in the same loop. A RAID-10 array is built from an even number of disks between 4 and 16. Choose the same number of primary disks as secondary disks. The primary disks will be a mirror copy of the secondary disks.The disks which are to be built into the SSA RAID Array. An array must be built from disks which are in the same loop. A RAID-10 array is built from an even number of disks between 4 and 16. Choose the same number of primary disks as secondary disks. The primary disks will be a mirror copy of the secondary disks.This selects which copy of the data remains available if the primary disk is completely separated from the secondary disk.These disks are a mirror copy of the secondary disks.These disks are a mirror copy of the primary disks.The operating state of the array. The possible values are: online The status of all mirror pairs is 'good'. exposed The status of one or more mirror pairs is 'exposed' and no mirror pairs are 'degraded' or 'rebuilding'. degraded The status of one or more mirror pairs is 'degraded' and no mirror pairs are 'rebuilding'. rebuilding The status of one or more mirror pairs is 'rebuilding'. offline One of these conditions exists: 1) The status of one or more mirror pairs is 'offline'. 2) The first two components of the primary group are missing and 'Split Array Resolution' is set to 'primary'. 3) The first component of the secondary group is missing and 'Split Array Resolution' is set to 'secondary'.These are the names of the SSA RAID managers. SSA RAID managers are devices that control SSA RAID arrays.These are the names of the SSA RAID arrays that can use hot spare disks.Loop A is the SSA loop connected to port A1 and A2 on the selected adapter. Loop B is the SSA loop connected to port B1 and B2 on the selected adapter.The hot spare pool that you want to display.The name of the hot spare pool that is being created.The name of the hot spare pool that is being changed or deleted.The existing status of the hot spare pool.The SSA RAID array member disks, hot spare disks, or free disks that are to be added to this hot spare pool. Adding a free disk causes that disk to be converted to a hot spare disk.The minimum number of hot spare disks that can exist in this pool before a hot spare pool error is logged.The SSA RAID array member disks, hot spare disks, or free disks that are to be added to this hot spare pool. Adding a free disk causes that disk to be converted to a hot spare disk.The number of components now in the hot spare pool.The number of hot spares configured when the hot spare pool was previously changed.The number of hot spares now in the hot spare pool.The SSA RAID array member disks or hot spare disks that are to be removed from this hot spare pool. Disks removed from this pool are moved to pool zero.If 'yes' is selected for this option, a hot spare disk is only selected from the hot spare pool containing the failed component. If 'no' is selected for this option, a hot spare disk is selected from the hot spare pool containing the failed component or, if no such hot spare exists a hot spare is selected from the default hot spare pool for that SSA loop (Pool A0 or B0).If 'no' is selected, when a RAID-1 or RAID-10 array is split exactly in half and all primary or all secondary components are present, the RAID manager does not attempt to use hot spares to replace the missing components. It is recommended that this option is set to 'no' if the RAID-1 or RAID-10 array is configured to provide protection against the loss of a physical domain.When set to 'yes', if the partner cache becomes unavailable, fast-write caching for this disk is disabled and an error log entry is made. When set to 'no', if the partner cache becomes unavailable, fast-write operations to this disk continue. In this event, if the adapter card fails, some data might not be flushed to the disk until the adapter has been repaired.If 'no' is selected, when a RAID-1 or RAID-10 array is split exactly in half and all primary or all secondary components are present, the RAID manager does not attempt to use hot spares to replace the missing components. It is recommended that this option is set to 'no' if the RAID-1 or RAID-10 array is configured to provide protection against the loss of a physical domain.The data on the Primary disks will be copied to the Secondary disks. This operation need be performed only if you intend to read any array LBA before you write to that LBA.List the status of all raid_1, raid_5 and raid_10 SSA RAID arrays which are connected to the system. The status information for each array reports the number of unsynchronized parity strips and the number of unbuilt data strips. An array will have errors logged against it if any of these values are non-zero. Status is not available for other array types.The existing status of the hot spare pool. Possible values are: full The number of hot spare disk drives that are in the pool is equal to the number of hot spare disk drives that were in the pool when the pool was last configured. empty Some RAID array components in the pool are not protected by any hot spare disk drives. Either there are no hot spares left in the pool, or at least one of them are too small for any of the RAID components. reduced The number of hot spare disk drives that are in the pool is less than the number of hot spare disk drives that were in the pool when the pool was last configured, but greater than the minimum number that is specified for this pool. critical The number of hot spare disk drives that are in the pool is less than the specified minimum number for that pool. inconsistent The member disk drives in the pool do not agree about the size of the hot spare disk drives, or about the minimum number of hot spare disk drives that is required. mixed An array in this pool has used a hot spare disk drive from another pool. unused Hot spare disk drives exist in the pool, but they are not protecting any member disk driveThese disks are present if a disk copy is being created. When the copy is complete the coupled disk drives will contain a mirror copy of the data on the primary disks.The operational state of the array copy. Not Copying No copy is being created for this array. Good The coupled disks contain an exact copy of the data on the array. The copy must be in this state before it can be uncoupled from the array. Copying Data is being copied to the coupled disks but they do not yet contain an exact copy of the data on the array. Degraded A copy has been created but one or more coupled disks are missing or have failed. If missing disks are replaced or exchanged for new disks the copying will continue.The disks that are coupled to the array and that contain the copy of the array data. These disks are present only if an array copy has been created.The percentage of the array data that has been copied onto the coupled disk drives. When this reaches 100 the coupled disks contain an exact copy of the data on the array and can be uncoupled at any time from the array.The name of the array from which the data was copied.The date and time that this array was uncoupled from the parent array.Select this option if you want to create a copy by using an existing RAID copy. This option will normally be selected if a copy has previously been created for the array but is now no longer needed.Select this option if you want to create a copy by using disk drives that are not now being used. This option must be selected if you have not previously created an array copy or if no offline copy exists that can be reused.Select this option if you want to uncouple a copy from an array. The copy must be in the good state before it can be uncoupled. Once uncoupled, a new hdisk will be created containing the copied data.Select this option to list all SSA RAID Arrays that can support disk copy.Use this selection to find the parent array and creation date of each array type of raid_copy.Select this option if you want to delete a copy. The copy might be coupled to the array or uncoupled from the array. The copy can be in any state. Deleting the copy causes all the data on the copy to be lost.Select the array for which you want to create the copy.The array to be used as the source data for the copy.To create a new copy for this array using an uncoupled copy, the uncoupled copy selected must have exactly this size.Selecting yes for this option will cause all data written to the copy to be verified before the write operation completes. This will reduce the possibility that unrecoverable media errors will be encountered when the copy is uncoupled and read but will increase the time required to perform the copy.Provides an option for automatic assignment of coupled disk drives to hot spare pools. Default This will assign the coupled disk drives to the pool to which those disk drives were previously assigned. Primary Each coupled disk drive will be assigned to the same hot spare pool as the Primary disk that it is copying. Secondary Each coupled disk drive will be assigned to the same hot spare pool as the Secondary disk that it is copying.The name of the existing RAID copy to be used. Press List for a list of uncoupled copies that might be used to create the new copy.The number of disk drives that must be coupled to the array to permit a copy to be performed.This is the effective size of each member disk drive in the array. Each disk drive coupled to the array must be at least this size. If larger disk drives are selected, the excess space will remain unused.The number of disk drives listed here must equal the number of Disk Drives Required. Press the List key for a list of candidate disk drives.Move cursor to the array that is to have its copy uncoupled and press Enter. The copy must be in the good state before it can be uncoupled. Once uncoupled a new hdisk will be created containing a copy of the data that was on the parent disk at the time the copy was uncoupled.The copy has been uncoupled from the array.Copy The name of the array copy Status The raid_copy Array status Parent The name of the array that the data was copied from. Timestamp The date and time that the copy uncoupled from the parent array.Select the copy to be deleted. The copy might be part of the parent array or it might be uncoupled from the parent. The array might be in any state. Deleting the copy will cause all the data on the copy to be deleted.Remove a disk drive from an SSA RAID array before you replace it with a new disk drive. The array data is rebuilt on the replacement disk drive. This option is used when no spare drive slot is available for the replacement disk drive. The array continues to function with degraded performance until a replacement disk drive is added to the array. NOTE Not all SSA RAID arrays support member swapping.Add a replacement disk drive to an SSA RAID array. Use this option after you have removed a failing disk drive from the array. The array data is rebuilt on the replacement disk drive. When the rebuild operation has completed on the new disk drive, the array returns to its normal mode of operation. NOTE Not all SSA RAID arrays support member swapping.Swap an array member out of a SSA RAID array and replace it with a new disk drive in one operation. The array member to remove might be a working disk drive, a failed disk drive or a missing disk drive. The disk drive to add can be a free or a hot spare disk drive. ATTENTION If you swap a disk drive with a hot spare disk drive check the status of all hot spare pools after the operation to ensure that the required number of spares remain in each hot spare pool. NOTE Not all SSA RAID arrays support member swapping.The name of an SSA RAID array from which to remove a disk drive. This becomes necessary if a disk drive in an array becomes unreliable. The failing disk drive can be removed, and replaced with a working disk drive.The name of an SSA RAID array that can have a new disk drive added to it. This is the name of an array that is currently operating in its degraded mode, because a disk drive has been removed from it. This could be because a disk drive has failed, or because the user has deliberately removed a disk drive from the array.An SSA physical disk drive to be added to the SSA RAID array. The array data is rebuilt on this disk drive and the array is returned to its normal operating mode.The name of an SSA RAID array that can have a member disk drive dynamically swapped with a replacement disk drive. The array data is rebuilt on the replacement disk drive.The SSA Array member to be exchanged with the new SSA physical disk drive. A failed or a missing disk is listed as BlankReserved.The SSA physical disk drive to be removed from the array.Select this option if you want to make a copy of a RAID array. If the RAID array is a member of an active Volume Group, select 'Prepare a Volume Group, Logical Volumes or Filesystems Copy'.Select this option if you want to copy a Volume Group or some part of a Volume Group. You must select this option if you want to copy any part of an active Volume Group.Select this option if you want to uncouple a copy from an array. The copy must be in the good state before it can be uncoupled. When uncoupled a new hdisk is created containing the copied data.Select this option if you want to uncouple a Volume Group. The Logical Volumes and File Systems that are available when the Volume Group uncoupled match those that were selected when the copy was created.Select this option if you want to delete a Volume Group copy. The copy might be coupled to the array or uncoupled from the array. The copy can be in any state. The deletion of the copy causes all the data on the copy to be lost.The name of the existing RAID copy to be used. Press List for a list of uncoupled copies that might be used to create the new copy. Leave this field blank if you are selecting 'Disk drives to be coupled'.A list of disk drives to be used for the copy. Press List for a list of free disk drives that might be used to create the copy. The number of drives selected must equal the 'Number of disk drives required'. Leave this field blank if you are selecting 'RAID copy to be coupled'.The Volume Group that is to be copied or the name of the Volume Group that contains the Logical Volumes or filesystems that are to be copied. Select 'ALL' to copy the entire contents of a Volume Group. Enter or select the names of one or two Logical Volumes to be copied. If you want to copy more than two logical volumes select 'ALL'.This is the name that is assigned to the new Volume Group that is created when the copy is uncoupled from the array. Leave this field blank if you want to assign the Volume Group name when the copy is uncoupled.This prefix is added to the names of the existing Logical Volumes when the new Logical Volume names are assigned during the uncouple operation. Leave this field blank if you want to assign the Logical Volume prefix when the copy is uncoupled.This prefix is added to the mount points of the existing filesystems when the new filesystem mount points are assigned during the uncouple operation. Leave this field blank if you want to assign the filesystem prefix when the copy is uncoupled.Select 'no' for this option if you do not want the filesystems to be automatically mounted when the copy is uncoupled. Select 'yes' for this option if you want the uncouple operation to mount the filesystems. Select 'read only' for this option if you want the uncouple operation to mount the filesystems as 'read only'. You can change this option when the copy is uncoupled.Select this option to schedule a 'sync' operation before the copy is uncoupled.Move the cursor to the Volume Group or hdisk that you want to uncouple. Press Enter. All the hdisks in the Volume Group will be uncoupled. All the hdisk copies in the Volume Group must be in the good state before the Volume Group can be uncoupled.This is the name of the Volume Group from which the copy was a taken.These are the names of the Logical Volumes that were selected when this copy was taken.The Volume Group name that is to be used when the copy is uncoupled from the parent. If no name is supplied, a default Volume Group name will be used.The prefix that is to be added to the parent Logical Volume names when the new Logical Volumes are created during the uncouple operation. If no prefix is assigned, a default value is used.The prefix that is to be added to the mount points of the existing filesystems when the new filesystem mount points are assigned during the uncouple operation. If no prefix is assigned, a default value is used.Move the cursor to the Volume Group to be deleted. Press Enter.This is the name of the Volume Group that will be deleted.Select 'Delete' to remove the Volume Group and to change its member disk drives to 'free'. Select 'Force Delete' to unmount the filesystems, remove the volume Group and change its member disk drives to 'free'. Select 'Delete and Recouple' to remove the Volume Group and recouple its member disk drives to the parent disk drives.Select 'Delete and Detach' to remove the Volume Group and change its raid_copy arrays to 'free'. Select 'Delete' to remove the Volume Group and to change its member disk drives to 'free'. Select 'Delete and Recouple' to remove the Volume Group and recouple its member disk drives to the parent disk drives.Select 'yes' to unmount copy filesystems, or to export varied off Volume Groups.Use this selection to find the parent array and creation date of each Volume Group copy.yes,no,exactArray Candidate Disk,Hot Spare Disk,System DiskRejected Disk,Array Candidate Disk,Hot Spare Disk,System DiskUnused,System DiskArray Candidate Disks,Hot Spare Disks,System DisksPrimary,SecondaryLoop A,Loop BDefault,Primary,Secondaryyes,no,read onlyDelete and Detach,Delete,Delete and Recoupleno,yes################################################# # SSA physical disks that need to be configured. ################################################# # SSA physical disks that are members of arrays. ################################################# # SSA physical disks that are free. ################################################# # SSA physical disks that are hot spares. ################################################# # SSA physical disks that are system disks. ################################################# # SSA physical disks that are rejected. Not Rebuilding################################################# # Arrays that cannot be viewed or changed. yes no################################################# # Fast-Write is Not Valid with this Raid Manager. no# Disks in Loop A are: # Disks in Loop B are: ################################################################ # Setting Force Delete to 'yes' will allow the system to disable # Fast-Write for this SSA Logical Disk even if this involves # discarding data in an inaccessible Fast-Write Cache card. # # The data in the Fast-Write Cache card is the most recent copy # of some portions of the data on the SSA Logical Disk. # Discarding this data may destroy the integrity of the data on # the disk, resulting in system crashes, data corruption and # loss of system integrity. # It is suggested that you try selecting no for this option first # Force Delete is only applicable if you are setting # Enable Fast-Write to 'no' # yes no# Fast-Write is Enabled for these devices # Fast-Write is Disabled for these devices # Fast-Write is Offline for these devices Fast-Write is not available for this device # Hot Spare Pools in Loop A are: # Hot Spare Pools in Loop B are: # SSA physical disks that are hot spare disks. # SSA physical disks that are members of an array. # SSA physical disks that are free. A value must be specified in the entry field for 'Primary Disks' or 'Secondary Disks' Component Location Size Pool Protected Status Pool Components Spares Configured Minimum Status Component Location Size Status A value must be specified in the entry field for 'Primary Disks', 'Secondary Disks' or 'Coupled Disks'# Fast-Write is Suspended for these devices All Hot Spare Pools are in use. The number of primary disks must be equal to the number of secondary disks.