Abstract: A method and system for synchronizing caches after reboot are described. In a cached environment, a host server stores a cache counter associated with the cache, which can be stored in the cache itself or in another permanent storage device. When data blocks are written to the cache, metadata for each data block is also written to the cache. This metadata includes a block counter based on a value of the cache counter. After a number of data operations are performed in the cache, the value of the cache counter is updated. Then, each data block is selectively updated based on a comparison of the value of the cache counter with a value of the block counter in the metadata for the corresponding data block.

Abstract: A method and system for synchronizing caches after reboot are described. In a cached environment, a host server stores a cache counter associated with the cache, which can be stored in the cache itself or in another permanent storage device. When data blocks are written to the cache, metadata for each data block is also written to the cache. This metadata includes a block counter based on a value of the cache counter. After a number of data operations are performed in the cache, the value of the cache counter is updated. Then, each data block is selectively updated based on a comparison of the value of the cache counter with a value of the block counter in the metadata for the corresponding data block.

Abstract: A method and system for synchronizing caches after reboot are described. In a cached environment, a host server stores a cache counter associated with the cache, which can be stored in the cache itself or in another permanent storage device. When data blocks are written to the cache, metadata for each data block is also written to the cache. This metadata includes a block counter based on a value of the cache counter. After a number of data operations are performed in the cache, the value of the cache counter is updated. Then, each data block is selectively updated based on a comparison of the value of the cache counter with a value of the block counter in the metadata for the corresponding data block.

Abstract: A method includes: communicating read requests from a host device to either a storage array controller or a data cache associated with the host device; classifying portions of data, in response to the read requests, according to frequency of access of the respective portions of data; and causing the storage array controller to either promote a first portion of data to a data cache associated with the storage array controller or demote the first portion of data from the data cache associated with the storage array controller in response to a change in cache status of the first portion of data at the data cache associated with the host device and in response to frequency of access of the first portion of data.

Abstract: A high-power aluminum-air battery system, which is battery pack electrically connected by at least two single aluminum-air batteries in series or parallel, bottom of the battery pack is provided with two liquid flow handling chambers, and upward side of the battery pack is provided with liquid distributing apparatus, the single aluminum-air batteries are interlinked with the liquid flow handling chambers via the respective liquid outlet pipes, the liquid flow handling chambers are interlinked with the pump liquid chamber via their respective liquid transmission pipes, the pump liquid chamber is interlinked with the liquid flow pump via the liquid sucking pipe, and the liquid delivery pipe of the liquid flow pump is interlinked with the liquid distributing apparatus, the liquid distributing apparatus is interlinked with the single aluminum-air batteries under it via liquid inlet pipes.

Abstract: A method and system for host caches managed in a unified manner are described. In an example, a server in a clustered environment designates cache ownership for a cluster application to the cache on one of the hosts. While the application is running on this host, the server monitors data writes made by the application. Upon detecting that the application is running on a different host in the clustered environment, the server can transfer cache ownership to the new host and selectively invalidate cache blocks in the cache of the new host based on the data writes that were previously monitored.

Abstract: A method and system for synchronizing caches after reboot are described. In a cached environment, a host server stores a cache counter associated with the cache, which can be stored in the cache itself or in another permanent storage device. When data blocks are written to the cache, metadata for each data block is also written to the cache. This metadata includes a block counter based on a value of the cache counter. After a number of data operations are performed in the cache, the value of the cache counter is updated. Then, each data block is selectively updated based on a comparison of the value of the cache counter with a value of the block counter in the metadata for the corresponding data block.

Abstract: Examples described herein include a system for storing data. The data storage system retrieves a first set of metadata associated with data stored on a first cache memory, and stores the first set of metadata on a primary storage device. The primary storage device is a backing store for the data stored on the first cache memory. The storage system selectively copies data form the primary storage device to a second cache memory based, at least in part, on the first set of metadata stored on the primary storage device. For some aspects, the storage system may copy the data from the primary storage device to the second cache memory upon determining that the first cache memory is in a failover state.

Abstract: The present invention is directed to a method and software for managing the host-to-volume mappings of a SAN storage system. The host-to-volume mappings of the SAN storage system are represented in mapping configuration components. The active mapping configuration component represents the current host-to-volume mapping for the SAN storage system. Only one mapping configuration component is active at a time. The host-to-volume mappings of the SAN storage system are changed by deactivating the active mapping configuration component and activating an inactive mapping configuration component that represents a different mapping configuration, effecting a repartition, repurpose, disaster recovery, or other business activity. This can be a scheduled task or performed in an on-demand manner. The mapping configuration components are managed and controlled through the management component of the SAN storage system.

Abstract: A high-power aluminum-air battery system, which is battery pack electrically connected by at least two single aluminum-air batteries in series or parallel, bottom of the battery pack is provided with two liquid flow handling chambers, and upward side of the battery pack is provided with liquid distributing apparatus, the single aluminum-air batteries are interlinked with the liquid flow handling chambers via the respective liquid outlet pipes, the liquid flow handling chambers are interlinked with the pump liquid chamber via their respective liquid transmission pipes, the pump liquid chamber is interlinked with the liquid flow pump via the liquid sucking pipe, and the liquid delivery pipe of the liquid flow pump is interlinked with the liquid distributing apparatus, the liquid distributing apparatus is interlinked with the single aluminum-air batteries under it via liquid inlet pipes.

Abstract: The present invention is directed to a method and software for managing the host-to-volume mappings of a SAN storage system. The host-to-volume mappings of the SAN storage system are represented in mapping configuration components. The active mapping configuration component represents the current host-to-volume mapping for the SAN storage system. Only one mapping configuration component is active at a time. The host-to-volume mappings of the SAN storage system are changed by deactivating the active mapping configuration component and activating an inactive mapping configuration component that represents a different mapping configuration, effecting a repartition, repurpose, disaster recovery, or other business activity. This can be a scheduled task or performed in an on-demand manner. The mapping configuration components are managed and controlled through the management component of the SAN storage system.

Abstract: The present invention is directed to a method and software for managing the host-to-volume mappings of a SAN storage system. The host-to-volume mappings of the SAN storage system are represented in mapping configuration components. The active mapping configuration component represents the current host-to-volume mapping for the SAN storage system. Only one mapping configuration component is active at a time. The host-to-volume mappings of a SAN storage system are changed by deactivating the active mapping configuration component and activating an inactive mapping configuration component that represents a different mapping configuration, effecting a repartition, repurpose, disaster recovery, or other business activity. This can be a scheduled task or performed in an on-demand manner. The mapping configuration components are managed and controlled through the management component of the SAN storage system.

Abstract: Systems and methods for management of replicated storage. Features and aspects hereof provide management of data replication among a plurality of storage systems in a manner substantially transparent to host systems attached to the storage systems. The storage systems are coupled to one another through a replication link. One storage systems is designated the primary storage system and all others are designated secondary storage systems. A common logical volume is defined with a common logical volume device identifier used by all of the replicating storage systems of a replication group and their respective attached host systems. The primary storage system processes I/O requests directed to the logical volume by accessing its physical storage volume and forwarding the request to be replicated to all secondary storage systems over the replication link. Secondary storage systems process I/O requests by shipping them over the replication link to the primary storage system for processing.

Abstract: Methods and structure within a storage system for tuning performance of the storage system based on monitored block level access within the storage system. Block level access, either in cache memory or on the storage devices of the storage system, is monitored to detect patterns of access and/or data that correspond to an identified host system program. Based on the identified host system program, a profile of desired storage device configuration information is selected by the storage system. The profile comprises information identifying optimal configuration of a logical volume used by the corresponding host system program. Reconfiguration options are identified from the profile information and used either to automatically reconfigure the logical volume or are presented to a user to permit the user to select desired options from the reconfiguration options.

Abstract: Methods and systems for managing a device in a Web Based Enterprise Management (“WBEM”) environment. At least a management software component and a device management adapter are reused through receiving a network command from the management software component, and forwarding the network command to the device management adapter for conversion to a device message. The WBEM environment is supported by packaging the device message in a WBEM envelope, and transmitting the device message in the WBEM envelope to a computer system. The computer system comprises the device. Subsequently, a native command based on the device message is issued to the device.

Abstract: Systems and methods for management of replicated storage. Features and aspects hereof provide management of data replication among a plurality of storage systems in a manner substantially transparent to host systems attached to the storage systems. The storage systems are coupled to one another through a replication link. One storage systems is designated the primary storage system and all others are designated secondary storage systems. A common logical volume is defined with a common logical volume device identifier used by all of the replicating storage systems of a replication group and their respective attached host systems. The primary storage system processes I/O requests directed to the logical volume by accessing its physical storage volume and forwarding the request to be replicated to all secondary storage systems over the replication link. Secondary storage systems process I/O requests by shipping them over the replication link to the primary storage system for processing.

Abstract: Methods and structure within a storage system for tuning performance of the storage system based on monitored block level access within the storage system. Block level access, either in cache memory or on the storage devices of the storage system, is monitored to detect patterns of access and/or data that correspond to an identified host system program. Based on the identified host system program, a profile of desired storage device configuration information is selected by the storage system. The profile comprises information identifying optimal configuration of a logical volume used by the corresponding host system program. Reconfiguration options are identified from the profile information and used either to automatically reconfigure the logical volume or are presented to a user to permit the user to select desired options from the reconfiguration options.

Abstract: Disclosed is a method of controlling power. Multiple paths via multiple I/O ports couple a server to a storage array. When I/O loads are low, it is determined if an I/O port may be deactivated and placed in a power saving mode. An I/O port may not be deactivated if deactivating that I/O port will affect a high-availability requirement or a performance requirement. Requests are stopped from being sent to an I/O port to be deactivated. When the port to be deactivated becomes idle, the I/O port is placed in a power saving mode. When I/O loads increase to a point where it is necessary to reactivate the I/O port, the I/O port is activated.