Abstract: Provided are a computer-implemented method, system, and computer program product for multidimensional data recover. A snapshot restore request is received with at least one parameter defining at least one dimension for data recovery. At least one snapshot is reconstructed from a single continuous snapshot stream taken for a certain period of time based on the at least one parameter. A selected snapshot is received for data recovery selected from the at least one reconstructed snapshot. The selected snapshot is restored.

Abstract: Techniques are described for backup and restore of a thin-cloned data file. The process iterates through a plurality of memory portions of the thin-cloned data file and determines whether a memory portion of the thin-cloned data file is a memory portion with common data shared with the source data file. Without storing the common data of the shared memory portion into the thin-backup data file, the process stores placeholder metadata and corresponding reference to the shared memory portion for the thin-backup data file, in an embodiment. At restore, the process may replicate the derivative data, different from the common data, from the thin-backup data file into the thin-restored data file. For the common data, the process restores a reference for the thin-restored data file to the share memory portion, in an embodiment.

Abstract: Methods, systems, and computer-readable media for versioned metadata management for a time-series database are disclosed. A metadata service of a distributed time-series database stores, to one or more metadata storage resources, first metadata descriptive of a table. The first metadata is associated with a version number in a logical sequence for the table. The metadata service stores, in a log, data indicative of one or more metadata updates for the table. The metadata update(s) are associated with an additional version number higher than the version number in the logical sequence. Responsive to a read request, the metadata service determines a most recent version number that has been applied from the log to the metadata storage resource(s). Responsive to the read request and based (at least in part) on the most recent version number, the metadata service returns either the first metadata or second metadata comprising the update(s).

Abstract: A storage management computing device obtains an information lifecycle management (ILM) policy. A data protection scheme to be applied at a storage node computing device level is determined and a plurality of storage node computing devices are identified based on an application of the ILM policy to metadata received from one of the storage node computing devices and associated with an object ingested by the one of the storage node computing devices. The one of the storage node computing devices is instructed to generate one or more copies of the object or fragments of the object according to the data protection scheme and to distribute the object copies or one of the object fragments to one or more other of the storage node computing devices to be stored by at least the one or more other storage node computing devices on one or more disk storage devices.

Abstract: An improved information management system is described herein that provides on-demand or live mount access to virtual machine data in a secondary copy format. For example, instead of restoring all of the virtual machine data in the secondary copy format to a virtual disk that is then mounted to a virtual machine, the improved information management system can, in response to request to access virtual machine data in a secondary copy format, create a virtual disk having a universal network component (UNC) path and create a virtual machine configured to access data via the UNC path. Once created and booted, the administrator or user can attempt to access the desired virtual machine data via the virtual machine.

Abstract: Data chunks sent to a content destination are tracked. It is determined whether content of a portion of an object to be sent to the content destination matches one of the data chunks previously sent to the content destination. In response to the determination that the portion of the object to be sent to the content destination matches one of the data chunks previously sent to the content destination, a source reference to the matching previously sent data chunk where the content destination can locally obtain the content for the portion of the object is provided to the content destination.

Abstract: Systems and methods for generating database schema change documents based on a data model and model changes indicated by a user. Information items related to one or more objects defined in the data model are received, and user input regarding changed objects is requested. In embodiments, changes are evaluated against configurable design criteria. One or more human and/or machine readable database schema change documents, and are stored in memory. Design criteria and change documents can vary based on a target database platform in embodiments.

Abstract: Methods and apparatus for acquiring and analyzing digital forensic data using a computing device. Forensic data collections are retrieved by a computing device, and artifacts can be identified according to a variety of display types and presentation formats specified in an extensible format, to facilitate review and reporting by a user.

Abstract: Data can be processed in parallel across a cluster of nodes using a parallel processing framework. Using Web services calls between components allows the number of nodes to be scaled as necessary, and allows developers to build applications on the framework using a Web services interface. A job scheduler works together with a queuing service to distribute jobs to nodes as the nodes have capacity, such that jobs can be performed in parallel as quickly as the nodes are able to process the jobs. Data can be loaded efficiently across the cluster, and levels of nodes can be determined dynamically to process queries and other requests on the system.

Abstract: Disclosed herein are systems, methods, and processes to perform context-driven (or context-based) data backup and recovery operations. A request to perform a backup operation on a dataset is received. Current external context datasets related to the dataset and generated based on prioritization techniques are collected from computing devices. a saved context dataset is generated based on the current external context datasets. The backup operation is performed by storing a backup image that includes at least a portion of the dataset and the saved context dataset.

Abstract: Techniques are described for presenting application variations on a user interface. In an example, the techniques include associating computer applications with an application group, the computer applications being different variations of a same computer program. The techniques further include generating a user interface (UI) element that represents the application group. The techniques further include selecting a first computer application of the computer applications to indicate in association with the UI element. The techniques further include presenting the UI element on a user interface, the UI element indicating the application group and the first computer application, the UI element configured to, upon selection via the user interface, launch the first computer application or launch a page about the application group.

Abstract: Methods and systems for improving data back-up, recovery, and search across different cloud-based applications, services, and platforms are described. A data management and storage system may direct compute and storage resources within a customer's cloud-based data storage account to back-up and restore data while the customer retains full control of their data. The data management and storage system may direct the compute and storage resources within the customer's cloud-based data storage account to generate and store secondary layers that are used for generating search indexes, to generate and store shared space layers and user specific layers to facilitate the deduplication of email attachments and text blocks, to perform a controlled restoration of email snapshots such that sensitive information (e.g., restricted keywords) located within stored snapshots remains protected, and to detect and preserve emails that were received or transmitted and then deleted between two consecutive snapshots.

Abstract: Example embodiments of the present invention provide a method, an apparatus, and a computer program product for providing information lifecycle management using a federation of arrays. The method includes receiving a request to provision storage resources of a one big array according to a class of service, the one big array comprising heterogeneous storage resources, and causing the requested storage resources to be provisioned according to a provisioning policy. Execution of an information lifecycle management policy then may be initiated for management of data stored to the storage resources according to the class of service.

Abstract: Methods and systems for accessing, maintaining, analyzing, and visualizing structured data are presented. The system receives from a requesting computing device, a first request for a first hierarchical record. The system searches a first repository having first structured data. The system determines whether the first hierarchical record is present in the first structured data and creates, based on the first hierarchical record, a snapshot query criterion. The system then searches, based on the snapshot query criterion, a second repository comprising a first snapshot of the first structured data. The system determines whether a second hierarchical record at least partially matches the first hierarchical record.

Abstract: A method of prioritizing replication of database objects between storage devices includes receiving a request to replicate data from a first to a second storage device; accessing a queries previously executed on the first device; determining database objects associated with the queries; calculating access metrics for the database objects indicating how the database objects were accessed by the queries; determining a subset of database objects for replication based on the access metrics; and initiating a data replication process to replicate the subset of database objects from the first device to the second device that prioritizes the subset of database objects relative to a remainder of the database objects.

Abstract: Described is a system for intelligently storing and recovering backup data using multiple storage tiers of a cloud-based storage. The intelligent storing of backup data may leverage different cost structures associated with various cloud-based storage tiers by efficiently distributing data to more cost effective tiers. The system may also provide a coordinated (e.g. phased) recovery that prioritizes the recovery of certain files so that a user can gain access to such files in a shorter amount of time. The system may also provide enhanced storage and recovery functionality (e.g. via specialized user interface elements) by leveraging placeholder files to offload and recover individual files, and expedite the recovery of individual files during a substantial recovery process.

Abstract: A method for storing data includes establishing an extended generation group comprising a plurality of data sets. The plurality of data sets includes a first data set containing primary members and a first number of generations of each of the primary members, and a second data set containing a second number of generations of each of the primary members. The method further indicates, in the metadata of the first data set, a maximum number of generations allowable in each of the first and second data sets When a primary member is modified in the first data set, the method automatically moves an oldest generation in the first data set to the second data set, and deletes an oldest generation in the second data set to ensure that the extended generation group does not exceed the maximum number.

Abstract: Initially, a database schema is parsed and a table tree structure is created delineating the relationships between data that are identified in the schema. In addition to accommodating relationships between main tables of data, the table tree structure also accommodates possible side tables of data, and possible circular references between tables, should such be encountered when parsing the schema. Subsequently, a migration mechanism consumes the generated table tree structure and iteratively migrates data in accordance therewith. Individual layers of the table tree structure are migrated consecutively with referenced layers being migrated prior to referencing layers. Circular links are accommodated through temporary null values, and side tables are accommodated during migration of the referencing main table. The iterative process provides completeness and fault tolerance/failure recovery.

Abstract: A method, apparatus, and system for performing file system restoration to a plurality of recovery destination virtual machines is disclosed. The operations comprise: receiving file system recovery requests associated with a same recovery source virtual machine from a plurality of recovery destination virtual machines; spawning a helper virtual machine to facilitate the recovery; configuring the helper virtual machine to host a web server; rebuilding a file system of the source virtual machine at the helper virtual machine; generating a web address served by the web server and associated with files of the rebuilt file system; transmitting the web address from the helper virtual machine to each of the plurality of recovery destination virtual machines through a backup server; downloading, at each of the plurality of recovery destination virtual machines, files of the rebuilt file system from the helper virtual machine to complete the recovery; and deleting the helper virtual machine.

Abstract: Embodiments of the present disclosure relate to a method, device and computer program product for data stream processing. The method comprises activating, in response to receiving a starting first predefined tag in a first input data stream from a first data source, a duplicate process of a process by duplicating a state of the process to the duplicate process. The method further comprises processing, by the duplicate process, only a data unit before an ending second predefined tag in a second input data stream from a second data source without interruption of processing of the first and second input data streams by the process. The second data source differs from the first data source. The method further comprises creating a snapshot of the duplicate process for recovery of the process due to failure in response to receiving the ending second predefined tag in the second input data stream.

Abstract: Methods and apparatus are provided for filtering dynamically loadable namespaces (DLNs). An exemplary method comprises, in response to a job submitted by an application, obtaining a DLN portion of a global single namespace of a file system, wherein the DLN is associated with the job and is maintained in a capacity tier of a storage system; obtaining filtering directives from a user; reducing the DLN using a filtering mechanism on a directory tree associated with the DLN, based on the filtering directives, by removing files in the directory tree of the DLN that do not satisfy requirements of the filtering directives to generate a filtered DLN; and dynamically loading the filtered DLN, including reduced metadata for the filtered DLN relative to the DLN, from the capacity tier into a performance tier of the storage system for processing by the application.

Abstract: Examples relate to extracting data from network communications. In one example, a programmable hardware processor may: receive a first set of network packets; store each network packet included in the first set in a first storage device; identify, from each network packet included in a subset of the first set of network packets, data included in the network packet, the data meeting at least one condition defined by first programmable logic of the programmable hardware processor; and for each network packet included in the subset: extract, from the network packet, data of interest; and store, in a second storage device, i) the extracted data of interest, and ii) an identifier associated with the network packet.

Abstract: Disclosed herein are systems and method for storing and managing states of a computing device. In one aspect, an exemplary method comprises determining an initial state of the computing device, wherein the initial state includes states of all storage sectors associated with the computing device, storing the determined initial state in an initial blocks storage, for each new state that corresponds to a respective point in time subsequent to a time at which the initial state was determined, creating a snapshot, where the created snapshot includes a difference between the initial state and the new state, for each created snapshot, identifying a set of changed blocks that are in storage, and storing the changed blocks of data to a changed blocks storage, and creating a snap-map for any number of consecutive changes based on the sets of changed blocks corresponding to the respective consecutive changes.

Abstract: In one implementation, lightweight incremental backups are created by a data recovery tool, which provides an extra layer of protection against data loss, and also provides a way of moving repositories between databases without the need of copying each of the repositories. Implementations include backing up a distributed cluster of services providing a simple, safe, and convenient way of instantiating files system repositories in a database, thereby avoiding the performance and scalability issues of using a database repository itself. In other implementations, a lightweight backup object is created that includes a threshold amount of compressed information. The lightweight backup objects may be configured to provide the differences between revisions, and/or may be configured to replicate or rebuild the repository from scratch. Implementations may be configured to backup and restore any single or revision set in any repository state either online or offline.

Abstract: Multiple substantially concurrent data streams with NDMP protocol improve robustness, performance, and granularity of backup and restore operations from/to a filer. NDMP data streams are initially allocated based on inventorying the root level of each filer volume. A best effort to balance the multiple NDMP data streams allocates them based on data amounts used in each volume. Orphaned files are also collected and backed up. Subsequent full backup jobs leverage a proprietary index generated in preceding full backup jobs to obtain better performance and to better balance the NDMP data streams by creating substantially co-equal groupings of source data. The index comprises granular information which is not available from querying the filer. The size of each individual backup copy from a preceding full backup job and/or the size of subtending subdirectories or individual backed up files therein is used by later backup jobs to fine tune NDMP data stream allocation.

Abstract: A method, apparatus, article of manufacture, and a memory structure for allocating storage of media programs among global and local storage assets for hot and cold storage is disclosed. Trend data is obtained from a plurality of sources including web page click-throughs and social media, indexed and combined with data describing available media programs to identify media programs of interest and reallocate them to hot storage as required. The system uses REST-compliant methods and commands and is therefore pluggable and can be used with a variety of existing systems.

Abstract: Embodiments of the present invention provide a system and method for synchronizing data to update backup files. In one embodiment, data associated with files to be synchronized is sent to a second computer system by a first computers system. The second computer system matches data associated with the files to be synchronized to a database, and the first computer system determines differences between an old and new version of the files to be synchronized and creates a backup of the files. The backup of the files is stored in a storage device.

Abstract: A computerized system maintains referential integrity during data migration and optionally masking. The system allows the user to identify one or more flat file(s) as the data source as well as identify the data destination file(s). The system automatically identifies the referential integrity columns where column names match in different flat files, automatically identifies referential integrity by analyzing related application source code for embedded business rules that indicate referential integrity, or can allow the user to describe the referential integrity pertaining to the data source to establish user-defined referential integrity, which referential integrity definition(s) are stored in a data store (e.g., an XML File) accessible via a configuration engine. The system, through a sequence engine and subsequently an execution engine, uses the stored referential integrity and other information to migrate and optionally masks the data from the data source file(s) into the data destination file(s).

Abstract: Implementations can include actions of, prior to executing a transport between a first and a second database system, receiving a set of records, and, for a first record: identifying a first table of the first database system that the first record is stored in, and determining that the first table is associated with a set of foreign key constraints (FKCs), and, for each FKC: determining that a referenced record exists based on a FKC, the FKC relating the first record in the first table to the referenced record in a second table, and selectively adding the referenced record to a list of the transport to maintain validity of the FKC within the second database system after execution of the transport, and providing the transport including the list, the transport being executable in the second database system to one or more of add records and delete records.

Abstract: Notice of migration of a portion of a data volume from a first location to a second location is received by a first computer system from a second computer system, where the data volume is separated over a network from the first computer system. A third computer system, separated over a network from the first computer system, is caused to invalidate a mapping between the portion and the first location. An indication that the third computer system seeks access to the portion is identified. A third computer system is enabled, by providing a mapping between the portion and the second location, to access portion at the second location.

Abstract: Various methods are provided for facilitating heterogeneous database migration. One example method may comprise accessing a migration configuration file, the migration configuration file comprising information indicative of at least a source database type of a source database, connection information of accessing the source database, a destination database type of a destination database, and connection information for accessing the destination database, generating configuration data based on the source database type and the destination database type to generate a mapping of a source database table stored within the source database to a destination database table stored within the destination database, and generating a query for execution on the source database enabling data migration from the source database to the destination database.

Abstract: Data-aware orchestration with respect to a distributed system platform enables at least lifting and shifting of pre-existing applications and associated data without developer action. A volume of a local store is created automatically in response to a container comprising a user application that is non-native with respect to the distributed system platform. The volume is then exposed to the container for use by the application to save and retrieve data. The container and local store are co-located on a compute node providing at least high availability. The application and local store can be duplicated on one or more replicas providing reliability in case of a failure. Further, partitions can be created automatically in response to declarative specification.

Abstract: Systems and methods for creating local, or on-premises, secondary copies of data managed and/or stored in online repositories are described. In some embodiments, the systems and methods perform a single application programming interface (API) call to a web application level of an online repository to transfer a copy of the data stored in the online repository from the online repository to a local site of a local information management system. Via the local site, the systems and methods access the copy of the data at the site of the local information management system, generate a metadata manifest file that associates metadata files and data files within the copy of the data of the site of the local information management system, and transfer the data files and the metadata manifest file to a media agent for storage to a secondary storage device of the local information management system.

Abstract: Various methods, apparatuses, and media for processing feed data are provided. The methodology includes operations of receiving a data file, receiving a configuration file that includes configuration instructions, extracting the configurations from the configuration file, generating a customized set of feed processing instructions by combining the configuration instructions with a standard framework set of instructions, and processing the data file by executing the customized set of instructions.

Abstract: One embodiment described herein provides a system for managing metadata for a shingled magnetic recording (SMR) drive. During operation, the system stores a metadata file in a memory of a host of the SMR drive; subsequent to the SMR drive performing a write operation, the system generates a metadata update, and sends the generated metadata update to a buffer associated with the SMR drive and the memory of the host. In response to a compaction condition being met, the system launches, in the memory of the host, a metadata compaction operation to generate a compacted metadata file based on the previously stored metadata file and the metadata update, and sends the compacted metadata file to the SMR drive.

Abstract: Input information comprising an identifier of a production instance is received. The input information indicating a given time a live database from the production instance is to be restored to in a temporary copy of the production instance. Based at least on the input information, backup data associated with the live database from production instance is identified. Based on the backup data, it is determined whether resource capacity is available for restoring the backup data to the temporary copy of the production instance. In response to determining the resource capacity is available, the temporary copy of the production instance is generated. The backup data is restored to the temporary copy of the production instance to represent a state of the live database from the production instance at the given time.

Abstract: A computer-implemented method according to one embodiment includes suspending a parent/control thread of a data storage system, and receiving a plurality of read requests while the parent/control thread is suspended, each read request having storage information associated therewith. The computer-implemented method further includes resuming the parent/control thread, analyzing the read requests, aggregating read requests requesting common data objects into a common read operation, and dispatching the common read operation to a multi-threaded I/O layer of the data storage system for retrieving data associated with the read requests. The analyzing includes sorting the read requests using the associated storage information.

Abstract: An interface between an existing local file system and a data store generates and exports to the data store a versioned file system. The state of the local file system at a given point in time can be determined using the versioned file system. In operation, the interface creates and exports to the data store structured data representations, which correspond to versions of the local file system, as well as actual file system data that these structured data representations represent. A cache associated with the interface stores recently used data and metadata, as well as all write data and metadata waiting to be transferred to the data store. Prior to transfer, one or more data transformations may be applied to the data and metadata. In one embodiment, the data store comprises one or more cloud storage service providers. A content control system is used to configure and manage the interface.

Abstract: Techniques and systems for restoring objects from a backup file without restoring a remainder of the backup file are described. For example, a plurality of object identifiers that identify a plurality of objects stored in the backup file may be determined. A selection of an object identifier of the plurality of object identifiers may be received. A set of objects to be restored from the backup file may be determined based on the object identifier. The set of objects may be granularly restored to a staging database directly from the backup file, without restoring a remainder of the backup file. The set of objects may be migrated from the staging database to a production database.

Abstract: A method and system for restoring a database are described. An identification of a restoration point of the database is received. Using a processor, metadata of a plurality of backups are analyzed to identify from the plurality of backups a reduced dataset required to restore the database to the restoration point. The reduced dataset is provided for use in restoring the database to the restoration point.

Abstract: Techniques for performing data compression in which host application data access patterns are used to determine a compression block size, which is the size of the blocks of data to which compression is applied by a data storage system. A compression block size may be set to the size of the typical data access performed by a host application on the storage data object. The performance resulting from using multiple compression block sizes may be calculated using a detected data access pattern, and the compression block size set to the size of the typical data access pattern performed by the host application in response to the performance resulting from using a compression block size equal to the typical data access performed by the host application on the storage data object exceeding the performance resulting from using the other compression block sizes.

Abstract: Migrating a logical partition with a native logical port including establishing in the target computing system a target VIOS that includes a virtual network interface controller (vNIC) server, the vNIC server of the target VIOS coupled for data communications to a first target virtual adapter; copying the logical partition including a vNIC client to the target computing system; starting the logical partition; establishing, by the vNIC client of the logical partition, data communications with the vNIC server of the target VIOS, including performing I/O data communications between the logical partition and the first target virtual adapter; establishing a second logical port in the logical partition on the target computing system, including coupling for I/O data communications the second logical port to a second target virtual adapter; and performing I/O data communications from the logical partition to the second target virtual adapter through the second logical port.

Abstract: According to embodiments of the present invention, a metadata file is transferred from the first system to the second system and a database on the second system is initialized based on the metadata file. An image, including information of the first system to be restored, is transferred from the first system to the second system, and restoration of the information to the second system based on the image is initiated. Prior to completion of the restoration, one or more log files indicating actions performed on the first system relating to the information to be restored is transferred from the first system to the initialized database on the second system. In response to completion of the restoration, the actions of the log files are performed to synchronize the restored data on the second system with the first system.

Abstract: A display method and an electronic device are provided. The method includes: displaying a display interface including at least one object; obtaining progress information of at least one first object of the at least one object, where the progress information indicates a content position of the at least one first object that was last output; and displaying the progress information of the at least one first object in the display interface.

Abstract: Embodiments of the present invention provide a system and method for synchronizing data to update backup files. In one embodiment, data associated with files to be synchronized is sent to a second computer system by a first computers system. The second computer system matches data associated with the files to be synchronized to a database, and the first computer system determines differences between an old and new version of the files to be synchronized and creates a backup of the files. The backup of the files is stored in a storage device.

Abstract: A file on file storage is archived as an object on object storage. In this case, a correspondence between UUID which is an identifier of the object and a path or an inode number which is an identifier of the file is recorded. This is referred to as correlation between the file and the object. However, because of changing of the path due to the renaming of the file, or changing of the inode number due to overwriting of the file, the correlation is likely to be lost. The invention provides a technique that restores the lost correlation and causes the correlation between the file and the object to be maintained.

Abstract: Embodiments of the present invention provide a system and method for synchronizing data to update backup files. In one embodiment, data associated with files to be synchronized is sent to a second computer system by a first computers system. The second computer system matches data associated with the files to be synchronized to a database, and the first computer system determines differences between an old and new version of the files to be synchronized and creates a backup of the files. The backup of the files is stored in a storage device.

Abstract: A method, framework, and computer program product are provided in order to migrate data files associated with a source enterprise application to a target enterprise application. A migration utility framework including processing circuitry may be configured to: generate a migration map to map a plurality of data files from a source enterprise application to a target enterprise application; validate the migration map, where the processing circuitry to validate the migration map includes processing circuitry to determine if target enterprise application requirements are met for both file types of the plurality of data files and metadata of the plurality of data files; generate a hash value of a validated map in response to validating the map, where the hash value represents only the validated map; and migrate the plurality of data files from the source enterprise application to the target enterprise application according to the validated map.

Abstract: In an aspect of the disclosure, a method, a computer-readable medium, and a computer system are provided. The computer system may include a first embedded-system device and a second embedded-system device. The first embedded-system device receives a first message instructing the first embedded-system device to make configurations of the first embedded-system device available at a location in a network. The first embedded-system device makes the configurations available at the location. The second embedded-system device obtains a subset of the configurations made available at the location. The second embedded-system device restores itself with the subset of the configurations.

Abstract: Example implementations are directed to restoration of data not only from the servers, but also from the clients connected to the server. Algorithms are incorporated to identify content that was created or modified after the last backup. This algorithm also identifies and resolves changes in the mount points for shared folders, preventing information leakage. When the server recovers from a failure, it notifies the clients about the recovery on their next connection. Each client then determines the current state of its mount points and file paths and compares them with the server's mount points and file paths. After the comparison, the client comprehends and indicates the mount point differences by renaming them and sends entire local data (all files, folders, mount points) to the server. The server reconciles the differences.