Abstract: A folder scan system configured to identify modified folders in a storage module including a plurality of folders during an incremental backup scan is presented. The folder scan system is configured to identify modified folders using a learning-based technique. A related method is also presented.

Abstract: A data storage device includes a memory device and a controller coupled to the memory device. The controller is configured to compare a first copy of a boot partition to a second copy of the boot partition. The first copy of the boot partition and the second copy of the boot partition each comprises a same number of a plurality of boot chunks. The boot partition corresponds to data of a boot operation of a host device. The controller is further configured to mark one or more of the compared boot chunks that equals or exceeds a similarity threshold and update a reliability index based on the marking. Based on the marking and the reliability index, the controller may increase or decrease an amount of error correction needed for the boot data.

Abstract: A object data backup and restore method and system include receiving a request to restore a target object to a first point-in-time version; identifying a first snapshot of the cluster corresponding to the first point-in-time version; generating a second snapshot of the cluster upon receiving the request to restore the target object; determining data changes associated with the target object based on the first snapshot and second snapshot; scanning all objects associated with the cluster to determine one or more additional objects that are affected by restoring the target object due to object dependencies defined by a cluster configuration; generating a relationship graph for the one or more additional objects and the target object; and restoring the target object based on the data changes, the first snapshot and the relationship graph.

Abstract: A method and system is disclosed for backing up and maintaining electronic medical records for periods of temporary loss of connectivity between a healthcare facility and an eMAR/eTAR provider storing and maintaining medication administration records and treatment administration records for a healthcare facility.

Abstract: A memory tier is established in a cluster system having a deduplicated file system. The memory tier includes memory pages configured as huge pages, where writes to the huge pages are exported in a device file that is outside of a user process namespace within which processes of the deduplicated file system run. At least a portion of metadata generated by the deduplicated file system is written to the memory tier. The portion of metadata includes an index of fingerprints corresponding to data segments stored by the deduplicated file system to a storage pool. A determination is made that an instance of the deduplicated file system has failed. A new instance of the deduplicated file system is started to recover file system services by loading the index of fingerprints from the device file.

Abstract: A specification of a data protection intent is received. Configurations for a plurality of different data management services are automatically determined in an attempt to achieve the specified data protection intent. The determined configurations in the plurality of different data management services are automatically implemented.

Abstract: In some examples, a method of performing a backup of a group of relational databases comprises identifying the group of relational databases; identifying I/O traffic flowing into or out of the group of relational databases; temporarily freezing the I/O traffic flowing into or out of the group of relational databases; identifying a set of batch backup operations to be performed during the temporary I/O freeze; identifying relational dependencies between at least some databases in the group of relational databases; based on the identified relational dependencies, identifying, among the set of batch backup operations, a first sub-set of backup operations eligible to be performed in parallel, and a second sub-set of backup operations not eligible to be performed in parallel; conducting the backup, wherein conducting the backup comprises performing the identified first sub-set of backup operations in parallel and performing the identified second sub-set of backup operations sequentially; and unfreezing the I/O tra

Abstract: Responsive to determining that a step in an interaction sequence has below a threshold similarity to any step in a set of log sequences, a first log entry is caused to be generated. The first log entry is emitted responsive to execution of the step in the interaction sequence by the software application. Responsive to determining that a starting key action lacks a corresponding ending key action, a second log entry is caused to be generated. The second log entry is emitted responsive to execution of code related to the corresponding ending key action by the software application. Responsive to determining, using a trained anomaly detection model, that a keyword related to an injected fault is not present in resulting fault log data, a third log entry is generated. The third log entry is emitted responsive to execution of code related to the keyword by the software application.

Abstract: When a user exploits virtualization software and navigates through or to a redirected client drive in a remote session then the file management application may refresh the directory/folder content very slowly, spending significantly more time than expected according to the amount of data, network speed and latency. Whilst this refreshing is being performed no actions with the file management application can be performed by the user. Accordingly to address this a system or method are provided that cache metainformation for files, folders, and subfolders, e.g. upon a network resource, in a driver which responds to a query directory and other related requests by filling a provided buffer with the cached data. Further, this driver may filter out some particular files from the results if a filtering option is selected to further reduce latency.

Abstract: Transitioning between replication sources for data replication operations, including: delaying a transition from using a first data repository as a source for data replication to using a second data repository as the source for data replication after detecting that one or more storage operations directed to the first data repository have not been replicated to the second data repository; and promoting the second data repository as the source for data replication such that storage operations received after completing the transition are directed to the second data repository.

Abstract: Each redundancy group is constituted by one active program (storage control software of the active program) and N standby programs (N is an integer of two or more). Each of the N standby programs is associated with a priority to be determined as a failover (FO) destination. In the same redundancy group, FO is performed from the active program to the standby program based on the priority. For the plurality of pieces of storage control software including the active programs and the standby programs that change to be active by FO in the plurality of redundancy groups arranged in the same node, standby storage control software that can set each of the programs as a FO destination are arranged in different nodes.

Abstract: A BMC firmware security system includes a BMC coupled to a programmable circuit device and a first storage subsystem. In response to BMC initialization, the BMC uses a system identifier to verify that a license in the first storage subsystem authorizes the BMC to use BMC firmware in the BMC, uses branding identity information in the BMC to verify that the BMC is branded for the BMC firmware, determines that the programmable circuit device identifies the BMC firmware and, in response, the performs BMC initialization operations using the BMC firmware. A BIOS is coupled to the programmable circuit device and a second storage system. In response to BIOS initialization, the BIOS uses the branding identity information in the second storage subsystem to identify the BMC firmware, determines that the programmable circuit device identifies the BMC firmware and, in response, performs BIOS initialization operations.

Abstract: A fault tolerant computer system and method are disclosed. The system may include a plurality of CPU nodes, each including: a processor and a memory; at least two IO domains, wherein at least one of the IO domains is designated an active IO domain performing communication functions for the active CPU nodes; and a switching fabric connecting each CPU node to each IO domain. One CPU node is designated a standby CPU node and the remainder are designated as active CPU nodes. If a failure, a beginning of a failure, or a predicted failure occurs in an active node, the state and memory of the active CPU node are transferred to the standby CPU node which becomes the new active CPU node. If a failure occurs in an active IO domain, the communication functions performed by the failing active IO domain are transferred to the other IO domain.

Abstract: Techniques are provided to allow more sophisticated operations to be performed remotely by machines that are not fully functional. Operations that can be performed reliably by a machine that has experienced a hardware and/or software error are referred to herein as Remote Direct Memory Operations or “RDMOs”. Unlike RDMAs, which typically involve trivially simple operations such as the retrieval of a single value from the memory of a remote machine, RDMOs may be arbitrarily complex. The techniques described herein can help applications run without interruption when there are software faults or glitches on a remote system with which they interact.

Abstract: Techniques are provided to allow more sophisticated operations to be performed remotely by machines that are not fully functional. Operations that can be performed reliably by a machine that has experienced a hardware and/or software error are referred to herein as Remote Direct Memory Operations or “RDMOs”. Unlike RDMAs, which typically involve trivially simple operations such as the retrieval of a single value from the memory of a remote machine, RDMOs may be arbitrarily complex. The techniques described herein can help applications run without interruption when there are software faults or glitches on a remote system with which they interact.

Abstract: A technique involves: in response to receiving a request to write data to a storage device, acquiring metadata of a redundant array of independent disks (RAID) extent that is associated with the request to write data, the RAID extent being built based on disk slices comprised in a plurality of disks of the storage device; determining, based on the metadata, a disk slice of data write-enabled RAID extent to write the data; and copying an identification and a degradation number into a metadata page associated with a mapper for data recovery, the identification and degradation number being comprised in the metadata and associated with the data write-enabled RAID extent, the mapper being used to map a physical space and a virtual logical space, and the degradation number indicating the number of times that the disk slice comprised in the RAID extent changes from being normal to being degraded.

Abstract: A method for maintaining high-availability of file system instances is described. The method includes maintaining replica file system instances such as a first replica file system instance on a first computing node and a second replica file system instance on a second computing node. Further, a third computing node is instructed to create a sparse replica file system instance on the third computing node in response to detection of a failure condition associated with the second computing node. Moreover, a data update request is directed to the first replica file system instance and the sparse replica file system.

Abstract: Techniques are provided to allow more sophisticated operations to be performed remotely by machines that are not fully functional. Operations that can be performed reliably by a machine that has experienced a hardware and/or software error are referred to herein as Remote Direct Memory Operations or “RDMOs”. Unlike RDMAs, which typically involve trivially simple operations such as the retrieval of a single value from the memory of a remote machine, RDMOs may be arbitrarily complex. The techniques described herein can help applications run without interruption when there are software faults or glitches on a remote system with which they interact.

Abstract: The present disclosure describes example service takeover methods, storage devices, and service takeover apparatuses. In one example method, when a communication fault occurs between two storage devices in a storage system, the two storage devices respectively obtain running statuses of the two storage devices. A running status can reflect current usage of one or more system resources of a particular storage device. Then, a delay duration is determined according to the running statuses, where the delay duration is a duration for which the storage device waits before sending an arbitration request to a quorum server. The two storage devices respectively send, after the delay duration, arbitration requests to the quorum server to request to take over a service. The quorum server then can select a storage device in a relatively better running status to take over a host service.

Abstract: Techniques are provided to allow more sophisticated operations to be performed remotely by machines that are not fully functional. Operations that can be performed reliably by a machine that has experienced a hardware and/or software error are referred to herein as Remote Direct Memory Operations or “RDMOs”. Unlike RDMAs, which typically involve trivially simple operations such as the retrieval of a single value from the memory of a remote machine, RDMOs may be arbitrarily complex. The techniques described herein can help applications run without interruption when there are software faults or glitches on a remote system with which they interact.

Abstract: The invention introduces a non-transitory computer program product for handling a sudden power off recovery (SPOR) to include program code to: drive a flash access interface to read pages of a current block in sequence after a power restart subsequent to a sudden power off (SPO); mark the last correct page of the current block according to page read statuses for the current block; configure n1 pages after the next page of the last correct page of the current block as dummy pages; and drive the flash access interface to store data of the last correct page and its previous n2-1 pages of the current block in empty pages after the last dummy page of the current block, wherein any of n1 and n2 is a positive integer.

Abstract: Example implementations described herein are directed to backup and restore of a public cloud and data center for disaster recovery. In a backup process of the disaster recovery, the VM root device information (a public cloud) and storage system volume information (a data center) in a main site are transferred to the disaster recovery tool. In a restoration process, the DR Tool specifies the storage system volume for backup to attach the VM in a backup site with the above information.

Abstract: A data protection system configured to replicate data may generate rescue packages that allow the system to recover when communication between a splitter or source of the production data being replicated and an appliance that stores the replicated data is disrupted. The rescue package is stored on a datastore and is then retrieved by the data protection system or another splitter. After processing the rescue package, which may contain IOs that the data protection is unaware of due to the communication disruption, replication may resume normally.

Abstract: The technology disclosed herein pertains to a system and method for managing write failures in a disc drive. Implementations disclosed herein provide a method including monitoring write fault events per sector for a storage device, in response to a write fault event, updating a write fault repeat count table, wherein the repeat count table tracks a number of write fault repeat counts per sector, comparing a write fault repeat count for a sector to a predetermined threshold write fault repeat count, and in response to determining that the write fault repeat count for a sector is above the predetermined threshold write fault repeat count, performing a write-reassign operation.

Abstract: A failure in a main site is recovered by operating in the same operational environment as a sub site. A remote copy system includes: a first storage system providing a main site; and a second storage system providing a sub site. A storage controller stores data and an operation processed in the main site as a main site journal, sends the main site journal to the sub site for sequential processing, stores data and an operation processed in the sub site as a sub site journal after a failover to the sub site is performed, and cancels an unreflected operation that is not processed in the sub site after being stored in the main site journal prior to the failover in the main site and sequentially processes the sub site journal in the main site, when a failback to the main site is performed.

Abstract: Embodiments of the present disclosure provide a method, electronic device and computer program product for managing a backup system. The method comprises: determining, based on historical backup information of the backup system in a first time period, at least one temporal feature corresponding to the first time period, the historical backup information indicating a set of numbers of backup jobs executed by the backup system in the first time period; determining, based on the at least one temporal feature, a set of predicted numbers of backup jobs expected to be executed by the backup system in a second time period; and determining a health status of the backup system based on the set of predicted numbers and a set of actual numbers of backup jobs executed actually by the backup system in the second time period. In this way, the health status of the backup system can be determined in time.

Abstract: Failover methods and systems for a storage environment are provided. During a takeover operation to take over storage of a first storage system node by a second storage system node, the second storage system node copies information from a first storage location to a second storage location. The first storage location points to an active file system of the first storage system node, and the second storage location is assigned to the second storage system node for the takeover operation. The second storage system node quarantines storage space likely to be used by the first storage system node for a write operation, while the second storage system node attempts to take over the storage of the first storage system node. The second storage system node utilizes information stored at the second storage location during the takeover operation to give back control of the storage to the first storage system node.

Abstract: Systems and methods are provided for persisting a data structure. One method may comprise, at a front-end node in a computing system: generating a data structure operation record for a data structure operation directed to a data structure persisted in a non-volatile memory (NVM) in a back-end node of the computing system, appending the data structure operation record in an operation log, generating a transaction record for a transaction that includes a plurality of memory operations that collectively accomplishing the data structure operation, appending the transaction record in a transaction log, flushing the transaction log to the back-end node after flushing the operation log; and at the back-end node of the computing system: persisting received operation log and received transaction log in the NVM, and accomplishing the data structure operation by performing the plurality of the memory operation records with the data structure operation record as a commit signal.

Abstract: A system for extending the utility of blockchain environments when such environments become too large or complex, is disclosed. The system systematically creates a second generation, or child blockchain that can retain machine-readable links to the parent blockchain which, in turn, can be archived and referenced, when necessary, for historical reference. Accordingly, the system serves to reduce the size of the working blockchain thereby making it easier to store the blockchain, and further serves to increase the speed of queries to interrogate the current state of the blockchain. By reducing the size of the working blockchain, the present invention seeks to extend the utility of large blockchains by segregating and archiving historical or older transactions recorded in the blockchain. The system and process further includes methodologies to create links between the current blockchain and the archived sections of the blockchain to ensure the integrity of the full historical ledger.

Abstract: An illustrative embodiment disclosed herein is an apparatus including a processor having programmed instructions to map a plurality of objects to a region and map the region to a plurality of vdisks. The plurality of objects are stored in the plurality of vdisks. The processor has programmed instructions to, responsive to mapping the plurality of objects to the region, identify a policy associated with the region. The policy specifies a policy action in response to satisfying a predetermined condition. The processor has programmed instructions to, responsive to satisfying the predetermined condition, access the plurality of vdisks and perform the policy action on the plurality of objects.

Abstract: The present invention provides a control method of a server, wherein the control method includes the steps of: periodically controlling a first register and a second register of a first node to have a first value and a second value, respectively; periodically controlling a third register and a fourth register of a second node to have a third value and a fourth value, respectively; controlling the first register and the fourth register to synchronize with each other, wherein the first value is different from the fourth value; controlling the second register and the third register to synchronize with each other, wherein the second value is different from the third value; and periodically checking if the third register has the third value and the fourth register has the fourth value to determine if the first node fails to work.

Abstract: In a server (111), an updater (201) updates a file by an editing process that includes an adding process that adds a record to the end of a file. A collector (202) reads, in order of location in the file, a record included in the file, causes a collection device of a collection system to associate and collect the record and a position of the record in the file, and non-transitorily stores the position as an offset. An estimator (203) estimates whether header records located between the beginning of the file and the recorded offset are updated. When it is estimated that any of the header records are updated, a starter (204) causes the collector (202) to start reading the record from the beginning of the file. When it is estimated that none of the header records have been updated, the starter 204 causes the collector (202 to start reading the record from the recorded offset.

Abstract: A storage entity of the data storage system may be visible to the host over a first path and a second path. The first path may operate in accordance with a first protocol and the second path may operate in accordance with a second different protocol. The storage entity may have a first protocol level personality and identity when presented to the host over the first path and a second protocol level personality and identity when presented to the host over the second path. A first native identifier associated of the storage entity on the first path and a second native identifier of the storage entity on the second path may be used to determine that the same storage entity is visible over the first and second paths even though the storage entity may have different protocol level identifiers on the first and second paths that operate using different protocols.

Abstract: The rebuilding process comprises the steps of detecting a failure on a first server that stores a first data and processes input/output requests from an application, redirecting incoming input/output requests from the application to a second server storing a second data. The second data being mirrored from the first data. The process further comprises forming, by the first server, a data loss information that identifies the lost data units in the first data. The process further comprises rebuilding, by the first server, the lost data units in the first data, by using the data that is retrieved from the second data and based on the data loss information by the second server. The process further comprises syncing up data units, other than the lost data units in the first data, with corresponding data in the second data in the second server during the rebuilding process.

Abstract: A system includes a host processor, a volatile memory device coupled to the host processor, and at least a first persistent memory device coupled to the host processor. The host processor is configured to execute one or more applications. The volatile memory device and the first persistent memory device are in respective distinct fault domains of the system, and at least one of a plurality of data objects generated by a given one of the applications is accessible from multiple distinct storage locations in respective ones of the distinct fault domains. For example, the host processor and the volatile memory device may be in a first one of the distinct fault domains and the first persistent memory device may be in a second one of the distinct fault domains. The data object remains accessible in one of the fault domains responsive to a failure in another of the fault domains.

Abstract: Systems, methods, and computer readable storage mediums for generating an alert on a failure of a storage subsystem to phone home to the cloud in a replication environment. A dataset is replicated from a first storage subsystem to a second storage subsystem. The first and second storage subsystems also phone home log data to the cloud on a periodic basis. In response to detecting a failure of the first storage subsystem to phone home, the cloud generates and sends an alert to the second storage subsystem. In response to receiving this alert, the second storage subsystem starts disaster recovery operations for the dataset.

Abstract: Example implementations relate to managing ownership transfer of a file system instance in a virtualized distributed storage system. The virtualized distributed storage system includes a first node having a first virtual controller that acts as an owner of a file system instance in a distributed storage, and a second node having a second virtual controller coupled to the first node over a network. A failure condition associated with a first node is detected. Further, in response to detection of the failure condition, an ownership of the file system instance may be transferred from the first virtual controller to the second virtual controller no later than an IP address switchover of the first virtual controller.

Abstract: A Data Storage Device (DSD) includes a plurality of storage areas for storing data. A command is received from a host to write data or read data in the DSD, and a storage area is identified for writing the data or reading the data for the command. An internal command is sent to the identified storage area to write the data or read the data for the command using an Ethernet protocol. In another aspect, a command is received from a controller of a DSD to copy data from one storage area to a different storage area of the DSD. The different storage area is identified using an address included in the command received from the controller, and the data for the command is read from the storage area. The data is sent to the different storage area using the address included in the command received from the controller.

Abstract: One or more techniques and/or systems are provided for cluster configuration information replication, managing cluster-wide service agents, and/or for cluster-wide outage detection. In an example of cluster configuration information replication, a replication workflow corresponding to a storage operation implemented for a storage object (e.g., renaming of a volume) of a first cluster may be transferred to a second storage cluster for selectively implementation. In an example of managing cluster-wide service agents, cluster-wide service agents are deployed to nodes of a cluster storage environment, where a master agent actively processes cluster service calls and standby agents passively wait for reassignment as a failover master in the event the master agent fails. In an example of cluster-wide outage detection, a cluster-wide outage may be determined for a cluster storage environment based upon a number of inaccessible nodes satisfying a cluster outage detection metric.

Abstract: In a decentralized system of nodes configured to provide data protection functionality, wherein at least a subset of the nodes store and share data using content-addresses managed via a distributed hash table in each of the subset of nodes, a given one of the subset of nodes locally stores: a data protection policy to be implemented by the given node; data protected on the given node; and metadata comprising information indicating placement of a given data set on one or more other ones of the subset of nodes. The given node accesses the locally stored metadata to manage protection of the given data set on the one or more other ones of the subset of nodes.

Abstract: Automatically managing an entire life-cycle of a practice failover. The system uses a virtualization management system that hosts one or more business applications which has capability and authority to manage both the application hosting infrastructure as well as the storage infrastructure that is used by the applications in a disaster recovery configuration. The set of applications is replicated along with an application platform together with the applications.

Abstract: A method, article of manufacture, and apparatus for analyzing a distributed file system is discussed. A metadata operation is captured in an audit log, wherein the metadata operation is on an object stored in the distributed file system. An event is pushed to a distributed commit log and a real-time analytics engine in response to capturing the metadata operation. The event is persistently stored in the distributed commit log.

Abstract: A method for execution by a dispersed storage and task (DST) execution unit identifying a failing memory device based on memory device diagnostic data. A cloning task is executed by designating memory of a replacement memory device to store encoded slices stored in the failing memory device, where the cloning task is executed over a cloning duration time period. A write request is received via a network at a receiving time during the cloning duration time period that includes a new encoded slice, and the new encoded slice is assigned to a temporary memory device for storage based on an identifier of the new encoded. The new encoded slice is transferred from the temporary memory device to the replacement memory device in response to an elapsing of the cloning duration time period corresponding to completion of the execution of the cloning task.

Abstract: A tool for synthetic order recovery is provided.

Abstract: Embodiments are described for distributed and scalable client-based storage management and microservices-based storage management, which can operate in combination. Embodiments distribute responsibilities and client-specific information needed for storage management jobs away from a central storage manager and its management database. New features and components minimize communications to/from the storage manager and ensure the integrity and synchronization of data being distributed. The management database at the storage manager retains its role as repository of information for the data storage management system as a whole, yet without being a bottleneck to storage operations. Improvements are implemented within the storage manager, through new functionality added to clients, and further through a new micro-server component interposed between storage manager and clients.

Abstract: Embodiments are described for distributed and scalable client-based storage management and microservices-based storage management, which can operate in combination. Embodiments distribute responsibilities and client-specific information needed for storage management jobs away from a central storage manager and its management database. New features and components minimize communications to/from the storage manager and ensure the integrity and synchronization of data being distributed. The management database at the storage manager retains its role as repository of information for the data storage management system as a whole, yet without being a bottleneck to storage operations. Improvements are implemented within the storage manager, through new functionality added to clients, and further through a new micro-server component interposed between storage manager and clients.

Abstract: A memory system for a data processing apparatus includes a fault management unit, a memory controller (such as a memory management unit or memory node controller), and one or more storage devices accessible via the memory controller and configured for storing critical data. The fault management unit detects and corrects a fault in the stored critical data, a storage device or the memory controller. A data fault may be corrected using a copy of the data, or an error correction code, for example. A level of failure protection for the critical data, such as a number of copies, an error correction code or a storage location in the one or more storage devices, is determined dependent upon a failure characteristic of the device. A failure characteristic, such as an error rate, may be monitored and updated dynamically.

Abstract: Provided is a method, system, and computer program product for managing requests received by a storage system. The method may include detecting, by one or more processors, a failure in a first storage system in response to a request to access data in the first storage system. The first storage system may include a primary storage for storing the data. A second storage system may be activated in response to the detected failure. The second storage system may include a first storage and a second storage. The first storage may include data synchronized with the primary storage of the first storage system. The second storage may be used to store data that corresponds to the request. The request may be managed using the second storage system.

Abstract: A method and system for proactive data migration across tiered storage that uses machine learning is shown. The method includes receiving first input-output (IO) event metadata describing a first IO event, and analyzing the first IO event metadata using an optimized learning model (OLM), to obtain a first learning model output. The first learning model output is interpreted to generate a first data migration request, and the first data is proactively migrated from a first storage tier to a second storage tier based on the first data migration request.

Abstract: Providing seamless mobility of stateful pods in a container management system, by: receiving an indication that a pod needs to be moved from a first site to a replica site, identifying, through a moving target defense (MTD) process, all persistent volumes attached to the pod; determining if an RPO/RTO objective for the movement is below a threshold value, draining all local I/O operations to a container having the persistent volumes attached; killing containers of the pod using the persistent volumes after the draining, waiting for data to be flushed to the replica site, initiating a failover of a first storage of the first site, and restarting a container to run on the replica site attached to replica storage. In this process, a resource management system (RMS) is used to provide an address of a secure golden copy of the container as the address of the replica site.