Abstract: Among other aspects disclosed are a method and system for processing a batch of input data in a fault tolerant manner. The method includes reading a batch of input data including a plurality of records from one or more data sources and passing the batch through a dataflow graph. The dataflow graph includes two or more nodes representing components connected by links representing flows of data between the components. At least one but fewer than all of the components includes a checkpoint process for an action performed for each of multiple units of work associated with one or more of the records. The checkpoint process includes opening a checkpoint buffer stored in non-volatile memory at the start of processing for the batch. For each unit of work from the batch, if a result from performing the action for the unit of work was previously saved in the checkpoint buffer, the saved result is used to complete processing of the unit of work without performing the action again.

Abstract: In a computer system running a primary virtual machine (VM) on virtualization software on a primary virtualized computer system (VCS) and running a secondary VM on virtualization software on a secondary VCS, a method for the secondary VM to provide quasi-lockstep fault tolerance for the primary VM includes: as the primary VM is executing a workload, virtualization software in the primary VCS is: (a) causing predetermined events to be recorded in an event log, (b) keeping output associated with the predetermined events pending, and (c) sending the log entries to the virtualization software in the secondary VCS; as the secondary VM is replaying the workload, virtualization software in the secondary VCS is: (a) sending acknowledgements indicating that log entries have been received; (b) when the virtualization software encounters one of the predetermined events, searching the log entries to determine whether a log entry corresponding to the same event was received from the primary VCS, and if so, comparing data

Abstract: A method and apparatus for networked recovery system is described herein. In one embodiment, a process is provided to obtain a type of recovery selected by a user. A non-volatile partition of a storage volume containing a recovery disk image is accessed. The recovery disk image does not include an installation package. If the obtained type of recovery is a predetermined type of recovery, a network connection is established using the recovery disk image and data is downloaded over the network connection for the obtained type of recovery. The obtained type of recovery of the system is performed.

Abstract: A data management system or “DMS” provides an automated, continuous, real-time, substantially no downtime data protection service to one or more data sources associated with a set of application host servers. To facilitate the data protection service, a host driver embedded in an application server captures real-time data transactions, preferably in the form of an event journal that is provided to other DMS components. The driver functions to translate traditional file/database/block I/O and the like into a continuous, application-aware, output data stream. The host driver includes an event processor. When an authorized user determines that a primary copy of the data in the host server has become incorrect or corrupted, the event processor can perform a recovery operation to an entire data source or a subset of the data source using former point-in-time data in the DMS. The recovery operation may have two phases.

Abstract: An apparatus and method are described for defining, maintaining and displaying a checkpoint result set to facilitate identification of desirable checkpoints during system recovery. The checkpoint result set may be mapped to a user-customizable namespace. The user customizes the namespace by selecting one or more characteristics of desirable file system checkpoints. Being able to customize the namespace in this manner enables the user to be provided a more streamlined checkpoint result set in the event of data corruption. As a result an appropriate checkpoint can be more quickly selected for use in recovery.

Abstract: A method including: displaying operation icons representing operations to be performed, a user selecting and arranging the operation icons to define a flow of data between operations and to form a graphical representation of a process, the user specifying an operation icon as a transaction boundary node at the end of a transaction region, and compiling instructions to execute the arranged operations wherein the beginning of a transaction region acts as a roll back point in the event of an error occurring in the transaction region.

Abstract: An image forming apparatus includes a process execution unit which processes data input to a storage area by using the attribute of a process set in the storage area, an error event generation unit which generates an error event to execute an error process when an error is detected during execution of the process by the process execution unit, and an error process execution unit which executes an error process associated with the storage area in accordance with the error event generated by the error event generation unit.

Abstract: A method and apparatus for providing an undoable programming language. More specifically the present invention relates to providing a fully undoable programming language, where the language includes a fully undoable core language portion and a conventional language portion. In an embodiment of the present invention, a method of encoding a general-purpose undoable programming language to enable fully undoable instructions includes encoding a fully undoable core imperative language portion having a plurality of undoable core instructions, each of the plurality of undoable core instructions to perform at least one undoable operation upon execution, and the at least one undoable operation being fully undoable until final termination of a program written using any of the plurality of undoable core instructions.

Abstract: A computer system including a first storage system connected to a first host computer, a second storage system connected to a second host computer and a third storage system connected to the first and second storage systems. The second storage system sets transfer setting before an occurrence of a failure, the transfer setting being provided with a dedicated storage area to be used for transferring data to the third storage system by asynchronous copy in response to a failure at the first host computer. Before the start of data transfer between the second storage system and third storage system to be executed after an occurrence of the failure, the second storage system checks the dedicated storage area, data transfer line and transfer setting information, and if an abnormal state is detected, this abnormal state is reported to the host computer as information attached to the transfer setting.

Abstract: A method and system for automated disaster recovery in an information technology computing system including computing resources, is provided. One implementation involves logging system events in a journaling log file, filtering the events of the log file for each resource and storing the filtered log file, reading the filtered log file, and restarting from a backup file by applying the filtered events to a backup file for recovery.

Abstract: Techniques are disclosed relating to storing a log of write operations made to a first storage device by one of a plurality of host computers running an instance of a distributed application. The log of write operations is stored at a second storage device. The plurality of host computers communicate status information to the second storage device over respective communication paths. Upon a failure to communicate status information between one of the host computers and the second storage device, the second storage device reads from a predetermined location in the first storage device to determine whether the host computer is still performing write operations. If the second storage device reads an expected signature value written by the host computer, the host computer is deemed to have written data, which indicates that the host computer is operational but that the write operations have not been recorded by the second storage device.

Abstract: The invention provides a method for data recovery. In one embodiment, a memory comprises a plurality of pages for data storage. First, first data is obtained from a host. A first page for storing the first data is then selected from the pages of the memory. A start page link indicating the first page is then stored in the memory. The first data, a first page link indicating a next page, and first FTL fragment data corresponding to the first page are then written into the first page. Next data is then obtained from the host. The next data, a next page link indicating a subsequent page, and FTL fragment data corresponding to the next page are written into the next page.

Abstract: In a work-process tracking system, each of event-data collecting threads collects event data from each of work systems. A storing thread stores the event data collected in a database. When a termination instruction is received, a thread in operation is terminated. For example, when an instruction to start (or terminate) an event-data collecting process is received, a control unit initiates (or terminates) the event-data collecting thread. Similarly, when an instruction to start (or terminate) a storing process, the control unit initiates (or terminates) the storing thread.

Abstract: A method of logging and storing of a sequence of acquired X-ray image frame data in an X-ray imaging lab includes logging and updating image frame data related information in a non-volatile memory on a real-time basis upon completion of storage of each image frame data and deleting the logged information upon completion of storage of the sequence of X-ray image frames.

Abstract: A computer-implemented method for transparently restoring data using streaming may comprise identifying an attempt to access backed-up data that is not present on a computing device, transmitting a request to a server to restore the backed-up data, receiving the backed-up data from the server via streaming, and restoring the backed-up data to the computing device. A corresponding method for streaming backed-up data to a target computing device is also disclosed. In addition, corresponding systems and computer-readable media are also disclosed.

Abstract: A method, system, and computer program product for providing continuous data protection for write data supplied from a host incorporating a processor device to data storage in accordance with write input/output (I/O) of an owning application is provided. The write data is identified as one of a synchronous candidate and an asynchronous candidate. The write data identified as the one of the synchronous candidate and the asynchronous candidate is transferred to at least one sidefile. The write data transferred to the at least one sidefile is secured in a nonvolatile storage journal. The nonvolatile storage journal is preset with a timeout limit applicable to write data identified as the synchronous candidate. If the timeout limit is exceeded, a loss mitigation operation to safeguard the write data identified as the synchronous candidate is performed.

Abstract: A management server includes a meta rule for identifying an event to be a root cause and a failure recovery method that corresponds to the meta rule for an event capable of occurring in a plurality of node apparatuses, and also displays a cause event to be a root cause of an event detected by the management server, and a method for recovering from this cause event.

Abstract: A method and apparatus for incrementally backing up database files is described. In one embodiment, the present invention replicates an original database file for the purpose of creating a backup database file. The backup database file is subsequently stored in a data store and the original database file is monitored for at least one change (i.e., new e-mail message). In response to a detected change, the change to the original database file is copied to the backup database file so that the two database files are replicas of each other.

Abstract: A file server architecture decouples logical storage from physical storage and provides proactive detection and containment of faults, errors, and corruptions in a file system, in order to enable in place (online) and non-intrusive recovery. The file system is built upon a thinly provisioned logical volume, and there are stored three copies of the metadata defining the logical volume in order to provide quick, deterministic, and reliable recovery from a faulted system. A first copy of the metadata is distributed among all of the slices of physical storage allocated to the logical volume. A second copy of the metadata is stored in a root slice of the logical volume. A third copy of the metadata is stored separate from the slices of physical storage allocated to the logical volume.

Abstract: Systems and methods of collecting and aggregating log data with fault tolerance are disclosed. One embodiment includes, one or more devices that generate log data, the one or more machines each associated with an agent node to collect the log data, wherein, the agent node generates a batch comprising multiple messages from the log data and assigns a tag to the batch. In one embodiment, the agent node further computes a checksum for the batch of multiple messages. The system may further include a collector device, the collector device being associated with a collector tier having a collector node to which the agent sends the log data; wherein, the collector determines the checksum for the batch of multiple messages received from the agent node.

Abstract: A method, apparatus, and system of a sequencing technique to account for a clock error in a storage area network are disclosed. In one embodiment, a system of a backup server includes a processing module to examine a data timestamped with a sequence of characters denoting a time according to a clock source, an analysis module to determine that the data has been timestamped at an earlier time than an other data previously received, a substitution module to provide the data an incremental sequence number placed with the data using an algorithm until a new data is received that includes a future timestamp with a later timestamp than the timestamp of the other data, and a storage module to store the data.

Abstract: Techniques are presented for embedding testing and debugging features within a service. A user service is modified to include record and playback features. When a record feature is activated, actions and state transitions, which occur within the user service, are monitored and recorded. These actions and transitions are represented within a script. During playback, the actions and state transitions are automatically replayed within the user service by accessing operations of the user service that are represented or mapped within the script.

Abstract: The active server A101 notifies its own operating status to the administration server 106, and the administration server 106 acquires a snapshot and copies a disk according to the policy established by a user. When the active server A101 or the active disk 113 fails, the administration server 106 chooses a backup server A104 and a status storage disk A114 to be booted and restarts them by using the snapshot according to the policy.

Abstract: In one embodiment, a computer accessible medium stores a plurality of instructions including instructions which, when executed: track dependencies among a plurality of assets; and responsive to an identification of an asset for potential recovery (the “selected asset”), identify an asset dependency set corresponding to the selected asset. The asset dependency set comprises at least a subset of the plurality of assets, wherein each asset in the subset has a dependency with the selected asset. In some embodiments, one or more of the following may be provided: tracking asset dependencies and presenting the asset dependency set to the user; pruning the asset dependency set to a recovery set identifying the asset dependency set; generating the recovery order (optionally optimized); initiating the recovery according to the recovery order; performing recovery steps; generating the recovery plan and/or executing recovery plans.

Abstract: In order to reproduce the past operations of a medical system, a reproduction test service apparatus stores a plurality of past log files directly or indirectly supplied from the medical system in a log file storage unit and reproduces the past operations of the medical system on a pseudo X-ray CT system in accordance with the stored log files.

Abstract: A computer-implemented method for storing information that identifies the state of health of a computing system at the time a backup of the computing system is created may comprise: 1) identifying a backup of the computing system, 2) performing an evaluation of the computing system's health, and then 3) storing health information that identifies the state of health of the computing system when the backup was created as metadata to the backup. Similarly, a method for determining whether to restore a backup of a computing system based on health information may comprise: 1) identifying a backup of the computing system, 2) identifying health information stored as metadata to the backup that identifies the state of health of the computing system when the backup was created, and 3) determining, based on the health information, whether to restore the backup. Corresponding systems and computer-readable media are also disclosed.

Abstract: Embodiments of the present disclosure provide methods and systems for detecting and correlating log events, configuration changes and conditions producing alerts within a virtual infrastructure. Other embodiments may be described and claimed.

Abstract: A method, apparatus, and computer program product for setting and implementing a policy to compress the history of data on a temporal volume is described.

Abstract: A storage apparatus for storing data includes a plurality of physical media provided with storage areas to store data, a storage group determining unit configured to determine, upon detecting a request to write new data to a virtual volume to be accessed, a storage group from which to allocate storage area by selecting a storage group from among a plurality of storage groups made up of the plurality of physical media, wherein the selected storage group is other than any storage groups that include a physical medium where a failure has occurred, and a storage area allocator configured to allocate storage area on the physical media existing within the storage group that was determined by the storage group determining unit to the virtual volume, the size of the storage area corresponds to the data size of the new data.

Abstract: An apparatus, system, and method are disclosed for restoring cluster server data at a volume level. A setup module opens at least one source volume of a cluster server for a volume-level restore, flushes each buffer for the at least one source volume, closes the at least one source volume, disables file system checks for the cluster disks, saves disk signatures of the cluster disks, and disables device-level checks for the cluster disks. A copy module copies data with a volume-level restore from the at least one snapshot volume to the at least one source volume. A reset module rewrites the saved disk signatures to the cluster disks, re-enables the device-level checks for the cluster disks, and resets at least one volume attribute on the at least one source volume.

Abstract: A data processor includes a cache record error storage and a hard error storage having at least one record error storage and at least one hard error record, respectively, both for keeping track of errors detected when accessing cache records. When an error is first detected, one of the error records in the cache record error storage is allocated to store a cache record identifier for that cache record, and an associated count value is set to a first value. If an error is detected when accessing a cache record, a correction operation is performed in respect of that currently accessed cache record, and access to that currently accessed cache record is then re-performed. If the count value reaches a predetermined threshold value, then the cache record identifier is moved from the cache record error storage to an error record of the hard error storage.

Abstract: Systems, methods, and computer program products are described that are capable of recovering an asynchronous process after an error occurs with respect to the process. For example, the process may be re-initiated upon detection of the error. The re-initiated process is capable of not repeating tasks of the process that were completed prior to the occurrence of the error.

Abstract: A gaming machine includes a processor adapted to execute a program of a game; a biometric reader configured to capture first biometric data from the player, and a trusted cache. The trusted cache includes a nonvolatile memory that is configured to store the first biometric data; a context data save engine configured to save the context of the program to the nonvolatile memory and to associate the stored first biometric data with the saved context of the program upon the processor receiving a request from the player to suspend game play, and a context data recovery engine configured to recover the saved context from the nonvolatile memory and to cause continued execution of the program from the recovered saved context upon the biometric reader capturing second biometric data from the player that matches the stored first biometric data and receiving a request from the player to resume game play.

Abstract: Database management systems, methods, and program products that exploit time dependent sequential database management system processes to ensure presentation of the same data or view to one or a plurality of users through sequencing asynchronous database management operations such as recovery and replication. Sequencing is accomplished through the use of entries in sequential logs, including transaction logs, recovery logs, and other data recovery tools and applications. Uses include managing data migration and data replication.

Abstract: A storage system maintains a journal and a snapshot of one or more data volumes. Two journal entry types are maintained, an AFTER journal entry and a BEFORE journal entry. Two modes of data recovery are provided: “fast” recovery and “undo-able” recovery. A combination of both recovery modes allows the user to quickly recover a targeted data state.

Abstract: A method and a system of improving recoverability of a dataset associated with a multi-tier storage system are provided. Updates to a dataset are stored in first storage. The dataset and a point-in-time copy of the dataset reside on second storage, and the first storage provides higher reliability than the second storage. The dataset is restored using at least a subset of the stored updates in combination with the point-in-time copy in the event that the dataset is lost.

Abstract: A backup VM is allowed to enter live execution mode at instruction boundaries but not in the middle of emulation of a single instruction. This is accomplished by having the last log entry of multiple entries generated during emulation of an instruction to have an indication of a “go-live” point and by having the backup VM not replay log entries provided by the primary VM beyond the log entry that indicates the “go-live” point.

Abstract: Storing, retrieving, transmitting and receiving data (20) by a) separating the data into a plurality of data subsets (A, B); b) generating parity data (P) from the plurality of data subsets (A, B) such that any one or more of the plurality of data subsets may be recreated from the remaining data subsets and the parity data (P). Steps a and b may be repeated on any one or more each of the plurality of data subsets and parity data providing further data subsets and further parity data; and d) storing each of the further data subsets and further parity data in separate storage locations (380) or transmitting the further data subsets and further parity data.

Abstract: A computer system including a first storage system connected to a first host computer, a second storage system connected to a second host computer and a third storage system connected to the first and second storage systems. The second storage system sets transfer setting before an occurrence of a failure, the transfer setting being provided with a dedicated storage area to be used for transferring data to the third storage system by asynchronous copy in response to a failure at the first host computer. Before the start of data transfer between the second storage system and third storage system to be executed after an occurrence of the failure, the second storage system checks the dedicated storage area, data transfer line and transfer setting information, and if an abnormal state is detected, this abnormal state is reported to the host computer as information attached to the transfer setting.

Abstract: Unique information including a logical type name is stored in a user data area of a management area as a media of the alternative disk drive to become an alternative of the storage device. Upon using the alternative disk drive, a disk controller reads the unique information of the alternative disk drive, and determines that copy back is unnecessary when the rotating speed and capacity belonging to the unique information of the alternative disk drive are the same as the rotating speed and capacity of the failed disk drive belonging to RAID, and otherwise determines that copy back is necessary.

Abstract: Methods, systems, and computer-readable media are disclosed for operating system-based application recovery. A particular method saves an application state of an application executing at a computer. When a failure of the application is detected, the operating system provides an option to initiate recovery of the application by reverting to the saved application state. When the option to initiate recovery is selected by a user of the computer, the operating system recovers the application by reverting to the saved application state.

Abstract: An example of a method for error tracking includes sending a data object to a first location. This example also includes determining if the data object was successfully stored at the first location, and if so, storing meta data corresponding with the data object, wherein the meta data includes first path information. This example of the method also includes sending the data object to a second location. This example further includes determining if the data object was successfully stored at the second location, and if so, adding second path information to the meta data corresponding with the data object, to update the meta data. Some examples of the invention may be called a data centric error tracking and problem analysis method (and system), because the error tracking is generally based on the path traveled by the data.

Abstract: A method and apparatus for transactions during a data migration. The transfer of data from an old database to a new database is structured as a set of small transactions. The transactions can be structured in a hierarchy of dependent transactions such that the transactions are nested or similarly hierarchical. A migration manager includes a set of data conversion methods or processes that enable the conversion of data from a format of an old database to that of a new database. The conversion process generates the nested transactions to resolve dependencies between records such as primary and foreign keys. The method and system provides a higher level of granularity in transaction size, providing the ability to transfer records individually and resolve the dependencies in such transactions without requiring a large mapping of an entire data set in the old database to an organization in the new database.

Abstract: A mirror destination storage server receives mirror update data streams from several mirror source storage servers. Data received from each mirror is cached and periodic checkpoints are queued, but the data is not committed to long-term storage at the mirror destination storage server immediately. Instead, the data remains in cache memory until a trigger event causes the cache to be flushed to a mass storage device. The trigger event is asynchronous with respect to packets of at least one of the data streams. In one embodiment, the trigger event is asynchronous with respect to packets of all of the data streams.

Abstract: The method begins with a processing unit receiving an encoded slice for storage. The method continues with the processing unit determining whether to store the encoded slice in one of a first set of memory devices or in one of a second set of memory devices based on metadata associated with the encoded slice, wherein the first set of memory devices are continually active and the second set of memory devices are selectively active. The method continues with the processing unit stores the encoded slice in the one of the second set of memory devices when the encoded slice is to be stored in the one of the second set of memory devices. The method continues with the processing unit de-activating the one of the second set of memory devices, in accordance with a deactivation protocol, after storing the encoded slice.

Abstract: An information processing apparatus able to recover consistency between file entity data and file management information when detecting an inconsistency therebetween at start-up of the apparatus, while reducing unavailable time of the apparatus as much as possible. A CPU of the information processing apparatus executes a base program stored in a storage unit to check for an abnormality in consistency between file entity data and file management information which are stored in another storage unit. If an abnormality is detected, the CPU executes a program for degeneracy operation stored in still another storage unit to perform a degeneracy operation, and recovers the consistency.

Abstract: A migration destination storage creates an expansion device for virtualizing a migration source logical unit. A host computer accesses an external volume by way of an access path of a migration destination logical unit, a migration destination storage, a migration source storage, and an external volume. After destaging all dirty data accumulated in the disk cache of the migration source storage to the external volume, an expansion device for virtualizing the external volume is mapped to the migration destination logical unit.

Abstract: To trace an activity through multiple components or applications that may be involved in the performance of the activity, an activity identifier can be generated and utilized by the various components or applications. Each can generate its own activity identifier to minimize changes to existing interfaces. When logging of events has been activated, each application or component can provide, to an event store, an indication of the activity identifier it is using for a given activity. If a preceding or subsequent component utilizes a different activity identifier for aspects of the same activity, a link between the two activity identifiers can be communicated to the event store. Subsequently, examination of the event store can filter out irrelevant entries based on the activity identifiers. A graph linking the various related activity identifiers can be created and only those events associated with activity identifiers not in the graph can be filtered out.

Abstract: A primary coordinator generates a prepare message for a two-phase commit distributed transaction, the prepare message including an address of a backup coordinator. The primary coordinator maintains a transaction log of the distributed transaction, wherein the transaction log is accessible to both the primary coordinator and the backup coordinator. The prepare message is sent to a plurality of participants. The primary coordinator fails over to the backup coordinator without interrupting the distributed transaction.

Abstract: According to an embodiment of the invention, a remote management device is integrated into a processing system, such as a filer or other storage server, and the remote management device and administrative data (such as console data) generated by the processing system are accessible even if the processing system becomes inoperable. The processing system includes a console port that outputs administrative data in the form of administrative data during system operation. The remote management device is accessible remotely, for example through a local area network (LAN) or a wide area network (WAN) such as the Internet, or a combination of networks. The remote management device intercepts the administrative data output by the console port and stores the data into memory on the remote management device.