Abstract: An I/O management method includes determining local target I/O rates for a plurality of storage controllers across which an I/O stream is distributed. The local target I/O rates may reflect a target latency corresponding to a QoS attribute associated with the I/O stream. A cumulative target I/O rate may be determined based on the local target I/O rates. A token bucket rate may be calculated for each applicable storage controller based on the local target I/O rates. The storage controllers may implement token bucket algorithms in accordance with the token bucket rates to enforce the QoS for the I/O stream. The local target I/O rates may be determined periodically based on measured data indicating actual latency and traffic. A queue depth is determined based on the measured values of latency and traffic. The queue depth is then used with the desired value of latency to obtain the target I/O rates.

Abstract: A data management method and system for migrating a data volume from a source array to a destination array includes receiving an indication of a source volume to migrate from the source array to the destination array wherein the source volume comprises a clustered volume associated with a plurality of cluster hosts. A path-flip is performed by the host multipath module, to switch the paths between source and destination array. This switch is done in a seamless manner, without disrupting host I/O. The path-flip includes transferring associated metadata from source to destination and can be performed even in clustered and/or multi-host environments. Sanity timers are built-in to ensure that the path-flip completes within a stipulated time-frame and, if not, the path-flip process is aborted and I/O is resumed without any disruption.

Abstract: A data management method and system for migrating a data volume from a source array to a destination array includes receiving an indication of a source volume to migrate from the source array to the destination array wherein the source volume comprises a clustered volume associated with a plurality of cluster hosts. A path-flip is performed by the host multipath module, to switch the paths between source and destination array. This switch is done in a seamless manner, without disrupting host I/O. The path-flip includes transferring associated metadata from source to destination and can be performed even in clustered and/or multi-host environments. Sanity timers are built-in to ensure that the path-flip completes within a stipulated time-frame and, if not, the path-flip process is aborted and I/O is resumed without any disruption.

Abstract: An I/O management method includes determining local target I/O rates for a plurality of storage controllers across which an I/O stream is distributed. The local target I/O rates may reflect a target latency corresponding to a QoS attribute associated with the I/O stream. A cumulative target I/O rate may be determined based on the local target I/O rates. A token bucket rate may be calculated for each applicable storage controller based on the local target I/O rates. The storage controllers may implement token bucket algorithms in accordance with the token bucket rates to enforce the QoS for the I/O stream. The local target I/O rates may be determined periodically based on measured data indicating actual latency and traffic. A queue depth is determined based on the measured values of latency and traffic. The queue depth is then used with the desired value of latency to obtain the target I/O rates.

Abstract: A system for correlating a subscriber unit to a physical port in a point to multipoint wire line network is disclosed. An installer is prompted to manually input a location code associated with the subscriber. The location code in the subscriber unit is received, and is transmitted via the network to a central repository. The location code is stored in the central repository toward associating the location code with the physical port.

Abstract: A system for correlating a subscriber unit to a physical port in a point to multipoint wire line network is disclosed. An installer is prompted to manually input a location code associated with the subscriber. The location code in the subscriber unit is received, and is transmitted via the network to a central repository. The location code is stored in the central repository toward associating the location code with the physical port.