Abstract: A storage system assigns one or more large disks in a storage enclosure as a common dedicated hot spare that is used by multiple RAID groups. Storage space equivalent to the smallest physical disk in a RAID group is allocated on the common dedicated hot spare. A mapping of this allocated storage space to the RAID group is maintained in nonvolatile memory. When a disk fails in the RAID group, the allocated storage space on the common dedicated hot spare receives a rebuild of the failed disk. Once the rebuild is complete, the allocated storage space acts as part of the RAID group. When the failed disk is replaced, the data on the allocated storage space is copied to the replacement disk. Once the copy is complete, the allocated storage space is once again set to act as a dedicated hot spare to the RAID group.

Abstract: A secondary location of a network acts as a recovery network for a primary location of the service. The secondary location is maintained in a warm state that is configured to replace the primary location in a case of a failover. During normal operation, the primary location actively services user load and performs backups that include full backups, incremental backups and transaction logs that are automatically replicated to the secondary location. Information is stored (e.g. time, retry count) that may be used to assist in determining when the backups are restored correctly at the secondary location. The backups are restored and the transaction logs are replayed at the secondary location to reflect changes (content and administrative) that are made to the primary location. After failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.

Abstract: A method of replicating tiered data includes copying a volume from a first tiered storage array of a primary processing site to a second tiered storage array of a failover processing site, wherein the volume is tiered with a first tiered organization in both the first and second tiered storage arrays, directing from a first storage controller of the primary processing site that a second storage controller of the failover processing site stop tiering the volume on the second tiered storage array, changing the first tiered organization of the volume in the first tiered storage array to a second tiered organization, and changing the first tiered organization of the volume in the second tiered storage array to the second tiered organization.

Abstract: Replication and recovery for a protected private cloud infrastructure that may include hosts, virtual machines (VMs) provisioned on the hosts, storage arrays and a management server. Metadata is periodically captured and made accessible to a recovery site. Upon a recovery event, replication of storage arrays is halted, and a number of target machines corresponding to the management server and the hosts to be recovered are assigned. The assigned management server and hosts are then bare provisioned by installing operating systems or hypervisors as specified by the metadata. Only then are recovery target machines connected to the replicated storage arrays so that virtual machines can be activated.

Abstract: A method, computer program product, and computing system for identifying at least one misassigned slice that is associated with a first data tier and is located in a first front end LUN. The at least one misassigned slice is being accessed contrary to the first data tier. The failure domain of the first front end LUN is determined. At least one replacement slice that is associated with a second data tier and is located in a second front end LUN is identified based, at least in part, upon the failure domain of the first front end LUN. The at least one misassigned slice is moved to the second front end LUN. The at least one replacement slice is moved to the first front end LUN.

Abstract: A method begins by a dispersed storage (DS) processing sending representations of a read-rebuild inquiry request to storage units and receiving a decode threshold number of encoded data slices in response. The method continues with the DS processing module receiving a remaining number of slice status responses regarding a remaining number of encoded data slices. The method continues with the DS processing module decoding the decode threshold number of encoded data slices to reproduce a data segment and interpreting the remaining number of slice status responses to determine whether one of the remaining number of encoded data slices includes an error. When determining the error, the method continues with the DS processing module generating a rebuilt encoded data slice based on the reproduced data segment to replace the one of the remaining number of encoded data slices that includes the error.

Abstract: A method and apparatus update an image stored in a memory of a device. A next block writing index n for updating a first target memory block of the memory is determined. Backup data is written to a backup block of the memory when n is an even number. The first target memory block is updated with the new data. The backup data is calculated based on a binary operation between new data corresponding to n and old data stored in a second target memory block corresponding to n+1, and the binary operation has reversibility. If n is the last block writing index, then the binary operation is not used and the backup data is the same as the new data.

Abstract: A method and apparatus for recovering the failed disk of a virtual machine in a virtualization system are disclosed. The apparatus includes a system performance analysis unit, a failed disk recovery unit, and a disk exchange unit. The system performance analysis unit calculates recovery resources, that is, network and disk I/O bandwidths, to be assigned to the recovery of a failed disk by analyzing the performance of the virtualization system. The failed disk recovery unit performs the discovery of the failed disk by recovering a copy disk, that is, a copy of the failed disk, using a mandatory disk stored in the virtualization system while ensuring the performance of virtual machines based on the recovery resources. The disk exchange unit deletes the failed disk and assigns the recovered copy disk to a virtual machine corresponding to the failed disk.

Abstract: A method includes monitoring a plurality of HyperSwap sessions between one or more storage systems located at a first location and one or more storage systems located at a second location, wherein at least one of the one or more storage systems located at the first location and at the second location are designated as a primary storage system. The method includes detecting an error event and freezing communications between the storage systems located at the first location and the second location in response to the error event. The method also includes designating either the first location or the second location as a preferred location and modifying the designation of all of storage systems at the preferred location to be primary storage systems in response to the error event.

Abstract: A method for policy based provisioning of shared boot images includes querying a storage name server for boot target that is in an accessible discovery domain. Boot target information about the boot target is received. A login request is sent to the boot target. The login request includes a flag specifying whether the login request is a first login request after a reboot.

Abstract: A method includes monitoring a plurality of HyperSwap sessions between one or more storage systems located at a first location and one or more storage systems located at a second location, wherein at least one of the one or more storage systems located at the first location and at the second location are designated as a primary storage system. The method includes detecting an error event and freezing communications between the storage systems located at the first location and the second location in response to the error event. The method also includes designating either the first location or the second location as a preferred location and modifying the designation of all of storage systems at the preferred location to be primary storage systems in response to the error event.

Abstract: The invention relates to apparatus for managing data swap in a migration of virtual memory data of a virtual machine. In one embodiment, an apparatus comprises a receiving unit configured to receive a migration instruction and the second site information; a copying unit configured to copy memory data to a sub-logical unit in the first storage device; and a notifying unit configured to send a notification to instruct the second host to read the memory data from a mirror logical unit of a sub-logical unit in the second storage device. The apparatus modifies a mirror direction between the first and second storage devices and modifies a path table related to the first and second storage devices. Data of the virtual machine can be migrated and swapped in a metro mirror manner, thereby the virtual machine data can be migrated across sites without affecting system operation.

Abstract: Rapid demanding for storage capacity at internet era requires a much flexible and powerful storage infrastructure. Present invention disclosed a type of storage system based a model of centrally controlled distributed scalable virtual machine. In this model, one or more service pools including virtual storage service pool and application service pools can be automatically created to meet the demands for more storage capacity from various applications. Specially this model provide a solid foundation for distributing storage volumes for supporting storage on-demand and sharing with exceptional management capabilities. In addition, this model provides a flexible fault recovery topology beyond the traditional recovery plan.

Abstract: One aspect of the present invention provides a system for failover comprising at least one client selectively connectable to one of at least two interconnected server via a network connection. In a normal state, one of the servers is designated a primary server when connected to the client and a remainder of the servers are designated as backup servers when not connected to the client. The at least one client is configured to send messages to the primary server. The servers are configured to process the messages using at least one service that is identical in each of the servers. The services are unaware of whether a server respective to the service is operating as the primary server or the backup server. The servers are further configured to maintain a library, or the like, that indicates whether a server is the primary server or a server is the backup server. The services within each server are to make external calls via its respective library.

Abstract: An SVC cluster manages a plurality of storage devices and includes a plurality of SVCs interconnected via a network, each SVC acting as a separate node. A new configuration node is activated in response to configuration node failures. The new configuration node retrieves client subscription information about events occurring in storage devices managed by the SVC cluster from the storage devices. In response to events occurring in the storage device managed by the SVC cluster, the new configuration node obtains storage device event information from a storage device event monitoring unit. The new configuration node sends storage device events to clients who have subscribed to this information according to subscription information obtained. The storage device is not installed in the original configuration node.

Abstract: In one embodiment, a method for managing data swapping in a migration of virtual memory data in a virtual machine, wherein the data swapping is from a first storage device at a first site to a second storage device at a second site, and the first and second storage devices have a metro mirror relationship includes sending a fail report in response to a failure to access the first storage device according to a path table, in response to the fail report, modifying a mirror direction between the first and second storage devices, sending a path modifying notification for modifying settings of a first path to the second storage device, and activating the path to the second storage device by modifying the path table according to the path modifying notification, so as to make the second storage device accessible.

Abstract: Synchronous local and cross-site switchover and switchback operations of a node in a disaster recovery (DR) group are described. In one embodiment, during switchover, a takeover node receives a failover request and responsively identifies a first partner node in a first cluster and a second partner node in a second cluster. The first partner node and the takeover node form a first high-availability (HA) group and the second partner node and a third partner node in the second cluster form a second HA group. The first and second HA groups form the DR group and share a storage fabric. The takeover node synchronously restores client access requests associated with a failed partner node at the takeover node.

Abstract: Techniques for providing session level replication and fail-over as a network service include generating a replication rule that replicates network traffic destined for a primary server from an originating server to a network controller and installing said rule in a switch component, identifying flows from the originating server to the primary server, replicating each incoming data packet intended for the primary server to the network controller for replication and forwarding to replica servers, determining said primary server to be in a failed state based on a number of retransmissions of a packet, to selecting one of the replica servers as a fail-over target, and performing a connection level fail-over by installing a redirection flow in the switch component that redirects all packets destined to the primary server to the network controller, which forwards the packets to the replica server and forwards each response from the replica server to said originating server.

Abstract: A storage processor includes storage for redundantly storing a log file of a journaling file system on a separate logical device from a primary copy of the log file and further provides for recovery of the file system upon failure of both the primary storage and the redundant storage storing the log file of the journaling file system by storing dirtied metadata objects in the cache of the storage processor to a vault area and then applying the stored dirtied metadata objects against the underlying persistent storage.

Abstract: Methods, apparatus and computer program products implement embodiments of the present invention that include arranging a first storage device and a second storage device to store data in a mirrored configuration. Upon a host processor receiving, in response to a first request conveyed to read the data from the first storage device, a message indicating that the first storage device is in an error recovery mode, the host processor can convey a second request to read the data from the second storage device. Upon receiving the data from the second storage device, the host processor can cancel the first request. Storage devices implementing embodiments of the present invention include hard disk drives and solid state disk drives.

Abstract: In one embodiment, RAID-related metadata may be stored on a distributed database of a cluster (i.e., a cluster database), which is separate and apart from a storage array of SSDs configured to serve as main storage for nodes of the cluster. The RAID-related metadata may be embodied as RAID labels (or other data structures) having configuration information that identifies one or more RAID groups associated with an extent store and storage devices, e.g., SSDs, within each RAID group. Each SSD may be part of a RAID configuration topology tree structure that defines an extent store using a multi-level hierarchy (e.g., three levels), wherein the first level of the tree identifies the SSD, the second level identifies the RAID group to which the SSD belongs, and the third level identifies the extent store or storage container to which the RAID group belongs.

Abstract: Methods and systems are described for performing storage operations on electronic data in a network. In response to the initiation of a storage operation and according to a first set of selection logic, a media management component is selected to manage the storage operation. In response to the initiation of a storage operation and according to a second set of selection logic, a network storage device to associate with the storage operation. The selected media management component and the selected network storage device perform the storage operation on the electronic data.

Abstract: According to certain aspects, an information management cell with failover management capability can include secondary storage computing devices configured to conduct primary data from a primary storage device(s) to a secondary storage device(s) during secondary copy operations, at the direction of a remote storage manager, wherein a first secondary storage computing device implements a failover storage manager configured to, in the event of a loss of connectivity between the cell and the remote storage manager: access a stored storage policy; initiate a first secondary copy operation according to the storage policy in which the first secondary storage computing device is involved in the creation of a first secondary copy on the secondary storage device(s); and initiate a second secondary copy operation according to the storage policy in which a second secondary storage computing device is involved in the creation of a second secondary copy on the secondary storage device(s).

Abstract: According to certain aspects, an information management cell can include a failover storage manager configured to: instruct a secondary copy application to perform a secondary copy operation in which primary data generated by at least one client computing device is stored as a secondary copy in a second secondary copy file format different than a first secondary copy file format; and subsequent to reestablishment of connectivity to a main storage manager, restore the secondary copy stored in the second secondary copy file format to obtain restored data that is no longer in the second secondary copy file format; and can include at least one secondary storage computing device configured to, subsequent to the restore of the secondary copy, and at the direction of the main storage manager, conduct the restored data to a secondary storage device(s) to create a secondary copy in the first secondary copy file format.

Abstract: Based on information security rules, it is not possible to take out a failure HDD to the exterior of a facility for replacement without erasing data therefrom. According to the present storage sub-system, a slot in which failure has occurred and a slot not registered to a configuration information of a storage sub-system are used to simultaneously perform correction copy to a spare HDD and data erase of the failure HDD in parallel, so as to enable the failure HDD to be brought out to the exterior of the storage facility. Further, time required from when failure has occurred to the HDD to data recovery is shortened, so as to prevent deteriorated redundancy that may be caused by another failure occurring during data recovery and to reduce the risk of data loss.

Abstract: Embodiments are directed to predicting the health of a computer node using health report data and to proactively handling failures in database services. In an embodiment, a computer system monitors various health indicators for multiple nodes in a database cluster. The computer system accesses stored health indicators that provide a health history for the database cluster nodes. The computer system then generates a health status based on the monitored health factors and the health history. The generated health status indicates the likelihood that the node will be healthy within a specified future time period. The computer system then leverages the generated health status to handle current or predicted failures. The computer system also presents the generated health status to a user or other entity.

Abstract: It is provided a management computer which refers to switching level information including switching patterns to be used at a time of switching the first task to the second application server; sets a level of a degree of safety for each of the switching patterns; refers to a stop time for each first task which is allowed upon switching the first task to the second application server; selects one of the switching patterns having a switching time that is shorter than the stop time of the task requirement information which is set to the first task and having the level of the degree of safety that is highest among the switching patterns of the switching level information; stops the second task of the second application server by the selected one of the switching patterns; and then controls the second application server to provide the first task.

Abstract: A primary storage controller is maintained in a copy relationship with a secondary storage controller, wherein the primary and secondary storage controllers are coupled to a host that is configurable to use the secondary storage controller instead of the primary storage controller. The primary storage controller determines occurrence of at least one condition in the primary storage controller, wherein the at least one condition occurs prior to a failure of the host to perform an Input/Output (I/O) operation with respect to at least one storage volume of the primary storage controller. The primary storage controller communicates the occurrence of the at least one condition to the host, wherein in response to the communicating the host is configured to determine whether to use the secondary storage controller instead of the primary storage controller based on the occurrence of the at least one condition.

Abstract: A computer-implemented method for fault recovery in multi-tier applications may include: 1) identifying a plurality of clusters, 2) identifying a multi-tier application that includes a plurality of components, each cluster within the plurality of clusters hosting a component, 3) identifying a fault of a first component within the plurality of components on a first cluster within the plurality of clusters, the fault requiring a first recovery action, 4) identifying at least one dependency relationship involving the first component and a second component within the plurality of components on a second cluster within the plurality of clusters, 5) determining, based on the fault and the dependency relationship, that the second component requires a second recovery action to ensure that the multi-tier application operates correctly, and 6) performing the second recovery action on the second component. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: A distributed data storage method, apparatus, and system for reducing a data loss that may result from a single-point failure. The method includes: splitting a data file to generate K data slices, splitting each data slice of the K data slices to generate M data blocks for each data slice, and performing check coding on the M data blocks by using a redundancy algorithm to generate N check blocks; determining, by using a random algorithm, a first physical storage node corresponding to one block of the M data blocks and the N check blocks, and determining at least M+1 different physical storage nodes based on the determined first physical storage node and according to a first rule-based sorting manner; and storing at least M+1 blocks of the M data blocks and the N check blocks onto the at least M+1 different storage nodes, where K, M, and N are integers.

Abstract: Systems and methods are disclosed herein for performing a failover operation between a first distributed database cluster and a second distributed database cluster. In one aspect, the method includes blocking a plurality of software processes from making any new access requests to the first distributed database cluster and completing a current access request to the first distributed database cluster that was initiated by one of the plurality of software processes before the failover operation was initiated, waiting for data to replicate from the first distributed database cluster to the second distributed database cluster, wherein replicating includes any changes to the data from the current access request, and allowing the plurality of software processes to make the new access requests to the second distributed database cluster once the replicating has completed.

Abstract: An architecture for protecting against failure in a switched storage network using virtualization.

Abstract: A storage device includes a controller device and a memory device. The controller device transmits communication information to which route information is added, the route information indicating a route to a destination of the communication information and including an address of a relay point that the communication information passes through before reaching the destination of the communication information. The memory device receives the communication information, and to transmit the communication information to a next relay point, when the destination of the communication information is not the local memory device, by using the address of the relay point included in the route information of the communication information.

Abstract: Jobs submitted to a primary location of a service within a period of time before and/or after a fail-over event are determined and are resubmitted to a secondary location of the service. For example, jobs that are submitted fifteen minutes before the fail-over event and jobs that are submitted to the primary network before the fail-over to the second location is completed are resubmitted at the secondary location. After the fail-over event occurs, the jobs are updated with the secondary network that is taking the place of the primary location of the service. A mapping of job input parameters (e.g. identifiers and/or secrets) from the primary location to the secondary location are used by the jobs when they are resubmitted to the secondary location. Each job determines what changes are to be made to the job request based on the job being resubmitted.

Abstract: A hybrid storage device that includes a hard-disk drive (HDD) and a flash memory is described. When control logic in the hybrid storage device receives a request from an external device to write a block of data to a logical address in a first portion of an address space that maps to the HDD, the control logic writes the block of data to the HDD. However, if there is a change in environmental state information of the hybrid storage device during the write operation, the control logic writes at least a portion of the block of data to a logical address for the block of data in a second portion of the address space which maps to the flash memory. Note that the address space may be common to the external device and the hybrid storage device.

Abstract: Embodiments of the present invention relate to invoking and managing a failover of a storage account between partitions within a distributed computing environment, where each partition represents a key range of data for the storage account. The partitions affected by the failover include source partitions hosted on a primary storage stamp and destination partitions hosted on a secondary storage stamp, where the storage account's data is being actively replicated from the primary to the secondary storage stamp. Upon receiving a manual or automatic indication to perform the failover, configuring the source partitions to independently perform flush-send operations (e.g., distributing pending messages as a group) and then configuring the destination partitions to independently perform flush-replay operations (e.g., aggressively replaying currently pending transactions).

Abstract: Handling failure of a primary group at a first data center that is part of plurality of data centers providing triangular asynchronous replication, includes creating a data mirroring relationship between at least one storage volume at a second data center having a synchronous backup group that is part of the plurality of data centers and at least one storage volume at a third data center having an asynchronous backup group that is part of the plurality of data centers and resuming work at the second data center. Handling failure of a primary group at a first data center may also include synchronizing the at least one storage volume at the second data center with the at least one storage volume at the third data center prior to resuming work at the second data center.

Abstract: According to one embodiment, a method for error correction in a memory module having ranks is provided where each rank has memory devices. The method includes determining a first mark condition for a first rank of the memory module, the first mark condition based on one or more uncorrectable error occurring in a first memory device in the first rank, placing a first mark in the first memory device, determining a second mark condition for the first rank, the second mark condition based on one or more uncorrectable error occurring in a second memory device in the first rank, placing a second mark in a third memory device in a second rank of the memory module and configuring the first memory device to respond to commands directed to the second rank, wherein configuring the first memory device is based on placing of the first mark and the second mark.

Abstract: Embodiments of the invention provide a device and method for warm booting whereby data restoration occurs at the powering-on of the host, and can therefore be performed by the boot disk. Specifically, when the system is powered on, a backup controller will send a notification to a DMA controller indicating the data restoration is needed. The backup controller will automatically resorts contents of a backup storage device to main memory. During the process, when the host requests data, the DMA controller reads the data from the backup storage unit and sends it to the host. Then, once data restoration is complete, normal operations can commence.

Abstract: A first video messaging service, running on top of an operating system in a data processing system, automatically presents a first video message. After using the first video messaging service to present the first video message, the data processing system automatically determines whether the first video messaging service has become nonfunctional. In response to determining that the first video messaging service has become nonfunctional, the data processing system automatically uses a backup video messaging service to present a second video message. The backup video messaging service operates in a boot environment. In one embodiment, the data processing system is configured to provide digital signage, the first video messaging service presents content for the digital signage when the operating system is operational, and the second video messaging service presents content for the digital signage when the operating system is nonfunctional. Other embodiments are described and claimed.

Abstract: A system and method for performing automated testing of an application in a cloud environment. A controller initializes an manages a number of virtual machines (VM), each VM including a test engine. The controller retrieves configuration data, determines a number of VMs to deploy, and initializes the VMs. The controller manages each VM by providing test commands and monitoring the results. Each VM receives and executes the test commands. The system may be used to test interactive applications or non-interactive applications.

Abstract: A disaster recovery system can include a plurality of resources arranged in a cloud computing environment. Each of the resources can be assignable to function within the cloud computing environment as part of one or more media systems. A content intake service can be programmed to control delivery of an incoming media asset to the cloud computing environment. A monitoring and recovery process can be programmed to monitor a primary media system to which the incoming media asset is being provided and, in response to detecting a disaster recovery condition, the monitoring and recovery process can intelligently manage selected resources of the plurality of resources based on the incoming media asset being delivered to the primary media system.

Abstract: The performance to transfer data to external storage media in thin provisioning is enhanced. A storage apparatus is connected via a network to a host system writing of data and to a tape management apparatus for managing tape storage media for storing the data.

Abstract: A primary storage controller is maintained in a copy relationship with a secondary storage controller, wherein the primary and secondary storage controllers are coupled to a host that is configurable to use the secondary storage controller instead of the primary storage controller. The primary storage controller determines occurrence of at least one condition in the primary storage controller, wherein the at least one condition occurs prior to a failure of the host to perform an Input/Output (I/O) operation with respect to at least one storage volume of the primary storage controller. The primary storage controller communicates the occurrence of the at least one condition to the host, wherein in response to the communicating the host is configured to determine whether to use the secondary storage controller instead of the primary storage controller based on the occurrence of the at least one condition.

Abstract: A second controller is communicated with from a first controller via an interface. Storage is also communicated with from the first controller via the interface. The first controller is configured to be a master on the interface and the second controller and the storage are configured to be targets on the interface.

Abstract: Approaches for recovering nodes and adding new nodes to object stores maintained on one or more solid state devices. At a surviving node, in a cluster of nodes, replicating, to a recovering node in the cluster of nodes, all requests to modify data stored in a first data store thereon that are received by the surviving node. The surviving node performing a bulk copy operation to copy data, stored in the first data store, to a second data store maintained on the recovering node. The surviving node (a) replicates all requests to modify data received by the surviving node and (b) performs a bulk copy operation in parallel.

Abstract: A container system and a monitoring method for the container system are provided. The container system includes a plurality of servers and a master server node. The servers are arranged in N areas. The master server node is coupled to the servers. The master server node selects one of a plurality of servers in an ith area to be a main node of the ith area. The main node collects temperature information of the servers in the ith area to transmit highest temperature information to the master server node. When the master server node cannot connect to the main node, the master server node selects one of other servers connected to the master server node in the ith area to be a replacing node, and adjusts the replacing node to be the main node of the ith area to collect the temperature information in the ith area continuously.

Abstract: An application instance identifier is employed with various systems and methods in order to provide a requestor with continuous access to a resource when operating in a client clustered environment. A requestor residing on a first client may attempt to access a resource. The first client sends a request to access the resource. The request may be associated with an application instance identifier that identifies the requestor. At some point, the first client fails and the requestor is associated with a second client via a failover mechanism. The second client sends a second request to access the resource on behalf of the requestor. The second request is associated with the requestor's application instance identifier. The application instance identifier is used to identify the second request as belonging to the same requestor as the first request, thereby granting the second request to access the resource while avoiding a conflict situation.

Abstract: A system includes a source storage device, a target storage device, a host coupled to the source storage device and the target storage device, and a first migration device coupled to the source storage device and the target storage device. The first migration device includes a first virtual storage device. The first migration device is configured to migrate data from the source storage device to the target storage device, and the first virtual storage device is configured to receive write access requests for the data from the host during the data migration and send the access request to the source storage device and target storage device.

Abstract: A standby server, a first main server, and a second main server to control shared input/output (I/O) adapters in a storage system are provided. The standby server is in communication with the first main server and the second main server, and the storage system is configured to operate as a dual node active system. The standby server is activated in response to receiving a communication from the first main server of a fail mode of the second main server. Systems and physical computer storage media are also provided.