Cascading payload replication to target compute nodes is disclosed. Cascading payload replication can be accomplished using a two-stage operation for a replication operation. In the first stage, a plan is generated and distributed for the replication operation. The plan includes an assignment of compute nodes to tree nodes in a tree hierarchy. In the second phase, the payload is distributed according to the plan. The plan is different for at least two replication operations. Thus, the cascading payload replication is adaptable to changing target compute nodes and provides for load balancing.

Secure loading and execution of user-defined content on an embedded controller associated with a remote terminal unit (RTU) includes providing a factory default image for the RTU having a default secured read only filesystem and providing a developer image for extending the RTU functionality, having a read/write filesystem equivalent working in conjunction with the read only filesystem.

A method of performing synchronous replication from a primary storage system apparatus (PSSA) to a secondary storage system apparatus (SSSA) is provided. The method includes (a) in response to write requests received by the PSSA, (i) calculating metadata changes by the PSSA for accommodating the write requests, (ii) generating, by the PSSA, metadata journal log entries that describe the metadata changes, and (iii) mirroring the metadata journal log entries from the PSSA to the SSSA; (b) regenerating the metadata changes by the SSSA based on the metadata journal log entries mirrored from the PSSA to the SSSA; and (c) writing the regenerated metadata changes to persistent storage of the SSSA. A method performed by the SSSA is also provided. An apparatus, system, and computer program product for performing similar methods are also provided.

A snapshot storage proxy receives a request from an object storage interface component to access a snapshot volume, wherein the request is formatted to interact with object storage data, and wherein the snapshot volume is stored as non-object storage data; translates the request from the object storage interface into a snapshot volume request, wherein the snapshot volume request is formatted to interact with non-object storage data; and accesses the snapshot volume in view of the translated snapshot volume request.

The present disclosure relates to a digital asset synchronization system that provides improved digital asset management and synchronization of a digital asset stored either within a component database or a packaged file. For example, the digital asset synchronization system enables a set of components that makes up a digital asset to appear as a singular packaged file, while also maintaining the benefits of having the digital asset made up of the components. In this manner, the digital asset synchronization system provides a bridge between a digital asset stored in a packaged file format and conventional file formats. In addition, the digital asset synchronization system also provides digital asset management and improved synchronization between a client device and a cloud storage system.

System and methods are described for automated recovery from errors occurring during replication of a database. The method includes getting text from one or more log files generated during database replication processing in a cloud computing environment, transforming the text into a structured language form represented by vectors, and identifying patterns in the vectors. The method further includes classifying one or more errors based on the identified patterns using supervised learning as either a recoverable error or an unrecoverable error, analyzing the one or more errors to determine one or more recovery jobs associated with database replication processing in the cloud computing environment for each of the recoverable errors, and invoking the one or more recovery jobs.

A system and method are presented that utilize separate append-only arrays to track metadata and real data for a file. All modifications to the file result in metadata records being appended to the end of the metadata array. Write modification commands cause real data to be appended to the file data array. The location of real data on the file data array is identified by a record in the metadata array. Modification commands can be grouped into sets, which complete as a set. Modification sets can rely upon the completeness of prior sets. Read-like commands cause the creation of a virtual array based upon the records of the metadata array. The created virtual array has the same size as the actual file but does not contain the real data for the file. Rather, the virtual file array maps to the actual data stored in the file data array.

In an embodiment, a computer stores source files and source clone files in a source filesystem. The source clone files are shallow copies of the source files, which initially share the same data blocks as the source files. A source file or a source clone file may eventually be modified, where some of the shared blocks are replaced by modified blocks. In a first phase, all data blocks of all source files that are not clones are replicated to a standby filesystem. A second phase compares each clone file on the source filesystem with its base file to detect a set of differed blocks. The second phase copies the differed blocks into the standby filesystem and, in the standby filesystem, applies the differed blocks to a corresponding clone file. Efficiency of keeping the standby filesystem synchronized with the source filesystem is improved by transferring, from the source filesystem to the standby filesystem, only one copy of only data blocks that are modified

The present technology pertains to a organization directory hosted by a synchronized content management system. The corporate directory can provide access to user accounts for all members of the organization to all content items in the organization directory on the respective file systems of the members' client devices. Members can reach any content item at the same path as other members relative to the organization directory root on their respective client device. In some embodiments novel access permissions are granted to maintain path consistency.

A file server manager disclosed herein accesses information regarding a selected share of a source distributed file server for replication, where the selected share stores at least a portion of a namespace of storage items and is hosted by a first file server virtual machine of the source distributed file server. The file server manager accesses a mapping between virtual machines of the source distributed file server and virtual machines of the destination distributed file server and replicates the selected share to a second file server virtual machine of the destination distributed file server based on the mapping. The file server manager directs a request to read a first storage item to the destination distributed file server and directs a request to write to a second storage item to the source distributed file server while the destination distributed file server services the request to read the first storage item.