Abstract: An information handling system may include a processor; a network interface; and a physical storage resource having data stored thereon that is usable by a virtual resource that is executable on the processor. The network interface may accelerate migration of the data to a destination system by, in response to a command from a virtual machine manager: offloading, from the processor, a copying process configured to copy the data to the destination system; tracking portions of the data that are changed by the virtual resource during the copying process; notifying the virtual machine manager that a designated checkpoint has been reached in the copying process; causing the virtual resource to pause; completing the copying process; and causing the virtual resource to resume and use the copied data at the destination instead of the data on the physical storage resource.

Abstract: Provided are a computer program product, system, and method for replication of versions of an object from a source storage to a target storage. A source retention policy indicates at least one source retention requirement to determine when to expire versions of an object at the source storage and a target retention policy indicates at least one target retention requirement to determine when to expire versions of the object at the target storage. The source and target retention requirements for versions of the object are different. The source retention policy is used to expire at least one version of the object at the source storage to satisfy the at least one source retention requirement. A number of the versions of the object maintained at the source storage and target storage differ due to the different source and target retention requirements.

Abstract: A robotic system is described for determining whether a flexible instrument has buckled. The robotic system comprises a medical instrument comprising an elongate body, and further comprises a first sensor placed in a first portion of the elongate body, and a controller. A command is directed to the elongate body. The first sensor generates sensor data providing information regarding a first measured status of the portion of the elongate body. The controller receives sensor data generated from the first sensor, and compare the first measured status with a first expected status expected to be caused by the command; and responsive to the first measured status deviating from the first expected status one of more or less than a first associated threshold, determine that the elongate body has buckled.

Abstract: Embodiments relate to systems and methods for tracking local and remote file usage, and aggregating the resulting file usage statistics for presentation to a user. The operating system of a local computer can cause presentation of a merged list of unified file usage information, wherein the merged list of unified file usage information comprises a first representation of the local file associated with local file usage information and a second representation of a Web application file associated with remote file usage information from a remote network host.

Abstract: Methods and apparatus are disclosed for controlling distributed software applications implementing asynchronous replication of shared data objects. Each shared data object has a distinct token. A token has respective states (active or inactive) at each computing system sharing the data object. At most one computing system can have the token active at any time; possessing an active token allows a computing system to update the shared data object. Counters maintain state across the computing systems, and semantic checks specific to a class of data objects (or, a single object) ensure consistency of updates across computing systems. Token activation requests and update replication requests are supported. Participating computing systems can have asymmetric or symmetric roles.

Abstract: According to certain aspects, a method can include creating a backup copy of data associated with a virtual machine (VM) on one or more secondary storage devices, wherein the backup copy includes corresponding secondary copies of a plurality of files associated with the VM; analyzing metadata associated with the secondary copies to determine which of the plurality files are eligible to be removed from the primary storage device; in response determining that one or more files are eligible to be removed from the primary storage device, for respective file of the one or more files: determining whether the respective file has been changed since a first time at which the backup copy of the data associated with the VM was created; in response to determining that the respective file has not changed since the first time, removing the respective file; and adding a file placeholder for the removed file.

Abstract: Retention of events of an ordered event stream is disclosed. Expiration of events stored in a segment of an ordered event stream (OES) can be desirable. New events are added to a head of an OES segment, and pruning events from a tail of the OES segment can be valuable. Processing applications can register a processing scheme for a segment, e.g., at-least-once processing, exactly-once processing, etc., and can generate checkpoints indicating a degree of advancement in processing events of the segment. The ordered event stream can determine a cut point indicative of a progress point, that before which, events of an OES can be marked as ready for expiration. However, events that are marked for expiration can be retained to allow processing based on a checkpoint, e.g., expiration of the event can be refused until there is an assurance the event was read by the processing application.

Abstract: An apparatus includes a memory and a hardware processor. The memory stores a plurality of logging rules. Each logging rule assigned to a tier of a multi-tier platform. The processor receives source code for an application configured to execute on a plurality of tiers of the multi-tier platform and detects, within the source code, an entry point and an exit point for a tier of the plurality of tiers. The processor determines, based on the plurality of logging rules, a first attribute that is to be logged during execution in the tier and a second attribute that is not to be logged during execution in the tier and inserts, between the entry point and the exit point in the source code, logging code that, when executed, logs the first attribute and hides the second attribute.

Abstract: Methods, computer program products, and computer systems for the management of data references in an efficient and effective manner are disclosed. Such methods, computer program products, and computer systems include receiving a change tracking stream at the computer system, identifying a data object group, and performing a deduplication management operation on the data object group. The change tracking stream is received from a client computing system. The change tracking stream identifies one or more changes made to a plurality of data objects of the client computing system. The identifying is based, at least in part, on at least a portion of the change tracking stream. The data object group represents the plurality of data objects.

Abstract: A method and system for verifying state monitor reliability in hyper-converged infrastructure (HCI) appliances. Specifically, the method and system disclosed herein entail using a supervised machine learning model—i.e., a classification decision tree—to accurately distinguish whether conflicting event notifications, logged across multiple state monitors tracking state on an HCI appliance, are directed to a real event or a non-real event. The classification decision tree, generated based at least on information gains calculated for the multiple state monitors, may reflect which state monitor(s) is/are more reliable in accurately classifying the conflicting event notifications.

Abstract: Methods, systems, and computer programs encoded on computer storage medium, for identifying, during a particular boot of an information handling system, basic input/output system (BIOS)-level events, each BIOS-level event associated with a different BIOS log event source; for each BIOS-level event: creating, by a respective driver computing module associated with the BIOS-level event, event data for the BIOS-level event; calling, by the respective driver computing module associated with the BIOS-level event, a dispatcher protocol to provide the event data associated with the respective driver computing module to a dispatcher computing module; placing, by the dispatcher computing module, each of the event data in a temporary data store, wherein each of the event data is unaltered; and creating, by the dispatcher computing module, a database log of the event data, including aggregating each of the event data to generate a sequence of events related to the particular boot of the IHS.

Abstract: In the presence of a network fault condition (130) preventing communication between a communication device (106) and a network device (200) of a first network (102), a method (400) includes receiving a heartbeat request (128) from the communication device requesting permission for the communication device to perform a device operation. The method further includes obtaining device state data (110) associated with the communication device and determining whether the communication device is permitted to perform the device operation based on the device state data associated with the communication device. When the communication device is permitted to perform the device operation, the method also includes transmitting a heartbeat confirmation signal (126) to the communication device. The heartbeat confirmation signal permits the communication device to perform the device operation.

Abstract: Embodiments of this application provide a method for determining route flapping information, to determine route flapping information based on parameter information reported by a routing device. The method in the embodiments of this application includes the following steps: receiving parameter information sent by each of at least one routing device, where parameter information sent by any routing device includes at least one of protocol packet information, count information, and identity identification information of the any routing device; and determining route flapping information of a target routing device based on the parameter information sent by each of the at least one routing device, where the target routing device is one of the at least one routing device.

Abstract: A technique provides efficient data failover by creation and deployment of a protection policy that ensures maintenance of frequent common snapshots between sites of a multi-site data replication environment. A global constraint optimizer executes on a node of a cluster to create the protection policy for deployment among other nodes of clusters at the sites. Constraints such as protection rules (PRs) specifying, e.g., an amount of tolerable data loss are applied to a category of data designated for failover from a primary site over a network to a plurality of (secondary and tertiary) sites typically located at geographically separated distances. The optimizer processes the PRs to compute parameters such as frequency of snapshot generation and replication among the sites, as well as retention of the latest common snapshot maintained at each site to create a recovery point and configuration of the protection policy that reduces network traffic for efficient use of the network among the sites.

Abstract: Failover methods and systems for a networked storage environment are provided. In one aspect, a read request associated with a first storage object is received, during a replay of entries of a log stored in a non-volatile memory of a second storage node for a failover operation initiated in response to a failure at a first storage node. The second storage node operates as a partner node of the first storage node. The read request is processed using a filtering data structure that is generated from the log prior to the replay and identifies each log entry. The read request is processed when the log does not have an entry associated with the read request, and when the filtering data structure includes an entry associated with the read request, the requested data is located at the non-volatile memory.

Abstract: The current document is directed to methods and systems that carry out live migration of multi-node applications in distributed-computing systems, including cloud-computing applications in cloud-computing facilities. The disclosed methods and systems employ an installer/agent and a data-transformation component to install new versions of a multi-node application within a distributed computing system and to then warm start each application-provided service within the newly installed new-version application nodes. Following a data sync operation, each warm-started application service is brought online to service subsequently received service requests as older-version corresponding services of current application nodes complete request services and terminate, providing live migration from an older version multi-node application to a new-version multi-node application without service-provision interruption.

Abstract: Systems and methods facilitating separation of dataset creation from movement in file replication are described herein. A method as described herein can include scheduling, by a first system operatively coupled to a processor, a first transfer of a dataset to a second system at a first time according to a first replication schedule; scheduling, by the first system, a second transfer of the dataset to a third system at the first time according to a second replication schedule; creating, by the first system, a snapshot of the dataset at a second time that is distinct from the first time according to a snapshot schedule that is distinct from the first replication schedule and the second replication schedule; and transferring, by the first system, at least a portion of the snapshot to the second system and the third system at the first time.

Abstract: A machine failure analyzing system includes a wearable electronic device is for a user to wear, a controlling and processing device provided with a machine history database and a failure causes analyzing unit. When a specific machine is malfunctioning or in a failure status, the controlling and processing device utilizes a machine status data collecting unit to collect machine status data from the specific machine. Subsequently, based on the machine status data, the failure causes analyzing unit is configured to find relative failure causes from the machine history database, thereby generating at least one troubleshooting solution. As such, under instructions of the troubleshooting solution, a field engineer who wears the wearable electronic device can achieve troubleshooting of the specific machine rapidly and precisely, without needing to spend time finding the failure causes.

Abstract: Embodiments of the present invention are directed to methods by which different services registered with cloud infrastructure may recover in case of disaster. Also directs procedures with which a resource provider may recover and rebuild its cloud resource information by scanning actual resources available. A resource provider will synchronize resources with a central service to get updated consumer and subscription information. In the scenario in which a central service fails and is recovered from backup, the central service should synchronize with resource providers to update its resource information.

Abstract: A database system may implement efficient database journaling using non-volatile system memory. An update to a database may be received, and log records indicating the update may be generated. A non-volatile portion of the system memory may be directly accessed to store the generated log records such that in the event of a failure of the database, the log records may be still maintained. Log records stored to the non-volatile portion of the system memory may be identified as durably persisted, in some embodiments. Log records may be identified and sent to block-based storage, in some embodiments. Recovery from a database system failure, in some embodiments, by obtaining log records from the non-volatile portion of system memory.

Abstract: Techniques for managing data involve determining multiple indications related to a status of a stripe, including a first indication to indicate whether a group of disks related to the stripe is available, a second indication to indicate whether to rebuild the stripe, and a third indication to retain a value of the first indication when a disk is unavailable; in response to detecting that a disk in the group of disks is unavailable, updating the first indication to indicate that the disk is unavailable; and in response to receiving a write operation, determining an updating to the third indication with a first value of the updated first indication; and in response to determining that the unavailable disk is available again within a predetermined time period, updating the second indication with a current value of the updated third indication, to indicate rebuilding of the stripe.

Abstract: Failover methods and systems for a networked storage environment are provided. A filtering data structure and a metadata data structure are generated before starting a replay of a log stored in a non-volatile memory of a second storage node, during a failover operation initiated in response to a failure at a first storage node. The second storage node operates as a partner node of the first storage node to mirror at the log one or more write requests received by the first storage node prior to the failure, and data associated with the one or more write requests. The filtering data structure identifies each log entry and the metadata structure stores a metadata attribute of each log entry. The filtering data structure and the metadata structure are used for providing access to a logical storage object during the log replay from the second storage node.

Abstract: Embodiments of the present invention are directed to methods by which different services registered with cloud infrastructure may recover in case of disaster. Also directs procedures with which a resource provider may recover and rebuild its cloud resource information by scanning actual resources available. A resource provider will synchronize resources with a central service to get updated consumer and subscription information. In the scenario in which a central service fails and is recovered from backup, the central service should synchronize with resource providers to update its resource information.

Abstract: A replicated block storage service provides durable and high performance network-attached storage replicated in two or more zones of a single region, and remains available despite a single zone failure. A probe file is generated to determine a health state of a replicated disk. When a disk is degraded, a lease is created indicating which replica is trusted and providing visibility to backend jobs to facilitate reconciliation of data between the first replica and the second replica. Moreover, degraded file markers are generated for use by the backend jobs in quickly identifying the data to be copied.

Abstract: Described are devices, systems and techniques for implementing atomic memory objects in a multi-writer, multi-reader setting. In an embodiment, the devices, systems and techniques use maximum distance separable (MDS) codes, and may be specifically designed to optimize a total storage cost for a given fault-tolerance requirement. Also described is an embodiment to handle the case where some of the servers can return erroneous coded elements during a read operation.

Abstract: The disclosure is directed to optimizing data writes in a distributed computing system, e.g., a social networking application. The system employs a write-ahead log (WAL) and a hybrid logical clock (HLC) together to improve data writes across data centers in the distributed computing system, including improving: (1) consensus monitoring and enforcement in replicating data across the data centers; (2) scalability of data writes, e.g., so that different data centers can together handle a sudden increase in data writes during specified periods and consistently maintain the time ordering of the data writes; (3) replication configuration of data centers so that client devices can specify a replication hierarchy per transaction, e.g., at the time of writing the data, rather than specifying at data center configuration time; and (4) a draining process to write transactions committed to the WAL to data storage systems in the data centers.

Abstract: Checking of a database snapshot of an active database is initiated. Thereafter, an anchor page associated with a most recent snapshot that links to a restart page is read. Subsequently, the linked restart page is read. It is then initially determined, based on the reading of the anchor page and the restart page, whether the snapshot is accurate. If it is initially determined that the snapshot is not accurate, the anchor page and the restart page are re-read until a final determination is made that whether the snapshot is accurate. Alternatively, if not is initially determined that the snapshot is accurate, then data is provided (e.g., displayed, loaded into memory, transmitted to a remote computing system, stored in physical persistence, etc.) that indicates that the snapshot is accurate.

Abstract: In one embodiment, a method includes receiving a request to perform a job from a second computing device, where the job includes one or more steps to be completed in a period, and where the request includes a job description for the job, storing the job description into a data store, retrieving a step description corresponding to one of the steps of the job to be performed from the data store, where each of the steps is performed by a corresponding worker system, sending the commands to the communication endpoint for the corresponding worker system, receiving a status update comprising results for the commands from the corresponding worker system, and storing the status update to the data store.

Abstract: The present disclosure provides a method and apparatus for transmitting data, and an electronic device thereof. The method includes identifying a first data object in a first object set in response to transmitting the first object set from a first storage area to a second storage area; and transmitting the first data object to the second storage area to indicate a start of transmission of the first object set from the first storage area to the second storage area.

Abstract: In various embodiments, a method of transferring referential data objects may be performed. The method may include receiving, by a system, a request to move a specified plurality of data objects from a source environment to a target environment within a multi-tenant database system. The system may identify, based on data relationships of the data objects, an unspecified plurality of data objects associated with the specified plurality of data objects. The unspecified plurality of data objects may have a referential relationship to the specified plurality of data objects. The system may initiate a transfer of the specified and unspecified data objects. The system may also identify a data field of a data object that has a source environment-specific data value and modify the data field to a target environment-specific data value.

Abstract: In some examples, data integrity verification may include obtaining, from an application for which data is stored in a primary storage volume, an identification of data blocks of the primary storage volume that are stored for the application in a snapshot storage volume that represents a snapshot of data stored in the primary storage volume. The identification may include references to locations of the data blocks in the primary storage volume. Using physical extent mappings and volume block addressing, the identified locations of the data blocks in the primary storage volume may be translated to locations of snapshot storage volume blocks of the snapshot storage volume. Based on the snapshot storage volume blocks that are read from the snapshot storage volume, integrity of corresponding backup copy blocks stored in a backup copy for backup of the primary storage volume may be verified.

Abstract: Network monitoring views can be recorded, replayed and shared. A monitoring system receives monitoring data, in response to which a monitoring view can be constructed. The monitoring data is maintained in memory or mass storage. One or more monitoring views can later be constructed in response to user preferences, even if those users would not have known to select those particular preferences or construct those particular monitoring views at the time. The monitoring views constructed in response to that monitoring data can be presented to users in a simulation of the problem, as if it were occurring at that time. Users can send particular monitoring views to others, with both the effects that the monitoring view can be preserved as part of a trouble report, and the persons receiving the monitoring view can have useful insight into what problem the user has pointed to.

Abstract: A method for aiding resolution of a transaction for use with a transactional processing system comprising a transaction coordinator and a plurality of grouped and inter-connected resource managers, the method comprising the steps of: in response to a communications failure between the transaction coordinator and a first resource manager causing a transaction to have an in-doubt state, connecting, by the transaction coordinator, to a second resource manager; in response to the connecting step, sending by the transaction coordinator to the second resource manager, a resolve request comprising a resolution for the in-doubt transaction; in response to the resolve request, obtaining at the first resource manager, by the second resource manager, a lock to data associated with the in-doubt transaction; and in response to the obtaining step, determining, by the second resource manager, whether the transaction is associated with the first resource manager.

Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for a distributed parallel processing database system that persists table data in memory to a distributed file system. A distributed parallel processing database system persists table data in memory to a distributed file system. A parameter of creating a database table specifies that data records in the database table and history of changes to the data records can be stored in memory as well as in the distributed file system. When the database table is populated or otherwise modified, data records and the history in memory are evicted to the distributed file system as log files and removed from memory. The log files can be designated as write-only, where the data records, once written, cannot be read by structured query language (SQL) queries, or as read-write, where the data records, once written, can be read by SQL queries.

Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for allocating a number of first containers to implement one primary segment instance each and a number of second containers to implement one mirror segment instance each. In one example system, the second containers are configured to have less computing resources than the first containers. The containers are distributed among a number of physical computers. The system receives an indication of a failure of a physical computer hosting a particular first container implementing a first primary segment instance. In response to receiving the indication, the system promotes a second mirror segment instance that is a mirror of the first primary segment instance to be a new primary segment instance. The system allocates additional resources to the particular second container implementing the promoted mirror segment instance.

Abstract: Techniques are disclosed to provide enhanced online security. When user authenticating information is provided to access secure content, a network server identifies the user via a website identifier. Some of the disclosed techniques leverage third party “cookie stitchers” to associate user data, which may include a website identifier, to the user's computing devices. If the cookie stitcher cannot identify a current computing device, or if a current website identifier does not match one stored in the user data, then 2-factor authentication (2FA) may be triggered. Other disclosed techniques leverage stored device management data (DMD), which uniquely identifies each computing device that is associated with a website identifier. These techniques allow the network server to block access to explicitly-identified computing devices, and to trigger 2FA unless specific computing device metrics, which are associated with a computing device, are matched to computing device metrics contained in the DMD.

Abstract: Logging includes: obtaining an event designating message (EDM) comprising: a set of keys, or a type of designation corresponding to the set of keys, or both; looking up a set of values associated with the set of keys in a key-value store storing a plurality of keys and their corresponding values; constructing an event using the set of keys and values corresponding to the set of keys; and outputting the constructed event.

Abstract: Embodiments of the present invention are directed to methods by which different services registered with cloud infrastructure may recover in case of disaster. Also directs procedures with which a resource provider may recover and rebuild its cloud resource information by scanning actual resources available. A resource provider will synchronize resources with a central service to get updated consumer and subscription information. In the scenario in which a central service fails and is recovered from backup, the central service should synchronize with resource providers to update its resource information.

Abstract: A data loading method and device, where the method includes obtaining a data loading request of a virtual machine after the virtual machine is started, the data loading requesting to load target data in an image file, determining whether the target data is stored in a volume and a snapshot corresponding to the virtual machine, where the snapshot is obtained based on a blank volume corresponding to the virtual machine when the virtual machine is created, writing the target data from a mirror server into the snapshot when the target data is not stored in the volume or the snapshot, reading the target data and transferring the target data to the virtual machine, obtaining virtual machine data generated by the virtual machine, and writing the virtual machine data into the volume. Hence, a conflict between new data and old data in a data loading process is resolved.

Abstract: Systems, methods, and non-transitory computer readable media are provided for facilitating improved analysis of remedial actions for faults. Fault information may be obtained. The fault information may characterize a fault of a device. The fault may be clustered into a fault type based on the fault information. A set of remedial actions taken for the fault type may be identified. A set of remedial effects of the set of remedial actions for the fault type may be determined. A timeline view of the fault type may be generated based on the set of remedial actions and the set of remedial effects. The timeline view may include a visual representation of effectiveness of the set of remedial actions. An interface, through which the timeline view of the fault type is accessible, may be provided.

Abstract: A system, topology, and methods to monitor the number of sessions hosted by servers in a distributed server architecture including counting the number of calls hosted by geographically distributed servers. Other embodiments may be described and claimed.

Abstract: A service provider launches an index analysis computing system instance to evaluate indexes generated by a virtual computing system server to identify events encountered by the server. In response to a notification from an index subject indicating presence of a new index for the server, the index analysis computing system instance obtains the index from a datastore and evaluates the index to identify a log for the server that specifies data that can be used to identify the events. The index analysis computing system instance obtains, from a second datastore, the identified log and used the log to identify the events. The index analysis computing system instance provides event data corresponding to the events to a data processing datastore where the data can be aggregated and processed.

Abstract: A storage system in one embodiment is configured to participate as a source storage system in a synchronous replication process with a target storage system. In conjunction with the synchronous replication process, the source storage system receives write requests from at least one host device. Responsive to a given write request being a multi-page write request, an entry is created in a first journal, where the first journal is utilized to ensure that the given write request is completed for all of the pages or for none of the pages. Responsive to the write request being a single-page write request, an entry is created in a second journal different than the first journal. An address-to-signature table is updated utilizing write data of the write request, and if the corresponding entry for the write request was created in the first journal, the entry is swapped from the first journal into the second journal, and the write data of the write request is sent to the target storage system.

Abstract: An aspect of resolving conflicts during recovery operations includes separating journal entries for first and second types of recovery operations into each of a first and second array. For each entry in the first array, an aspect includes taking a range lock of a designated number of the addresses and creating an entry in a table. For each entry in the second array, an aspect includes upon determining a corresponding sub-LUN has been locked for an entry in the first array, incrementing a count in the table. Upon determining the corresponding sub-LUN is not locked for the entry, an aspect includes taking the address lock for the entry in the second array. An aspect further includes opening gates for a corresponding address, performing a first recovery operation corresponding to the first type of recovery operation, and performing a second recovery operation corresponding to the second type of recovery operation.

Abstract: A semiconductor device includes an interrupt control circuit that receives a plurality of interrupt signals from the circuit blocks and outputs an interrupt request to the processor, and an interrupt monitoring circuit that corresponds to one of the interrupt signals and includes a setting circuit for setting a monitoring type and first and second monitoring periods. If the monitoring type indicates an asserted state of the interrupt signal, the interrupt monitoring circuit monitors the asserted state. If a first duration of the continuous asserted state exceeds the first monitoring period, the interrupt monitoring circuit detects the state as a failure. If the monitoring type indicates a negated state of the interrupt signal, the interrupt monitoring circuit monitors the negated state. If a second duration of the continuous negated state exceeds the second monitoring period, the interrupt monitoring circuit detects the state as a failure.

Abstract: A computing system includes nodes executing data processing programs that each process at least one stream of data units. A data storage system stores shared data accessible by at least two of the programs. Processing at least one stream using a first data processing program includes: processing a first stream of data units that includes multiple subsets of contiguous data units; initiating termination of processing within the first data processing program, between processing a first subset of contiguous data units and processing a second subset of contiguous data units adjacent to the first subset of contiguous data units within the first stream of data units; durably storing at least some changes to the shared data caused by processing the first subset of contiguous data units after determining that the termination of processing within the first data processing program has completed; and resuming processing within the first data processing program.

Abstract: The insertion into a data stream of collection records associated with multiple collections of data items in the data stream, for purposes of aiding in subsequent processing of the data stream by collections. Each collection record comprises a collection definition that does not overlap with the collection definition in any of the sequence of collection records including the collection definition of any neighboring collection record in the sequence of collection records. Each collection record also includes a data stream address range extending from the first data item to the last data item in the collection.

Abstract: The disclosure relates to systems, methods and computer-readable media for using system jobs for performing actions outside the constraints of batch compute jobs submitted to a compute environment such as a cluster or a grid. The method for modifying a compute environment from a system job disclosure associating a system job to a queuable object, triggering the system job based on an event and performing arbitrary actions on resources outside of compute nodes in the compute environment. The queuable objects include objects such as batch compute jobs or job reservations. The events that trigger the system job may be time driven, such as ten minutes prior to completion of the batch compute job, or dependent on other actions associated with other system jobs. The system jobs may be utilized also to perform rolling maintenance on a node by node basis.

Abstract: An integrated circuit includes one or more portions having error detection and error correction circuits and which is operated with operating parameters giving finite non-zero error rate as well as one or more portions formed and operated to provide a zero error rate.

Abstract: A computer-implemented method includes identifying a source data object of a distributed computing environment. The distributed computing environment includes two or more storage nodes. The source data object exists as two or more slices. At least one of the slices is replicated on at least two storage nodes. The computer-implemented method further includes associating the source data object with a tape. The tape is written by a tape drive controlled from the distributed computing environment. The computer-implemented method further includes copying the source data object to the tape by, for each source slice of the two or more slices, in sequence: selecting a source node of the two or more storage nodes whereon the source slice is replicated, mounting the tape drive to the source node, appending the source slice to the tape, and unmounting the tape drive. A corresponding computer program product and computer system are also disclosed.