A data set integration system receives a first data set that includes a user identifier and a message type code. The integration system locates an object profile that is associated with the terminal identifier in a data repository. The located object profile includes a tracking identifier and a counter value. The integration system updates the counter value in the object profile in accordance with a value of the message type code. The integration system updates receives a second data set from a communications device. The second data set includes the tracking identifier. The integration system locates the counter value in the object profile that is associated with the tracking identifier, and transmits to the communications device a data payload that includes the updated counter value.

A cloud migration framework may include an enterprise application data store that contains electronic records associated with enterprise applications. Each record may include, for example, an electronic record identifier and enterprise application parameters. A data repository stores a catalogue of cloud computing patterns. A back-end application computer server retrieves information from the enterprise application data store and, based on enterprise application parameters, creates a move group representing a subset of the enterprise applications. For each application in the move group, the computer server identifies whether an appropriate cloud computing pattern exists in the catalogue. If an appropriate cloud computing pattern is identified, it is used to automatically create a reference implementation of the enterprise application in a cloud computing environment. If no appropriate cloud computing pattern is identified, a pattern on-boarding process may be initiated to add a new cloud computing pattern to the catalogue.

A method, non-transitory computer readable medium, and device that replicates data and provides instantaneous access to data includes receiving in a destination volume one or more named data extents and one or more references to the one or more named data extents associated with a file in parallel from a source volume. A determination is made to check whether the one or more references arrive before the one or more named data extents arrive. Each of the received one or more references which are determined to have arrived prior to the one or more data extents is allocated as absent by the storage management computing device. An instantaneous access to the file is provided during the allocation.

Technologies are disclosed for migrating large amounts of data objects, e.g., billions of data objects, from a distributed data store to another data store or computing device. A method includes generating an inventory of the data objects in the distributed data store and dividing the inventory into multiple listings of data objects. Each data object is identified in only one corresponding listing. Manifests are generated based upon the listings. Each manifest is assigned to a corresponding portable storage device of a plurality of portable storage devices, and the data objects and listings are transferred, based at least in part, upon the manifests to the plurality of portable storage devices. The inventory of the data objects and the plurality of portable storage devices are provided to an entity associated with the another data store or computing device. The data objects are transferred from the plurality of portable storage devices to the another data store or computing device using the inventory.

A computer-implemented method includes receiving custom metadata for several data items, the data items having system metadata associated therewith, selecting, based on the custom metadata, some of the data items to move between a primary storage system and a secondary storage system, and moving the selected data item(s) between the primary storage system and the secondary storage system. A computer program product includes a computer readable storage medium having program instructions embodied therewith. The program instructions are executable by a computer to cause the computer to perform the foregoing method. A system includes a processor and logic integrated with the processor, executable by the processor, or integrated with and executable by the processor. The logic is configured to perform the foregoing method.

Solutions for supporting storage using a multi-writer log-structured file system (LFS) are disclosed that include receiving incoming data from an object of a plurality of objects that are configured to simultaneously write to the LFS from different nodes; based at least on receiving the incoming data, determining whether sufficient free segments are available in a local segment usage table (SUT) for writing the incoming data; based at least on determining that insufficient free segments are available, requesting allocation of new free segments; writing the incoming data to a log; acknowledging the writing to the object; determining whether the log has accumulated a full segment of data; based at least on determining that the log has accumulated a full segment of data, writing the full segment of data to a first segment of the free segments; and updating the local SUT to mark the first segment as no longer free.

The disclosed technology relates to a system configured to detect a modification to a node in a tree data structure. The node is associated with a content item managed by a content management service as well as a filename. The system may append the filename and a separator to a filename array, determine a location of the filename in the filename array, and store the location of the filename in the node.

According to aspects of the disclosure, there is provided a scalable cloud distributed database system for hosting data of multiple database tenants. In some embodiments, the database may be serverless. The serverless database may be configured to automatically and dynamically match resources to workload demands for tenants of the database. Databases described herein may include replica sets hosting multiple tenants. Tenants may be migrated from one replica set to another replica set based on usage. Usage of tenants may be throttled during migration between replica sets. Tenants with lower usage may be selected for migration between replica sets. During migration, files containing both a document and a history of updates to the document may be migrated. Databases described herein may include multiple storage tiers having different read and/or write speeds.

Systems and methods electronically tag received data associated with an entity with an electronic tag including an identifier uniquely associated with the entity. The system may electronically store the received data such that the received data is identifiable via the electronic tag. Then, when a request for deletion of all the entity’s data is made by the particular entity, it is fulfilled with much less effort, namely by searching for elements with that entity’s tag. Whenever that data is copied, transformed, or derivative data is made, the system copies the electronic tag with it. Thus, even when the data is copied or modified, it can be more efficiently identified as being associated with the particular entity. In some embodiments, the tagging includes electronically recording an association of the electronic tag with the received data as a transaction on a blockchain, the transaction on the blockchain being associated with the electronic tag and with the received data.

Techniques for performing test adaption and distribution for customer storage systems in accordance with a customer knowledge base. The techniques can include sending, by each customer storage system, data to the customer knowledge base. The data includes, for each customer storage system, a version of a data storage application and associated system configuration and parameters. In response to a query from a QA testing system, the data is migrated from the customer knowledge base to a QA database. The QA testing system analyzes the data to determine the most common system configuration, parameters, and data storage application version for most of the customer storage systems. The QA testing system adapts a test plan for testing the data storage application to conform with the most common system configuration and parameters and executes an application upgrade plan on QA storage appliances pre-prepared in accordance with the most common data storage application version.