Abstract: A primary active manager can manage a first copy of a database in a first computer system cluster according to a set of management rules that provide for an active copy and one or more passive copies of the database at a given time. The primary active manager can also manage a second copy of the database in a second computer system cluster according to the rules. The rules can allow the first copy of the database or the second copy of the database to be the active copy if one or more criterion in the rules is met for that active copy. The first copy can be designated as the active copy and the second copy can be designated as a passive copy. A failure of the first copy can be detected, and in response, the second copy can be automatically designated as the active copy.

Abstract: A system, method and program to improve the processing speed of a simulation system. A processing system finds an entry point so that functional blocks cover a broad range. The processing system places code of a look-ahead dispatcher for assigning processing. The look-ahead dispatcher monitors an input state at the entry point to determine whether the input state is a stable state. If the input state is stable, the look-ahead dispatcher calls an adaptive execution module at some frequency or otherwise calls an idle execution module. The adaptive execution module performs processing on multiple timestamps at once. When a discrete system receives an input event, the look-ahead dispatcher calls a recovery execution module. Based on the input event on that occasion, the timestamp, and a value stored in a state vector, the recovery execution module calculates a state for which recovery is performed.

Abstract: A file operations engine is provided that manages many user interactions with their files via a computer system. The operation engine may provide a user with the option to keep both files that have a file name conflict. It may further permit the user to rename a file involved with a file name conflict. The operations engine may also automatically rename one of the files of a file name conflict by appending a character to a root of the filename. The character may include the lowest integer available for the root in a destination for the files. The operations engine may provide the option to keep both files as part of a pre-calculation of potential errors for a requested operation. The operations engine may place file name conflicts in an error queue and permit the user to select an option to keep both files after the conflict is encountered.

Abstract: A maintenance free storage container includes a plurality of storage servers, wherein the maintenance free storage container allows for multiple storage servers of the plurality of storage servers to be in a failure mode without replacement. The maintenance free storage container further includes a container controller operable to manage failure mode information of the plurality of storage servers, manage mapping of a plurality of virtual storage servers to at least some of the plurality of storage servers based on the failure mode information, communicate storage server access requests with a device external to the maintenance free storage container using addressing of the plurality of virtual storage servers, and communicate the storage server access requests within the maintenance free storage container using addressing of the plurality of storage servers.

Abstract: A running of an application resource of a first site of at least two sites is stopped from accessing a storage device of the first site. A running of a replication resource is brought to a stop. The replication resource is configured to control a replication of data between the storage device on the first site on which data from the running application resource on the first site are stored to the storage device on the second site. A replication request is submitted to the automation engine for changing a replication direction to run from the second site to the first site. The application resource is started on the second site only after changing the replication direction to start from the storage device on the second site instead of from the storage device of the first site.

Abstract: Communication is arrested between a source data entity and a replicated data entity at a location declared in a DR mode. The DR mode is negotiated to a central replication management component as a DR mode entry event. The DR mode entry event is distributed, by the central replication management component, to each member in a shared group. The DR mode is enforced using at least one replication policy.

Abstract: Systems and methods of managing problem determination (PD) data provide for obtaining PD data from a plurality of data sources via an input/output (I/O) interface of a data management device and storing the PD data to a memory of the data management device. In addition, an automated diagnostic analysis of the PD data may be conducted on the data management device. An automated discovery manager may provide the ability to find new sources of PD data and to either reconfigure remote systems to send data to the data management device or to automatically retrieve data from remote systems on a configurable schedule. Dynamically updateable database of symptom information can also be used, wherein the data management device may include a dynamically updateable set of analysis modules with which to conduct analysis on the PD data.

Abstract: A method for assisting an administrator to identify files suspected of causing instability on a personal computer comprises periodically creating file content sharing logs concurrently with archiving files of a plurality of personal computers by de-duplicating, when a notification is received regarding instability of a personal computer, then analyzing archive file content sharing log of the personal computer made immediately after receiving the notification for unique system and program files, missing files and newly installed files to generate an instability report. A missing or corrupted file can be restored back on the unstable personal computer by performing a backup restore operation on the unstable personal computer.

Abstract: Replicas of a database are synchronized. A failure of update data is detected from a first replica to be applied to a second replica. A cause of the failure is determined. The cause of the failure is resolved. The replicas of the database are synchronized without requiring manual intervention.

Abstract: A technique of backing up data for networked storage devices using de-duplication is disclosed in which a communication device divides a to-be-stored new file into data blocks, defines and updates a statistical value representative of a history of reference to each data block within previous files, and transmits the statistical value to another communication device. The communication device, upon reception of the statistical value, selects a preloaded data block, based on the received statistical value, and transmits to another communication device a copying request for making a copy of a real data block identical to the preloaded data block. The communication device, upon reception of the copy, stores the copy as the preloaded data block.

Abstract: A storage system of the present invention carries out remote copying among a plurality of sites, detects a new copy path when a failure occurs, and resumes remote copying. The storage system comprises a plurality of sites. Each site comprises a host and a storage controller. The controller of each site comprises a copy controller, a failure detector, a candidate detector, and a resume controller. The failure detector detects a failure that occurs in a remote copy configuration. The candidate detector detects a candidate for a copy path. The resume controller resumes remote copying using any one copy path from among copy path candidates detected in the respective sites.

Abstract: Replication techniques are presented. According to an embodiment of a method, a node of a replicated storage network is assigned to be an owner of a data block to issue write memory block commands. The network includes at least two nodes including the node assigned to be the owner. If a read memory block command is received to read the data block, a read_lock is issued for the data block, the data block is read, and the read_lock for the data block is released. If a write memory block command is received to write new data to the data block, a write_lock is issued for the data block, the data block is written and a version associated with the data block is incremented, and the write_lock for the data block is released.