Abstract: Disclosed in some examples are methods, systems, memory devices, and machine-readable mediums that allows an application thread to indicate an undo logging operation when calculations are beginning that may need to be rolled back if a crash or other failure occurs. During the undo logging operation, memory writes an identified memory are done to a copy and the original value is preserved. If the undo logging operation is committed, then the copy becomes the correct value and may then be subsequently used in place of the original, or the value stored in the copy is copied to the original. If the undo logging operation is abandoned, the copy is not preserved and the value goes back to the original.

Abstract: Architectures and techniques are presented that can more efficiently update derived data products in response to updated source data. Source data is typically stored in source tables, whereas a materialized view of a query can generate a derived table based on the state of the source tables at the time the query is executed. When source data changes (e.g., in response to late-arriving input data), rather than recomputing the entire derived table (e.g., by again executing the original query, which can be expensive), an invertible relationship between timestamps can be leveraged to identify only those portions of the derived table that are affected by the update. Therefore, a new defining query can be generated to update only those portions of the derived table that are affected by the source data update.

Abstract: Techniques are described with regard to managing transaction size during a database replication process. An associated computer-implemented method includes identifying each of at least one transaction associated with at least one source database stored in a replication capture memory, identifying at least one potential excessive memory transaction by applying, via at least one machine learning pattern detection model, pattern detection to each of the at least one transaction stored in the replication capture memory, and constructing at least one compact data unit associated with each of the at least one potential excessive memory transaction. The computer-implemented method further includes facilitating compact data unit transmission to a replication apply server system in order to replicate the at least one compact data unit associated with each of the at least one potential excessive memory transaction to at least one target database via a replication apply server application.

Abstract: One example method includes performing delta operations to protect data. Each delta generated by a data protection operation includes data. The deltas are stored in a delta queue, when moving a current replica to another point in time represented by the selected delta in the delta queue, the deltas are processed so that all relevant data can be applied in a batch. This ensures that when the same extents are represented in multiple deltas, only the oldest version is applied to the replica volume to move the current replica to the selected point in time.

Abstract: A system for indexing includes an interface and a processor. The interface is configured to receive a metadata amendment. The metadata amendment defines a change to a transactional index schema to a first transactional index. The first transactional index comprises a querying system data. The processor is configured to maintain a first state of the first transactional index. The first transactional index does not incorporate the metadata amendment. The processor is configured to build a second transactional index incorporating the metadata amendment, determine whether an indication to switch from the first transactional index to the second transactional index has been received, and indicate to switch from using the first transactional index to the second transactional index for queries regarding a system data.

Abstract: Systems and methods for updating policy profiles can include utilizing one or more machine learning processes to determine a probability of the likelihood that an available insurance policy data point within a set of currently available policy data points is incorrect. The system may further generate a plurality of policy profile data points based on those determined probabilities. This plurality of policy profile data points can be associated with various customer insurance policies. The system can further parse the plurality of data points for collection, generate uniform resource locator data for each data point type and associate each data point with uniform resource locator data. Finally, the system can utilize the generated uniform resource locator data to locate and copy updated data point data related to the associated data point for each data point and format the data point data for transmission to an agent management system for further processing.

Abstract: Generating any point in time backups from secondary storage without native snapshot generation and providing failover capabilities from a primary storage. Data or IOs from a source are distributed to both the primary storage and the secondary storage. When a disaster occurs with one of these storages, recovery of one of the storages can be achieved using a delta marker and data from the other of the storages.

Abstract: One example method includes a splitter for data protection operations including replication operations. The splitter is located on or integrated into a smart network interface card and operates in two modes. The splitter is controlled by a replication controller. In one mode, the control path and the data path both go to the replication controller. In another mode, the data path is directly from the splitter to one or more targets without passing through the replication controller.

Abstract: A database system may include a database service and a separate distributed storage service. The database service (or a database engine head node thereof) may be responsible for query parsing, optimization, and execution, transactionality, and consistency, while the storage service may be responsible for generating data pages from redo log records and for durability of those data pages. For example, in response to a write request directed to a particular data page, the database engine head node may generate a redo log record and send it, but not the data page, to a storage service node. The storage service node may store the redo log record and return a write acknowledgement to the database service prior to applying the redo log record. The server node may apply the redo log record and other redo log records to a previously stored version of the data page to create a current version.

Abstract: Techniques for adjusting storage space involve: receiving a request for adjusting available storage space of a user in a filesystem from a first size to a second size; determining whether to allow to adjust the available storage space based on the request; and in response to allowing to adjust the available storage space, adjusting the available storage space to the second size. Accordingly, not only operations that an administrator needs to perform for adjusting the available storage space of a user is reduced, but also a quick and correct response for a request from a user of adjusting the available storage space is guaranteed.

Abstract: Disclosed herein is a data structure that reduces computational load on a database in querying and visualizing historical values of slowly changing dimensions. The slowly changing dimensions have one or more values associated with them (e.g., a monthly average accounts receivable is a single value, and a set of contact information for an individual may have multiple values). On a periodic basis, database images, also known as “snapshots” are generated of a current status of a given database. The snapshots are used to build a historical data table that is computationally efficient to reference.

Abstract: One or more techniques and/or computing devices are provided for moving a consistency group having a replication relation. For example, a first consistency group of storage objects (e.g., files, logical unit numbers (LUNs), etc.) within first storage may have a replication relationship with a second consistency group within second storage (e.g., the second consistency group is maintained as a synchronously replicated copy of the first consistency group). A volume copy operation, a single file move on demand command, a single file restore command, or other functionality is used to move the first consistency group from the first storage to third storage, such as for load balancing, to create a moved first consistency group within the third storage. A new replication relationship is established between the moved first consistency group and the second consistency group, and the moved first consistency group and the second consistency group are resynchronized.

Abstract: A system and method may reduce the costs associated with adding or editing configuration elements for an API. A generic schema for the API codebase may keep the configuration definitions flexible and associations between various configuration definitions may also be saved within the codebase. New configuration instances may then be created using the definition of the configuration. Since the definition of the configuration is saved in a codebase, updating the definition or adding a new definition will not require going through the cycle of requirement analysis, coding, and testing. Once the definition is updated, the application code may appropriately mark the difference between the configuration instance and its definition and it will utilize the new definition to create instances of the new configuration.

Abstract: Systems and methods provide multi-version concurrency control of database records with uncommitted transactions. The system and methods may include receiving a query regarding a transaction counter number. When a transaction header identifying data is updated with the assigned transaction counter number, the updated transaction header may be used in identifying data as an instance of multiversion concurrency control information by the received query. A key lookup may be performed, and when the key lookup encounters an uncommitted row for a transaction number, a corresponding transaction header identifying data to identify a data array element to determine whether the transaction number is committed, and determining the transaction counter number when the transaction number is committed. The transaction counter number may be stamped on the row version record when it is determined that the row is committed.

Abstract: A method for managing data includes obtaining, by a first storage controller, a write request associated with an object from a host, applying an erasure coding procedure to data associated with the write request to obtain a plurality of data chunks and at least one parity chunk, wherein object comprises the data, deduplicating the plurality of data chunks to obtain a plurality of deduplicated data chunks, generating storage metadata associated with the plurality of data chunks and the at least one parity chunk, generating an object entry associated with the plurality of data chunks, storing, across a first plurality of persistent storage devices, the plurality of deduplicated data chunks and the at least one parity chunk, and storing, via a continuous data protection interceptor executing on the first storage controller, in at least one of a second plurality of persistent storage devices the object entry.

Abstract: The present disclosure relates to a system and techniques for enabling data to be updated within a data store through concurrent operations. Embodiments of the system enables multiple client applications (e.g., implemented on a cloud platform) to update data concurrently. In some embodiments, operations may be determined to be either client-managed operations or service-managed operations. Client-managed operations may be performed by a client application, whereas the client application may pass service-managed operations to a service application. The service application may put each of the service-managed operations into a commit queue wherein each service-managed operation is committed only after the one put into the queue before it has been committed.

Abstract: Batch processing of undo log records may be performed for rolling back a database transaction. When a rollback operation for a database transaction is performed, undo log records from an undo log to rollback the database transaction are divided into different groups of undo log records. Different requests for the different undo log records are sent to a storage system to be performed. If a conflict is detected for an undo log record in a group, an indication of the conflicting undo log record may be provided to indicate the conflict. The group of undo log records may be resent with a request to reapply the undo log records in the group. When all groups have been identified as successfully completed, then the rollback operation may be considered completed.

Abstract: A serverless application is provided to a cloud site of a cloud services provider. The cloud services provider offers backend services that include an object store and a database. Input/output (IO) writes sent to a volume of a block storage device at a production site are intercepted and aggregated. The aggregated IOs and metadata for the IOs are transmitted from the production site to the cloud site of the cloud services provider. Upon receipt of the aggregated IOs and metadata at the cloud site, the aggregated IOs are stored in an object in the object store at the cloud site, and a function of the serverless application is triggered to write the metadata to the database offered by the cloud services provider.

Abstract: A first storage system in one illustrative embodiment is configured to participate in a replication process with a second storage system. The first storage system detects a replication failure condition or other condition requiring termination of a synchronous replication mode of the replication process, and responsive to the detected condition, captures a snapshot of source data that is subject to replication from the first storage system to the second storage system as part of the replication process. The first storage system terminates the synchronous replication mode of the replication process, initiates an asynchronous replication mode of the replication process, executes an asynchronous-to-synchronous transition cycle scan operation for the replication process utilizing the captured snapshot, and resumes the synchronous replication mode of the replication process responsive to successful completion of the asynchronous-to-synchronous transition cycle scan operation.

Abstract: The present invention relates to a method for determining a configuration operable by a configurable electronic device. The device receives a second configuration and a predefined parameter. The device archives a first configuration in the non-transitory computer readable storage medium. The device applies the second configuration and then determine whether the predefined parameter is satisfied. When the predefined parameters are satisfied, the device maintains to apply the second configuration. When the predefined parameter is not satisfied, the device retrieves the first configuration and applies the first configuration.

Abstract: Managing databases implemented in a cloud computing environment. A method includes detecting that a database implemented in the cloud computing environment is in a state of non-use. The method further includes as a result of detecting that a database implemented in the cloud computing environment is in a state of non-use, instantiating a workload in the cloud computing environment to deactivate the database. The workload is configured to store metadata for the database and database data remotely in cloud storage such that the database can be reactivated at a later time.

Abstract: A service implements techniques for modifying a data table stored in a key-value or non-relational database via a table-oriented schema. In some aspects, a request to modify a table-oriented schema of a table of data may be received. In response to the request, an association between a customer identifier of elements of the table and an internal identifier of elements of the table may be stored that updates a prior association between a customer identifier and an internal identifier. The table-oriented schema of the table may be modified using one or more keys that are generated using the internal identifier.

Abstract: A plugin is provided to a service that includes a database for storing data corresponding to transactions received by the service and applied to the database. Upon receipt of a transaction to be performed by the service, the plugin receives a message generated by the service and associated with informing another service of the transaction. The message is stored in the database together with the transaction, the message and transaction thereby being in the same transactional context. Upon the transaction being committed, the message is also processed because the transaction and message are in the same single transactional context within the database.

Abstract: A system and method for disk replication over a network with network failover, the method including: generating at least one write packet when a write instruction is detected from a first computing environment, where the at least one write packet includes: metadata associated with a data block, and a packet identifier; storing the at least one write packet in a cache; sending the at least one write packet from the cache to a second computing environment for storage; and determining if the at least one write packet has been successfully stored in the second computing environment.

Abstract: Detect duplicated questions using reverse gradient adversarial domain adaptation includes applying a general network to multiple general question pairs to obtain a first set of losses. A target domain network is applied to multiple domain specific network pairs to obtain a second set of losses. Further, a domain distinguishing network is applied to a set of domain specific questions and a set of general questions to obtain a third set of losses. A set of accumulated gradients is calculated from the first set of losses, the second set of losses, and the third set of losses. Multiple features are updated according to the set of accumulated gradients to train the target domain network.

Abstract: One or more techniques and/or computing devices are provided for snapshot creation. For example, a request may be received to create a snapshot of a first storage object, hosted by a first storage controller, having a synchronous replication relationship with a second storage object hosted by a second storage controller. A coordinator workflow is initialized to issue a drain and hold request to a splitter. Responsive to an indication that the splitter has stopped processing and started queuing incoming write operations and has drained current write operations based upon the drain and hold request, snapshot creation requests are sent to the first storage controller and the second storage controller. Responsive to the first storage controller creating a first snapshot of the first storage object and the second storage controller creating a second snapshot of the second storage object, the splitter may be resumed to process write operations.

Abstract: Predicting large data flushes by collecting usage data for system assets, analyzing the data using machine learning on each asset and the whole system to determine usage trends, predicting a next large data flush using a time-series model, and determining if a size of the predicted next flush size is too large relative to journal storage space in order to advance fast forward mode. Further, protecting history information by pausing distribution of data from journal volumes to replica volumes, taking storage-level snapshots of the replica and the journal volumes, storing a snapshot timestamp for each of the storage-level snapshots in a snapshot database prior to advancing the fast forward mode or un-pausing distribution.

Abstract: A content management system provides event data relating to other users' activity or interactions with a content item for display in an activity feed provided in conjunction with a user interface of a native application displaying the content item. Though provided in conjunction with the native application, the event data is maintained separate from the content data of the content item and displayed in the activity feed by an application separate from the native application of the content item. The activity feed permits users to exchange chat messages and retrieve information for multiple versions of the content item.

Abstract: A non-transitory computer-readable recording medium storing a data acquisition program that causes a computer to execute a process including: identifying a position of a part to be extracted in a document that is associated with a specific URL and includes structural information of tags, the position being on a hierarchical structure of the tags included in the document, and allowing the position on the hierarchical structure to be registered; and accessing periodically or non-periodically the document associated with the specific URL, and extracting and outputting data corresponding to the registered position on the hierarchical structure of the tags.

Abstract: A database system may include a database service and a separate distributed storage service. The database service (or a database engine head node thereof) may be responsible for query parsing, optimization, and execution, transactionality, and consistency, while the storage service may be responsible for generating data pages from redo log records and for durability of those data pages. For example, in response to a write request directed to a particular data page, the database engine head node may generate a redo log record and send it, but not the data page, to a storage service node. The storage service node may store the redo log record and return a write acknowledgement to the database service prior to applying the redo log record. The server node may apply the redo log record and other redo log records to a previously stored version of the data page to create a current version.

Abstract: Aspects of the inventive concept relates to a method of accessing a storage device including a nonvolatile memory device and a controller. The method includes writing user data, a first logical address and a second logical address associated with the user data in a storage space corresponding to the first logical address of the nonvolatile memory device. The user data is update data that updates previous data written in the nonvolatile memory device. The second logical address is a logical address of a storage space of the nonvolatile memory device in which the previous data is written.

Abstract: Synchronization metadata is read from non-volatile storage. The synchronization metadata comprises indications of one or more synchronization targets. A synchronization target is a node of a clustered storage system. A synchronization cache is populated with the synchronization metadata. After populating the synchronization cache with at least a portion of the synchronization metadata, a connection to a network is established. After the connection to the network is established, a connection to a first of the one or more synchronization targets is established.

Abstract: Techniques are disclosed for providing an aggregate key performance indicator (KPI) that spans multiple services and for receiving user adjustment to KPI factors to configure an aggregate KPI (e.g., heath score). The techniques may enable a user to select KPIs and to adjust weights (e.g., importance) associated with the KPIs. The weight of a KPI may affect the influence a value of the KPI has on the calculation of an aggregate KPI value. The techniques may also include the ability to create a correlation search using the selected KPIs and weights so that a notification may be generated when the aggregate KPI value exceeds a threshold.

Abstract: An issue is detected in the operation of a set of integrated applications. Assistive logic is launched and an application, causing the issue, is identified. Application running logic is controlled to roll the application back to a last known good state.

Abstract: Systems and methods provide multi-version concurrency control of database records with uncommitted transactions. The system and methods may include receiving a query regarding a transaction counter number. When a transaction header identifying data is updated with the assigned transaction counter number, the updated transaction header may be used in identifying data as an instance of multiversion concurrency control information by the received query. A key lookup may be performed, and when the key lookup encounters an uncommitted row for a transaction number, a corresponding transaction header identifying data to identify a data array element to determine whether the transaction number is committed, and determining the transaction counter number when the transaction number is committed. The transaction counter number may be stamped on the row version record when it is determined that the row is committed.

Abstract: The present disclosure discloses a data processing method and device for Internet entity analysis. The data processing method includes: acquiring a first entity state and a second entity state; acquiring first indicator data and second indicator data, the first indicator data being indicator data of the first entity state and the second indicator data being indicator data of the second entity state; and acquiring a corresponding relationship between the entity state and the indicator data, the corresponding relationship including a first corresponding relationship and a second corresponding relationship, the first corresponding relationship being a corresponding relationship between the first entity state and the first indicator data and the second corresponding relationship being a corresponding relationship between the second entity state and the second indicator data.

Abstract: Example apparatus and methods create and maintain a functional mirror of file system metadata for an active file system. The functional mirror may be implemented as a set of feature vectors in a feature space stored in a spatial database that allow a journal functionality for information received from the active file system. Mirror creation and maintenance can operate in parallel. The functional mirror may be created primarily using a systematic, system-wide, multi-threaded crawler approach whose results are updated using an event-driven approach that accounts for changes that may obsolete information acquired during the crawler approach. Transaction identifiers may be stored and potentially obsolete information preserved to facilitate providing views and rewind features.

Abstract: Example embodiments of the present invention relate to a method, a system, and a computer program product for enabling concurrent host access at a replica site to a point in time different than a current point in time of a replication environment. The method includes performing data protection from a production site to a replica site in a replication environment and enabling concurrent host access at the replica site to a point in time different than a current point in time of the replication environment.

Abstract: A computer system for using an undo stack to explore past actions and apply new actions to previous states in a data view is provided. The computer system includes program instructions to detect a change in an application data view. The application then displays an undo stack and stores the data change in the application data view to the undo stack. Upon detecting a selection of the undo stack entry for undo, the application returns the application data view to the state represented by the undo stack entry. The computer system further includes program instructions to provide a user interface allowing a user to perform operations on undo stack entries. Responsive to the user utilizing the user interface and making selections, the application then adjusts the application data view state based on the performed actions.

Abstract: A computer program product for using an undo stack to explore past actions and apply new actions to previous states in a data view is provided. The computer program product includes program instructions to detect a change in an application data view. The application then displays an undo stack and stores the data change in the application data view to the undo stack. Upon detecting a selection of the undo stack entry for undo, the application returns the application data view to the state represented by the undo stack entry. The computer program product further includes program instructions to provide a user interface allowing a user to perform operations on undo stack entries. Responsive to the user utilizing the user interface and making selections, the application then adjusts the application data view state based on the performed actions.

Abstract: A method includes receiving a user inputted lower-level hierarchical filter key, processing filter key relational data to identify higher-level filter criteria keys associated with the user inputted lower-level hierarchical filter key, updating higher-level filter criteria to include the identified higher-level filter criteria keys, and generating a list of results according to the updated filter criteria. A computer program product and computer system corresponding to the method are also disclosed.

Abstract: Example embodiments of the present invention provide a method, an apparatus and a computer-program product for bandwidth management in a metro-cluster data replication environment. The method includes receiving an I/O at a first site and replicating the I/O from the first site to a second site by synchronous replication. Load balancing is then determined between the first site and the second site. Respective portions of the I/O then may be replicated from at least one of the first site and the second site to a third site by asynchronous replication according to the load balancing.

Abstract: A first communication apparatus for performing wireless communication with a second communication apparatus includes a memory storing a predetermined wireless setting and a confirmation unit confirming whether it is possible to perform wireless communication with the second communication apparatus using a current wireless setting in the first communication apparatus. The first communication apparatus includes a first change unit changing the current wireless setting to the predetermined wireless setting if it is not possible to perform wireless communication using the current wireless setting and specific information is received from the second communication apparatus, and holding the current wireless setting if it is not possible to perform wireless communication using the current wireless setting and the specific information is not received from the second communication apparatus.

Abstract: Techniques are described for schema lifecycle management. In one example, a method includes dividing, with one or more processing devices, a plurality of statements of a data definition language (DDL) script into a plurality of groups, the plurality of groups configured to be executed in parallel by a persistence layer. The method further includes assigning, with the one or more processing devices, one or more of the plurality of groups to a plurality of worker applications. The method further includes executing, with the one or more processing devices, constituent statements of the plurality of statements of the DDL script within each group of the plurality of groups by the plurality of worker applications in a session.

Abstract: Database Definition Language (DDL) transactions are defined that include one or more DDL operations that are to be executed to modify aspects of a relational database, such as its structure. If performance of one or more of the DDL operations in a DDL transaction fails, then the changes made to the relational database by some or all of the DDL operations may be reversed. Instructions and state information may be generated and stored prior to, during, and/or following the execution of a DDL operation that may be utilized to reverse the changes to a relational database made by the DDL operations. User interfaces might also be provided for defining, selecting, editing, and executing DDL transactions, and for providing information relating to the execution and rollback of DDL operations in a DDL transaction.

Abstract: Systems and methods for restoring files and metadata records associated with files are provided herein. Some of the methods include identifying a version of the file, evaluating one or more reverse incremental delta increments, and restoring an arbitrary version of the file based on an arbitrary time reference by assembling the arbitrary version of the file based on the one or more reverse incremental delta increments.

Abstract: A mechanism is provided for restoring a file recorded on a storage medium to a previous version of the file. At least two different versions of a file recorded on the storage medium are presented to a user via a graphical user interface, where the at least two different versions of the file are identified from at least two different indexes recorded on the storage medium. Responsive to a selection of the previous version of the file from the at least two different versions of the file, the file is restored to the previous version of the file by recording a new index on the storage medium for the file that matches an index of the file associated with the previous version of the file.

Abstract: Systems and methods for undoing changes or modifications made to a communication network are described. In some embodiments, the systems and methods access a request to rollback one or more changes made to parameters of managed objects associated with a communication network within a given time period, retrieve information identifying the one or more changes made to the parameters of the managed objects within the given time period, and, for each managed object, determine a cumulative changetype (e.g., add, deleted, or update) associated with the one or more changes made to the parameters of the managed object and perform an action to apply the determined cumulative changetype to the managed object.

Abstract: A computer implemented method, system, and program product for data consistency comprising establishing a memory-mapped file, enabling the memory-mapped file data to be paged to the non-volatile storage medium, receiving, at a consistency layer, a write IO; wherein the write IO corresponds to a space on the storage medium, issuing a read IO to the storage medium, wherein the read IO corresponds to the space on the storage medium to be overwritten by the write IO, writing the data of the read IO to a undo log and writing the write IO to the storage medium.

Abstract: In accordance with embodiments disclosed herein, there are provided methods, systems, and apparatuses including, for supporting transactional message handling in an on-demand service environment including, for example: enqueuing a message specifying a transaction to be processed via a host organization; inserting a row into a database of the host organization associating the message with a status of pending, wherein the row is autocommitted to the database upon insertion; updating the status for the row to ready if a commit operation for the transaction is initiated; requesting a lock on the row; and performing final processing for the transaction based on the status for the message and based further on whether the lock is obtained for the row. Final processing may include, for example, a transaction roll back, a transaction commit, a transaction requeue, a termination of transaction processing, or an orphaned transaction clean up.