Abstract: A method, apparatus, and computer instructions for a storage subsystem. This subsystem includes controller devices, storage devices, and a communications network. The communications network connects the controller devices and the storage devices. The communications network also includes a set of diagnostic outputs. The set of diagnostic outputs is configured to output data sent between two devices from the controller devices and the storage devices for monitoring.

Abstract: The present invention is directed to a method of an adaptive procedure table which is capable of providing default behaviors for each procedure if a corresponding procedure is not defined or has been removed from a software build. The default behaviors for each procedure may be defined in a template file provided by a developer before a compile time of software. The present invention may permit a module that defines the implementation of a procedure to be removed from the software build without requiring source code changes. As such, the developer may be allowed to remove or add certain features from a compiled program without introducing compile time or link time errors.

Abstract: Methods and structure for improved import/export of RAID level 6 logical volumes in subsystems supporting RAID level 5 but not level 6. When a RAID level 6 logical volume is imported into a RAID level 5 storage subsystem, features and aspects hereof re-map the logical volume for use as a RAID level 5 logical volume. Disk blocks containing the level 6 additional redundancy information are not used by the RAID level 5 storage subsystem but are skipped in the re-mapping of the logical volume. All other blocks of the logical volume are mapped to corresponding blocks of the RAID level 6 mapping of the logical volume. The logical volume may then be flagged to indicate the additional redundancy information is invalid. A RAID level 6 storage subsystem may then rebuild the additional redundancy information when the flagged logical volume is re-imported to a RAID level 6 storage subsystem.

Abstract: Methods and structure for improved import of RAID level 6 logical volumes into subsystems devoid of RAID level 6 hardware support. When a RAID level 6 logical volume is exported from a first storage subsystem and imported into a second storage subsystem devoid of RAID level 6 hardware support, features and aspects hereof first migrate the logical volume for use as a logical volume with a different RAID level supported by the second storage subsystem. The migration may be, for example, to a RAID level 5 logical volume performed by movement of data blocks to form new stripes and re-generation of associated parity blocks or by simpler re-mapping of existing blocks of the RAID level 6 volume to use only blocks and parity needed for RAID level 5 management. Further features and aspects allow migration to any other RAID management level supported by the second storage subsystem.

Abstract: In some embodiments, a method for managing embedded devices may include one or more of the following steps: (a) loading an embedded web server module, (b) loading a first webpage when loading a first embedded module, (c) replacing the first webpage with a second webpage when a second embedded module is loaded or when a failure is detected by the first embedded module, (d) loading a boot loader module, (e) interacting with the computer system to correct the failure condition, (f) loading an embedded operating system module, and (g) loading a third webpage when loading a RAID application module.

Abstract: Methods and systems for generating differential backup or roll forward data within a storage system. Snapshot copies are generated within the storage system using copy-on-write techniques to maintain the integrity of the snapshots so generated. As an atomic operation with the generation of any snapshot, a copy of the list of data saved by the copy-on-write operations in any earlier snapshots is retained with the newly generated snapshot. The saved overwritten data list and any pair of corresponding snapshots may then be used to generate an accurate differential block list for data to be included in a differential backup or in a roll forward operation. Thus a storage system may generate differential backups or roll forward updates by its own processing to relieve attached host systems from the processing burden.

Abstract: The present invention is a system for optimizing the reconstruction and copyback of data contained on a failed disk in a multi-disk mass storage system. A system in accordance with the present invention may comprise the following: a processing unit requiring mass-storage; one or more disks configured as a RAID system; an associated global hot spare disk; and interconnections linking the processing unit, the RAID and the global hot spare disk. In a further aspect of the present invention, a method for the reconstruction and copyback of a disconnected RAID disk utilizing a global hot spare disk is disclosed. The method includes: disconnecting a RAID component disk; reconstructing data from the disconnected RAID disk onto a global hot spare disk; reconnecting the disconnected RAID component disk; and copying the reconstructed data from the global hot spare disk back to the reconnected RAID component disk.

Abstract: The present invention is an optimized method for the rollback of copy-on-write snapshot volumes. A method in accordance with the present invention may comprise the following steps: (a) creating a copy-on-write snapshot volume; (b) receiving a base volume write request addressed to a base volume data block; (c) executing copy-on-write operations; (d) receiving a snapshot volume rollback request; (e) disabling the copy-on-write operations; and (f) executing volume copy operations.

Abstract: A system and method for packaging a command string in an offline mode into a script, transmitting the script, and using a controller to read the script and send commands and data to an individual device attached to the controller. The script may contain a header and one or more action and action payloads. When the script is interpreted by the controller, various commands and data may be passed directly to the individual device. Such a system may be useful for performing low level commands on the device, including loading firmware.

Abstract: The present invention is directed to a method and apparatus for managing virtual team collaboration meetings. Team members enter answers to scrum questions into a virtual scrum tool, subject to user-defined answer length restrictions, at the beginning of their work day. The virtual scrum tool sends reminders to team members if scrum answers are not submitted a within user-defined time frame. The virtual scrum tool sends brief notifications to registered team members when a team member updates scrum answers. The virtual scrum tool stores scrum answers and provides browsing access to the stored scrum answers and RSS feeds of team member's latest scrum answers.

Abstract: Methods and structure for improved migration of a RAID logical volume from a higher level RAID management to a lower level. Features and aspects hereof provide for migrating a RAID logical volume by removal of one or more disk drives from the logical volume and moving or regenerating only the information of the removed drive(s) that is required for the lower level of RAID storage management. In one exemplary embodiment, a RAID level 6 volume may be migrated to a RAID level 5 volume by removing a single disk drive of the volume. Minimal movement of remaining data blocks and RAID 5 parity blocks in each stripe may be performed creating new RAID level 5 stripes devoid of RAID level 6 second redundancy blocks. The newly formed RAID level 5 volume may then be mapped according to modified mapping algorithms to reduce the need for further data movement.

Abstract: Methods and structure for improved import/export of RAID level 6 logical volumes in subsystems supporting RAID level 5 but not level 6. When a RAID level 6 logical volume is imported into a RAID level 5 storage subsystem, features and aspects hereof re-map the logical volume for use as a RAID level 5 logical volume. Disk blocks containing the level 6 additional redundancy information are not used by the RAID level 5 storage subsystem but are skipped in the re-mapping of the logical volume. All other blocks of the logical volume are mapped to corresponding blocks of the RAID level 6 mapping of the logical volume. The logical volume may then be flagged to indicate the additional redundancy information is invalid. A RAID level 6 storage subsystem may then rebuild the additional redundancy information when the flagged logical volume is re-imported to a RAID level 6 storage subsystem.

Abstract: Methods and structure for improved import of RAID level 6 logical volumes into subsystems devoid of RAID level 6 hardware support. When a RAID level 6 logical volume is exported from a first storage subsystem and imported into a second storage subsystem devoid of RAID level 6 hardware support, features and aspects hereof first migrate the logical volume for use as a logical volume with a different RAID level supported by the second storage subsystem. The migration may be, for example, to a RAID level 5 logical volume performed by movement of data blocks to form new stripes and re-generation of associated parity blocks or by simpler re-mapping of existing blocks of the RAID level 6 volume to use only blocks and parity needed for RAID level 5 management. Further features and aspects allow migration to any other RAID management level supported by the second storage subsystem.

Abstract: A method for returning a logical volume which is part of a redundant data storage system to on-line status following a disk failure within the logical volume during the time when another of that volume's disks is unavailable as a result of having its firmware updated, as an example. Data which would otherwise be changed in the logical volume due to host write requests is directed to a logging facility within the data storage system, but outside of the logical volume undergoing upgrade.

Abstract: A redundant array of solid state disk drives is provided among the storage devices controlled by a storage controller. The solid state disk drives may serve as a level 2 cache using standard multi-level cache management algorithms. The solid state disks may share a drive channel with other storage devices or may have a dedicated channel. Multiple solid state disk devices may also be provided to avoid single points of failure. With two solid state disks, the storage processor could maintain the cache data in both devices. If one device fails, the other could be used to maintain data services. With two or more devices, other Redundant Array of Independent Disks organizations may be used to improve data-to-metadata ratio while maintaining fault tolerance. Using these Redundant Array of Independent Disks techniques, the plurality of solid state disks may then be organized as a single level 2 cache volume that serves as a second level cache for a storage controller.

Abstract: Methods and structure for storing volume and other configuration information on all disk drives of a volume group and for performing pre-merge operations to inform a user of the pending availability of the identified volumes. Configuration information has been historically stored in two distinct areas of configuration information on disk drives—a volume information area and an “other” information area. Aspects of the invention provide for storing all configuration information in the “other” information area. All disks of a system therefore include all configuration information relating both to volumes and to pseudo volume. A pre-merge operation is performed when each disk drive is inserted into a storage system to present new volume information to a user. When the last disk drive of a volume group is inserted, the user may select new volumes to be imported into the system.

Abstract: A solid state disk drive is provided among the storage devices controlled by a storage controller. The solid state disk drive may serve as a level 2 cache using standard multi-level cache management algorithms. The solid state disk may share a drive channel with other storage devices or may have a dedicated channel.

Abstract: Methods and systems for managing control structure access by a processor are disclosed. In general, a processor can communicate with a plurality of control structures. A memory window manager can then be implemented, which communicates with said processor and said plurality of control structures. The memory window manager specifies which control structure among said plurality of control structures is accessible by said processor. The memory window manager also specifies which control structure can be mapped into an address space of said processor.

Abstract: The present invention is directed to a method of an adaptive procedure table which is capable of providing default behaviors for each procedure if a corresponding procedure is not defined or has been removed from a software build. The default behaviors for each procedure may be defined in a template file provided by a developer before a compile time of software. The present invention may permit a module that defines the implementation of a procedure to be removed from the software build without requiring source code changes. As such, the developer may be allowed to remove or add certain features from a compiled program without introducing compile time or link time errors.

Abstract: Methods and associated structure for migrating storage devices between storage subsystems. A storage device to be removed from a storage subsystem is first “exported” by altering configuration data stored on the storage device. The altered configuration information helps assure that the storage device will be recognized as a foreign device in any storage subsystem into which it is subsequently inserted. Forcing recognition of the storage device as a foreign storage device in any subsystem helps assure predictability of the process of importing the storage device into a new system and helps reduce the risk of data loss when reinserting the storage device into a storage subsystem. Storage devices so migrated may include individual disk drives as well as entire volumes comprising one or more disk drives.