Abstract: A system can determine that a node a storage cluster has failed, wherein respective data protection levels are maintained for respective files. The system can traverse the respective files, comprising, in response to determining that a data protection level for a file is degraded and that the file is a priority file, adding an identifier of the file to a priority table for restoration of data protection, or, in response to determining that the data protection level for the file of the respective files is degraded and that the file is not the priority file, adding the identifier of the file to a non-priority table for the restoration of data protection. The system can, after traversing the files, restore respective first data protection levels of respective first files represented by the priority table, and then restore respective second data protection levels of respective second files represented by the non-priority table.

Abstract: Example methods and systems for accessing data in a log-structured file system having a plurality of snapshots of storage objects backed by a first-level copy-on-write (COW) B+ tree data structure and a plurality of second-level B+ tree data structures have been disclosed. One example method includes obtaining a first first-level mapping associated with a first snapshot from the plurality of snapshots based on a first logical block address, wherein each of the plurality of snapshots corresponds to each of the plurality of second-level B+ tree data structures, identifying a first second-level B+ tree data structure corresponding to one of the plurality of snapshots based on the first first-level mapping, obtaining a first second-level mapping based on the first logical block address in the first second-level B+ tree data structure, obtaining a first physical block address based on the first second-level mapping, and accessing data at the first physical block address.

Abstract: One example method includes accessing a point-in-time copy including retention locked backups that were stored on a backup storage server at a time the point-in-time copy was generated. The method further includes accessing a current namespace including retention locked backups that are currently stored on the backup storage server. Each retention locked backup includes data backup files. The method also includes determining a first set of retention locked backups that are included in the point-in-time copy, but are not included in the current namespace. The method finally includes copying the first set of retention locked backups from the point-in-time copy into the current namespace without removing any of the retention locked backups already in the current namespace.

Abstract: Nodal work assignments efficiently distribute server work items, such as storing redundant copies of electronic data. A cloud computing network establishes a policy that governs how and where the redundant copies are stored cloud computing nodes (such as by region, zone, and cluster targets). The cloud computing network repeatedly or continuously re-evaluates the work assignments based on replication assignment skews and/or leadership penalties. The nodal work assignments thus minimize hardware and software operations, network traffic, and electrical energy consumption.

Abstract: A self-healing method of recovering files using a cyber recovery vault for deduplication filesystems. Data to be backed up from a production system to a backup system in a datacenter is also copied to a cyber security vault coupled to the data center through an air gapped connection. A copy process makes a point-in-time (PIT) copy of the portion of data to a namespace in the vault, and retention locks the copied portion in the vault. An automated process detects a missing segment error, such as due to a bad index lookup in the data to be backed up. The self-healing process provides the missing segment from the PIT copy in the cyber security vault. For any missing fingerprints the process adds the data in new containers and the references in the index, providing an indirection that allows for just writing a new container with the missing L0 references and updating the index.

Abstract: Distributed database systems including compute nodes and page servers are described herein that enable separating logical and physical storage of database files in a distributed database system. A distributed database system includes a page server and a compute node, and is configured to store a logical database file that includes data and is associated with a file identifier. Each page server is configurable to store slices (i.e., subportions) of the logical database file. The compute node is coupled to the plurality of page servers and configured to store the logical database file responsive to a received command. In an aspect, such storage may comprise slicing the data comprising the logical database file into a set of slices with each being associated with a respective page server, maintaining an endpoint mapping for each slice of the first set of slices, and transmitting each slice to the associated for storage thereby.

Abstract: Methods and systems for providing computer implemented services using pods are disclosed. To provide the computer implemented services, instances of the pods may be deployed to data processing systems. When a new instance of a pod is created, a volume for the pod may be established. To select where to create instances of pods, locations where data access conflicts are less likely to arise may be selected. These locations may be identified based on the locations of pods and data access patterns for the pods.

Abstract: A system can include a memory device and a processing device operatively coupled with the memory device, to perform operations including receiving, from a first host application, a data object to store on the memory device and associating an object identifier with physical address ranges. The operations can further include associating the object identifier with a snapshot identifier to define a snapshot and mapping the physical address ranges to corresponding virtual address ranges of a second host application. The operations can also include responsive to receiving, from the first host application, a request to write to the data object recording, in a change log, an entry reflecting a change made to the data object, and responsive to receiving, from the first host application, a request to read a part of the data object, retrieving the part from the entry of the change log.

Abstract: Systems and methods are provided for data migration. The system may comprise one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the system to migrate at least one first table of a first database schema to at least one second table of a second database schema, determine a query for modifying the first table during the migration, modify the second table based at least in part on the query, and update a mutation table to describe the modification, wherein the mutation table at least describes the modification.

Abstract: Object-based transportation between tenants may provide advantages over persistence layer-based transportation on a cloud platform in situations where persistence layer storage space is limited. Object based transportation involves obtaining a selection from the target tenant application of a set of objects from the plurality of objects and determining objects identifiers for each of the selected set of objects. For each object in the selected set of objects, a request is sent to a source tenant. The requests includes the corresponding object identifier for that object. Corresponding object data is received from the source tenant. At least a portion of the corresponding object data is stored in a target tenant database. An existing object may be updated or a new object may be created.

Abstract: A method for managing data include obtaining, by a universal connector, a backup request for a set of files, in response to the backup request: performing a batching of file read requests for data associated with the set of files to obtain a set of file read batches, sending the set of file read batches to a network attached storage (NAS) server, obtaining a response for each of the set of file read batches from the NAS server, wherein the response for each of the set of file read batches comprise a portion of the data, wherein at least two responses for the set of file read batches are obtained in parallel, writing the portion of the data to a backup container in parallel with the obtaining, and initiating a backup of the set of files using the backup container after the writing is completed.

Abstract: Writers on a host and associated with a copy service are identified. The identification includes names of the writers and writer types as being system or application writers. For each writer identified as a system writer, a size of the system writer is calculated and a check is made as to whether a volume associated with the system writer includes system data. When the volume include system data, the volume is marked as a critical volume and a size of the critical volume is obtained. A tally is maintained summing the sizes of the system writer and critical volume.

Abstract: Selective migration of a database in which one or more computing devices establish a creation specification for a snapshot of a subset of a source database of a source database management system (DBMS). The device(s) receive instruction to create the snapshot in accordance with the creation specification. The device(s) retrieve, in response to receiving the instruction to create, record(s) from the source database in accordance with the creation specification. The device communicates, via broadcast, the retrieved records to one or more creation listeners; and serializes, by each listener and in accordance with the creation specification, the broadcast records into the snapshot comprising the fragments and the parts.

Abstract: Embodiments of the invention relate to generating backups of assets. More specifically, in one or more embodiments of the invention, multiple copies of a backup are stored in separate locations. The copies may then be used to perform a restoration when one of the copies is corrupted. If all copies are corrupted the invention allows for partial restoration of those portions of the copies that are not corrupted. By using copies, embodiments of the invention allow the backups to be more resilient to attacks and system failures.

Abstract: A distributed table storage processing method, device and system, a master server to which a to-be-split slice belongs generates a splitting log of the to-be-split slice and a serial number of the splitting log after receiving a first splitting instruction for the to-be-split slice sent by a control device; sends the splitting log and serial number of the splitting log to a slave server to which the to-be-split slice belongs, and the slave server sends a first acknowledgment message to the master server after storing the splitting log and the serial number; performs splitting storage on the to-be-split slice according to the splitting log to obtain a plurality of new slices when the number of the received first acknowledgment messages is not less than a first threshold; sends a second splitting instruction to each slave server, and the slave server performs splitting storage to obtain a plurality of new slices.

Abstract: An illustrative storage management appliance is interposed between client computing devices and one or more cloud storage resources. The appliance uses cloud storage resources in conjunction with a network attached storage device configured within the appliance to provide to the client computing devices seemingly unlimited network attached storage on respective network shares. The storage management appliance monitors data objects on the network shares and when a data object meets one or more criteria for archiving, the storage management appliance archives the data object to a cloud storage resource and replaces it with a stub and preview image on the network share. When access to the stub and/or preview image is detected, the storage management appliance restores the data object from the cloud storage resource. The criteria for archiving flexibly allow individual data objects to be archived to cloud storage without archiving frequently-accessed “neighboring” data objects on the same network share.

Abstract: A database system stores a hypertable representing a database table partitioned into chunks along a set of one or more dimension attributes. A subset of chunks of the hypertable is stored in a primary database storage and another subset of chunks stored in cloud storage. The database system transmits chunks from the primary database storage to a cloud storage either individually or as larger batches of chunks. Each chunk in the cloud storage is stored using a different database storage format compared to the database storage format used in the primary database storage. The database system receives a database query and generates a query execution plan including operators for accessing a set of chunks stored in the primary database storage and operators for accessing a set of chunks stored in the cloud storage. Results obtained by processing the different sets of chunks are combined.

Abstract: A map-reduce compatible distributed file system that consists of successive component layers that each provide the basis on which the next layer is built provides transactional read-write-update semantics with file chunk replication and huge file-create rates. Containers provide the fundamental basis for data replication, relocation, and transactional updates. A container location database allows containers to be found among all file servers, as well as defining precedence among replicas of containers to organize transactional updates of container contents. Volumes facilitate control of data placement, creation of snapshots and mirrors, and retention of a variety of control and policy information. Also addressed is the use of distributed transactions in a map-reduce system; the use of local and distributed snapshots; replication, including techniques for reconciling the divergence of replicated data after a crash; and mirroring.

Abstract: A target host is booted into a preinstallation environment. A request to register as a recovery agent is issued from a REST API of the target host to a backup management server. A TLS certificate to establish a secure channel is received from the backup management server. A request identifying a backup copy to be stored on the target host is issued from the REST API of the target host and over the secure channel to the backup management server. Credentials required to access a backup storage at which the backup copy is stored is received. Using the credentials, the backup copy is retrieved from the backup storage.

Abstract: A method and system to provide artificial intelligence services to user interacting applications which includes receiving first unfulfilled service request from a user interaction application executing on a user device and generating, from the unfulfilled service request, an unfulfilled artificial intelligence service request and an unfulfilled non-artificial intelligence service request. The unfulfilled artificial intelligence service request is transmitted to an artificial intelligence service module to fulfill the unfulfilled artificial intelligence service request, which generates a fulfilled artificial intelligence service request. The unfulfilled non-artificial intelligence service request is transmitted to a back-end server to fulfill the unfulfilled non-artificial intelligence service request, which generates a fulfilled non-artificial intelligence service request.

Abstract: A method and system for migrating data and metadata from a first backup system to a second backup system via a staging system is disclosed. The system accesses the backup data from the first backup system and restores it, along with the associated metadata, to a staging system. A metadata file is created at the staging system which comprises of the metadata that is to be migrated to the second backup system. The system then migrates the data from the staging system to the second backup system. The metadata is also migrated to the second backup system in a format such that it can be indexed. As a result, the migrated data can be browsed and searched based on one or more search criteria based on the associated metadata. Other details are provided herein.

Abstract: A virtual machine disk image file backup is selected among a plurality of virtual machine disk image file backups stored on a backup storage based on a backup update policy. A version of the selected virtual machine disk image file backup is mounted. Based on the backup update policy, an update to the mounted version of the selected virtual machine disk image file backup is applied without restoring the selected virtual machine disk image file backup. The updated version of the selected virtual machine disk image file backup is stored on the backup storage.

Abstract: An identification of a new primary snapshot created for a primary storage system is received. A change tracking time window that is at least a portion of a period between a first capture time associated with a previous primary snapshot and a second capture time associated with the new primary snapshot is determined. Entries of a storage log of the primary storage system occurring within the change tracking time window are analyzed to coalesce changes identified in the entries of the storage log occurring within the change tracking time window into a change tracking result set. The change tracking result set is used to identify at least a portion of data changes between the previous primary snapshot and the new primary snapshot to capture in a new backup snapshot stored at a secondary storage system.

Abstract: A snapshot is taken of at least a portion of a file system having a set of files to retain over a retention duration. The snapshot is taken at a level of the file system or a directory of the file system. A retention lock is applied to the snapshot to block, over the retention duration, operations involving deletion of the snapshot. The retention lock is not applied to the set of files.

Abstract: Systems and methods for durable storage of storage volume “snapshots” are provided. Snapshots are stored as collections of snapshot data objects. To improve the durability of snapshot storage, physical deletion of snapshot data objects may be delayed for a period of time after the snapshot data objects are marked for deletion. Lists of the stored snapshot data objects and the snapshot data objects that make up active snapshots may be periodically analyzed. If there are any snapshot data objects that are part of active snapshots and are not present in the list of stored snapshot data objects, the snapshot data objects may be recovered before they are physically deleted.

Abstract: A data storage and retrieval system for a computer memory including a memory slice formed of segments and adapted to contain one or more documents and a checkpoint adapted to persist the memory slice. The checkpoint includes a document vector containing a document pointer corresponding to a document. The document pointer including a segment identifier identifying a logical segment of the memory slice and an offset value defining a relative memory location of the first document within the identified segment. There are checkpoint memory blocks, each storing a copy of a corresponding segment of the memory slice. The segment identifier of the document pointer identifies a checkpoint memory block and the offset value of the document pointer defines a relative location of the document within the checkpoint memory block.

Abstract: A cloud-native global file system, in which one or more filers are associated with a volume of a versioned files system in a private, public or hybrid cloud object store, is augmented to include a rapid ransomware recovery service. Upon detecting a ransomware attack associated with one or more files or directories of the volume, read and write access to the volume is restricted. A recovery filer is then activated or designated in the cloud. A restore operation is then initiated at the recovery filter. Following completion of the restore operation, a new clean (healthy) snapshot of the volume is then created using the recovery filer For any filer other than the recovery filer, a determination is made whether the filer has completed a merge operation with respect to the new clean snapshot. If so, read and write access to the volume is re-enabled from that filer.

Abstract: Use of multivariate data backup retention policies, including: generating a snapshot of a dataset; identifying respective subsets of the dataset that correspond to respective retention policies of a plurality of retention policies; and generating tracking information indicating the respective subsets of the dataset corresponding to the respective retention policies of the plurality of retention policies.

Abstract: An illustrative media agent (MA) in a data storage management system instructs a NAS file server (filer) to restore an MA-created synthesized-copy instead of larger filer-created backup copies. The synthesized-copy is designed only for the particular files to be restored and mimics, and is typically much smaller than, a filer-created backup copy. The synthesized-copy is fed to the filer on restore as a “restore data image.” When receiving a restore request for certain backed-up data files, the MA synthesizes the synthesized-copy on the fly. The MA generates a header mimicking a filer-created backup header; extracts files from filer-created backup copies arranging them within the synthesized-copy as if in filer-created backups; and instructs filer to perform a full-volume restore from the synthesized-copy. The MA serves the synthesized-copy piecemeal as available, rather than waiting to synthesize the entire synthesized-copy. The synthesized-copy is not stored at the MA.

Abstract: An apparatus comprises a processing device configured to identify a cloud snapshot lineage that is being managed by first virtualization software running on a first storage system, the cloud snapshot lineage comprising one or more snapshots of at least one storage volume, the cloud snapshot lineage being stored on cloud storage of at least one cloud external to the first storage system. The processing device is also configured to pause management of the cloud snapshot lineage by the first virtualization software running on the first storage system, to obtain, from the first virtualization software running on the first storage system, configuration data for the cloud snapshot lineage, to provide, to second virtualization software running on a second storage system, the configuration data for the cloud snapshot lineage, and to resume management of the cloud snapshot lineage by the second virtualization software running on the second storage system.

Abstract: A changed block tracking (CBT) driver at a production host tracks, in a bitmap, changes made to a source volume of the production host since a last backup. A command is received to perform a differential backup of the source volume. A request is issued to a copy service to take a snapshot of the source volume. The bitmap is embedded into the snapshot. The snapshot is mounted on a backup proxy, different from the production host. The backup proxy retrieves the bitmap from the snapshot and conducts the differential backup of the source volume to secondary storage, thereby backing up the changes made to the source volume since the last backup according to the bitmap.

Abstract: The nodes of a squad of nodes include a coordinating node and a set of worker nodes for sharing computational resources to perform resource intensive tasks. To coordinate the sharing of resources, the coordinating node requests a report of resources status and current utilization from each worker node. The report of resource status includes at least a battery level of a corresponding worker node. The coordinating node receives a work request from a requesting worker node, and identifies a subset of worker nodes for executing the work request based on at least the battery level of each worker node and the current utilization of each worker node. The coordinating node then sends the list of identified worker nodes to the requesting worker node to allow the requesting worker node to divide the tasks for completing the work request among the worker nodes included in the list of identified worker nodes.

Abstract: Techniques are provided for an object file system for an object store. Data, maintained by a computing device, is stored into slots of an object. The data within the slots of the object is represented as a data structure comprising a plurality of nodes comprising cloud block numbers used to identify the object and particular slots of the object. A mapping metafile is maintained to map block numbers used to store the data by the computing device to cloud block numbers of nodes representing portion of the data stored within slots of the object. The object is stored into the object store, and the mapping metafile and the data structure are used to provide access through the object file system to portions of data within the object.

Abstract: In some embodiments, a behavior classifier comprises a set of neural networks trained to determine whether a monitored software entity is malicious according to a sequence of computing events caused by the execution of the respective entity. When the behavior classifier indicates that the entity is malicious, some embodiments execute a memory classifier comprising another set of neural networks trained to determine whether the monitored entity is malicious according to a memory snapshot of the monitored entity. Applying the classifiers in sequence may substantially reduce the false positive detection rate, while reducing computational costs.

Abstract: A storage system establishes a staging region, for temporary writing of arriving data, and a stable region, for transfer of data from the staging region, in storage memory. The storage system establishes resiliency groups, each with a characteristic level of redundancy that is settable on an individual basis. The storage system performs data accesses of data stripes in accordance with the staging region, the stable region, a first resiliency group and a second resiliency group.

Abstract: Embodiments described herein facilitate enhancement of data model acceleration, including generating data model summaries and performing searches in an accelerated manner. In one implementation, a set of events are indexed, each of the events having a corresponding index time representing a time at which the event was indexed in an indexer. Index time parameters including an index earliest time indicating a first index time at which to begin generating a data model summary and an index latest time indicating a second index time at which to complete generating the data model summary are obtained. Thereafter, a data model summary is generated. Such a data model summary summarizes events having corresponding index times between the index earliest time and the index latest time. The data model summary is provided to a remote data store that is separate from the indexer at which at least a portion of the events were indexed.

Abstract: A method for managing a read statement of a transaction, the method may include: (a) receiving the read statement, wherein the read statement is for receiving a data unit that is stored in a relational database; (b) finding one or more candidate versions of the data unit; wherein the finding may include: (i) accessing a database segment (DS) version metadata of one or more DS versions of one or more DSs that are related to the data unit and are stored in the relational database; (ii) performing a timestamp based determination that may include checking whether to ignore a database segment version when the database segment version metadata identifies the database segment version by a database segment commit timestamp; and (iii) performing a transaction metadata based determination of whether to ignore the database segment version when the database segment version metadata identifies the database segment version by a transaction identifier; and (c) responding to the read statement by outputting a version of the

Abstract: A live image of a virtual machine is disclosed. When generating a live image, an image of a virtual machine is generated. A journal is also generated that starts before a start time of the image and ends after the start time of the image. A live image is then generated by synchronizing the start time of the image with the journal. This includes evaluating or analyzing the journal relative to the backup to determine or synchronize the start time relative to the entries in the journal.

Abstract: An apparatus comprises a processing device configured to maintain a snapshot mapping structure for a storage volume. The snapshot mapping structure comprises objects representing the storage volume and snapshots thereof. The objects are organized in a tree structure representing data dependencies between the storage volume and its snapshots. Each of the objects comprises a dynamic bitmap indicating whether that object contains new data for different offset positions relative to its ancestor objects in the tree structure. The processing device is further configured to detect operations directed to a specified one of the storage volume or one of its snapshots, to parse the snapshot mapping structure to identify objects to utilize for processing the operations, and to processing the operations utilizing the dynamic bitmaps of the identified objects.

Abstract: Described is a system (and method) for size-based organization of backup files within an object storage for efficient object re-tiering. The system may perform a specialized process to re-tier objects stored within an object storage by organizing backup files into individual or shared objects based on a backup file size. Accordingly, the system may initiate a re-tiering of objects immediately after performing an incremental backup to improve storage efficiency while at the same time retaining the ability to synthetically perform a full restore.

Abstract: A method and apparatus for elimination of log file synchronization delay at transaction commit time is provided. One or more change records corresponding to a database transaction are generated. One or more buffer entries comprising the one or more change records are entered into a persistent change log buffer. A commit operation is performed by generating a commit change record corresponding to the database transaction and entering a commit buffer entry comprising the commit change record into the persistent change log buffer. The commit operation returns without waiting for the commit change record to be recorded in a change record log file.

Abstract: An approach for staged data backup is provided. The approach comprises downloading data to be backed up, by one or more processors, from at least one of cloud computing servers in a plurality of stages into a local cache, wherein each of the plurality of stages corresponds to a time point when a corresponding downloading operation starts, and a time point corresponding to the last stage of the plurality of stages is the time point when a request to back up the data is received. The approach comprises merging, by one or more processors, downloaded data corresponding to each of the plurality of stages into up-to-date data. The approach further comprises saving, by one or more processors, the merged up-to-date data corresponding to the last stage as a backup dataset.

Abstract: Methods and systems for generating backups are disclosed. To generate a backup, a snapshot may be generated. A snapshot may be a point in time representation of data, in contrast to live data which may be updated over time. To reduce the impact of snapshot generation, a method, system, and device for generating and maintaining a snapshot that utilizes fewer writes is disclosed. To reduce the writes, the snapshots may be generated by preferentially referring to already stored copies of data for the snapshot rather than storing an additional copy of data for the snapshot. The snapshots may be maintained by storing copies of data for the snapshot only when live data diverges from the snapshot.

Abstract: Distributed database systems including compute nodes and page servers are described herein that enable separating logical and physical storage of database files in a distributed database system. A distributed database system includes a page server and a compute node and is configured to store a logical database file that includes data and is associated with a file identifier. Each page server is configurable to store slices (i.e., subportions) of the logical database file. The compute node is coupled to the plurality of page servers and configured to store the logical database file responsive to a received command. In an aspect, such storage may comprise slicing the data comprising the logical database file into a set of slices with each being associated with a respective page server, maintaining an endpoint mapping for each slice of the first set of slices, and transmitting each slice to the associated for storage thereby.

Abstract: A versioned file storage system (VFS) and method for operating and using the same is disclosed. In an aspect, a mechanism is provided wherein a first VFS interface unit coupling the VFS to a local data storage system is replaced with a second VFS interface unit in a coordinated procedure for taking the first unit offline, making a reliable snapshot of its data and cache structure in the VFS, and loading the same data and cache structure into the second VFS interface brought online. The first and second VFS interfaces transfer the necessary data to achieve the switch through respective side-loading daemons running in each interface. Clients in the local data storage system experience minimal interruption of services in the VFS.

Abstract: Aspects of the disclosure describe methods and systems for cross-referencing forensic snapshots over time. In one exemplary aspect, a method may comprise receiving a first snapshot of a computing device at a first time and a second snapshot of the computing device at a second time and applying a pre-defined filter to the first snapshot and the second snapshot, wherein the pre-defined filter includes a list of files that are to be extracted from each snapshot. The method may comprise subsequent to applying the pre-defined filter, identifying differences in the list of files extracted from the first snapshot and the second snapshot. The method may comprise creating a change map for the computing device that comprises the differences in the list of files over a period of time, wherein the period of time comprises the first time and the second time, and outputting the change map in a user interface.

Abstract: Provided are techniques for encrypting a virtual disk of a virtual computing instance (VCI) while the VCI is online and still running using a mirror driver. In certain aspects a mirror driver is a filter running in an I/O stack used for accessing a virtual disk, such that the mirror driver receives I/Os destined to the virtual disk and mirrors those I/Os to the virtual disk and one or more additional virtual disks. The mirror driver begins copying data from an unencrypted source virtual disk to a destination virtual disk, and the data is encrypted as it is stored in the destination virtual disk, while the VCI is still online. During the copying, as new writes are issued to the unencrypted source virtual disk from the VCI, the mirror driver mirrors the writes to both the unencrypted source virtual disk and the destination virtual disk.

Abstract: A data catalog system that is configured to automatically generate synthetic datasets based upon original datasets cataloged by the data catalog system, wherein each synthetic dataset comprises synthetic data that is generated using one or more data generation techniques. The data catalog system may access an original dataset and harvest associated metadata information and generate catalog information for the original dataset. The data catalog system may then generate a synthetic dataset based upon the original dataset and its harvested metadata information. The data catalog system may also generate catalog information for the generated synthetic dataset. The catalog information generated for the original dataset may be updated to refer to the newly generated synthetic dataset and its catalog information. The catalog information generated for the synthetic dataset may include references to the original dataset and its catalog information to inform a user of the original dataset about the synthetic dataset.

Abstract: A controller device manages a plurality of network devices. The controller device includes one or more processing units implemented in circuitry and configured to determine that one or more stateless intents of a deployed graph model including a first set of stateless intents used to manage the plurality of network devices have changed, wherein stateless intents comprise fully declarative descriptions of an intended state of a network including the network devices, state of one or more of the network devices, or state of storage for the network; maintain both the deployed graph model and an undeployed graph model including a second set of stateless intents including the one or more changed stateless intents; compile the changed stateless intents of the undeployed graph model to generate low-level configuration data for the network devices; and configure the network devices using the low-level configuration data.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for managing asynchronous data replication in a multiple availability zone cloud environment. Metadata for files for asynchronous replication at a second availability zone is stored at an in-memory data grid of a first instance of a storage service at a first availability zone at a multiple availability cloud platform that provides storage services. The in-memory data grid includes a queue data structure of metadata records and a map of metadata records. In response to determining that connection from the first availability zone to the second availability zone is available, asynchronous data replication for files identified at the map is executed. A file for replication is identified at the map and provided for replication at a second file storage at the second availability zone through a replication interface of a second instance of the storage service at the second availability zone.