Proposed is a digital multi-channel platform based on a multi-channel, high-layer data-transfer structure accessible by means of web-client applications running on front-end network-enabled devices providing discrete high-layer data-flow and capturing of structured and unstructured data content transferred from the front-end network-enabled devices over a data transmission network to a digital multi-channel back-end system.

A computerized-method to conduct a staggered maintenance activity based on tenants' prioritization for tenants of a cloud-based Software as a Service (SaaS) platform contact-center, is provided herein. The computerized-method includes operating a Staggered-Maintenance-Activity (SMA) module. The SMA module includes: (i) selecting a plurality of tenants from the data store of one or more tenants, for a migration activity; (ii) allocating each tenant in the plurality of tenants for migration activity, to a maintenance-window of one or more maintenance-windows; (iii) prioritizing the allocated plurality of tenants to yield an ordered list of tenants, in each maintenance-window of the one or more maintenance-windows; (iv) operating a migration activity during each maintenance-window, of the one or more maintenance-windows, according to the yielded ordered list of tenants; and (v) sending a notification with details of each migration activity to a corresponding tenant administrator, to be displayed, via a display unit.

Embodiments provide for identifying and resolving conflicts in access permissions migrated data by receiving a set of mappings including path mappings of a hierarchy of data objects on the source system to locations on the target system for migrated data objects. Based on the received set of mappings, permissions controlling access to data objects of the hierarchy of data objects on the source system can be translated to permissions controlling access to the migrated data objects on the target system for one or more user accounts on the target system. One or more conflicts can be detected between permissions on the source system and permissions on the target system. A conflict resolution strategy can be selected from a plurality of conflict resolution strategies and the selected conflict resolution strategy can be applied to the permissions controlling access to the migrated data objects on the target system.

Embodiments for enabling granular migration of data with high efficiency. A defined metadata element, a tag, is assigned to each file, and then tag filtering is used to direct the data to the proper location. Files with different tags can be selected for transfer, and such a group of tags is referred to as a tag set. Embodiments can be used with a defined backup system file migration process, such as present in the Data Domain File System. By using snapshots, incoming new data (ingested file) is allowed to continue while the migration is in process and maintaining data consistency at the same time. This is achieved by performing operations on B+ Tree snapshots in conjunction with tag filtering on keys present in the leaf pages of these structures. This method is efficient became it makes a single pass walk of a B+ Tree in contrast with previous methods that look up files one-by-one via their pathname.

One or more buckets of key-value pairs of a first node of a distributed storage system are selected to be migrated to a second node of the distributed storage system. One or more underlying database files corresponding to the one or more selected buckets are identified. The one or more identified underlying database files are directly copied from a storage of a first node to a storage of the second node. The copied underlying database files are linked in a database of the second node to implement the one or more selected buckets in the second node.

In accordance with embodiments, there are provided mechanisms and methods for creating, exporting, viewing and testing, and importing custom applications in a multitenant database environment. These mechanisms and methods can enable embodiments to provide a vehicle for sharing applications across organizational boundaries. The ability to share applications across organizational boundaries can enable tenants in a multi-tenant database system, for example, to easily and efficiently import and export, and thus share, applications with other tenants in the multi-tenant environment.

Techniques and solutions are described for storing and processing metadata, including to instantiate database artefacts at a target system based on metadata for database artefacts maintained at a source system. The target system can query the source system for metadata associated with database artefacts of the source system. The target system can instantiate database artefacts based on such metadata. The database artefacts of the target system are linked to corresponding database artefacts of the source system, such as by associating a database artefact of the target system with an API useable to obtain data or metadata from the source system for a corresponding database artefact of the source system. The target system obtains additional data or metadata for a database artefact of the target system using a corresponding API.

A point-in-time clone may be created for a database. A request to create the point-in-time clone may be received. The clone may be provided with access to a storage for the database that stores a history of modifications to the database applicable to return data of the database according to a state of the data at the specified point in time. The clone may then be updated so that the updates made to the clone are stored for subsequent access by the clone.

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 method and system for converting database applications into blockchain applications is disclosed. Multiple applications on different nodes can automatically perform global data consensus to prevent data conflicts using the embodiments described. One method involves monitoring databases as they is modified by database applications, to extract data operations from transaction logs, convert the data operations to a general format, and activate the smart contract on the blockchain to complete the data consensus check at multiple nodes. Each node monitors the blocks on blockchain and synchronizes the data back to database. In the case of conflicting data, the data is not able to pass consensus and synchronize with the other nodes in the blockchain. The local nodes automatically roll back when detecting invalid data.