Abstract: A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative.

Abstract: Intercepting a requested memory operation corresponding to a conventional memory is disclosed. The requested memory operation is translated to be applied to a structured memory.

Abstract: Stubbing systems and methods are provided for intelligent data management in a replication environment, such as by reducing the space occupied by replication data on a destination system. In certain examples, stub files or like objects replace migrated, de-duplicated or otherwise copied data that has been moved from the destination system to secondary storage. Access is further provided to the replication data in a manner that is transparent to the user and/or without substantially impacting the base replication process. In order to distinguish stub files representing migrated replication data from replicated stub files, priority tags or like identifiers can be used. Thus, when accessing a stub file on the destination system, such as to modify replication data or perform a restore process, the tagged stub files can be used to recall archived data prior to performing the requested operation so that an accurate copy of the source data is generated.

Abstract: A database durability implementation records only committed transactions in a log file. A pair of log files and a pair of snapshot files are maintained. When a snapshot of the database is completed, the ‘current’ log becomes the ‘prior’ log and the other log becomes the ‘current’ log. After the next snapshot is completed, the prior log and prior snapshot may be deleted. Transactions that are not committed are not recorded in the current log, thereby avoiding the need to undo aborted transactions. If a given change is reflected in a completed snapshot, it does not appear in either of the logs; if the change is not yet reflected in a completed snapshot, it is guaranteed to be stored in one of the logs. During recovery, the system assesses both snapshots. The most recent of the completed snapshots is used, and the corresponding log(s) is (are) applied.

Abstract: A backup image generator can create a primary image and periodic delta images of all or part of a primary server. The images can be sent to a network attached storage device and one or more remote storage servers. In the event of a failure of the primary server, an updated primary image may be used to provide an up-to-date version of the primary system at a backup or other system. As a result, the primary data storage may be timely backed-up, recovered and restored with the possibility of providing server and business continuity in the event of a failure.

Abstract: A method of and system for enhanced storage allows more data to be backed up than would otherwise be possible. Instead of storing uncompressed base images and incremental images, differentials of non-current base images are compressed and stored. Furthermore, incremental images that are older than the current base image are removed. By only saving differential base images that are compressed, aside from the newest base image, and deleting older incremental images, a significant amount of space is saved. A removable drive is used as temporary storage in the process of generating a compressed differential base for previous base images. Additionally, a process ensures that previous base images are differentials of the most recent base image and not each other.

Abstract: A backup image generator can create a primary image and periodic delta images of all or part of a primary server. The images can be sent to a network attached storage device and one or more remote storage servers. In the event of a failure of the primary server, an updated primary image may be used to provide an up-to-date version of the primary system at a backup or other system. As a result, the primary data storage may be timely backed-up, recovered and restored with the possibility of providing server and business continuity in the event of a failure.

Abstract: A method and system for merging files of multiple volumes in a data store to a single merged volume. The method includes creating one or more snapshots of one or more volumes of a data store of a first system. Files in the one or more snapshots are merged into a merged volume. The merged volume is mounted and stored in a second system.

Abstract: Simulation control techniques include shutting down peer processes and user code modules, storing an image of a simulation as a checkpoint after the peer processes and user code modules are shutdown, and re-starting user code modules and peer processes after storing an image of the simulation. The resulting checkpoint and processes can be used for restoring from a checkpoint or restarting a new simulation environments having peer processes such as debuggers coupled to the simulation.

Abstract: Management of a file hierarchy for a clustered file system can be distributed across nodes of the cluster. A cluster file hierarchy is accessed to determine location of a file in response to a request to write to a file. A first node maintains the cluster file hierarchy. It is determined that management of a fileset object, which represents a fileset that includes the file, has been delegated to a second node based, at least in part, on said accessing the cluster file hierarchy. A node file hierarchy maintained by the second node is accessed responsive to determining the delegation. The cluster file hierarchy represents filesets of the clustered file system and the node hierarchy represents a subset of one or more of the filesets. Location of the file is determined based, at least in part, on said accessing the node file hierarchy.

Abstract: A system and method provide for a reception of data at a computer processor. The data relates to a dataset in a computer system. The computer processor calculates a weight for the dataset as a function of the data, and the processor executes an action on the dataset as a function of the weight. In an embodiment, the action is a backup of data on the computer system, and through recalculation of the weight over a period of time, the backup schedule, backup media, and other parameters are altered based on the changing weight for a dataset.

Abstract: A method for recording a sequence of events is provided. The method includes operating a sequence of events recorder in a normal mode, wherein data stored is related to the sequence of events in a history buffer. The method also includes initiating a snap-shot mode of the events recorder after a triggering event occurs in the sequence of events. The snap-shot mode operates by freezing data related to a moment in the sequence of events that occurred prior to the triggering event, storing data related to the sequence of events at the time of the triggering event in the snap-shot buffer, and continuing to record the data related to the sequence of events to a snap-shot buffer until a predetermined event.

Abstract: An approach to providing failure protection in a loosely-coupled cluster environment. A node in the cluster generates checkpoints of application data in a consistent state for an application that is running on a first node in the cluster. The node sends the checkpoint to one or more of the other nodes in the cluster. The node may also generate log entries of changes in the application data that occur between checkpoints of the application data. The node may send the log entries to other nodes in the cluster. The node may similarly receive external checkpoints and external log entries from other nodes in the cluster. In response to a node failure, the node may start an application on the failed node and recover the application using the external checkpoints and external log entries for the application.

Abstract: Methods, program products, and systems for checkpoint based progressive backup are described. When a system receives a request to update a page of a storage device storing database files of a database, the system can update the page and replicate the updated page in a shadow page in a backup queue. The backup queue can store multiple shadow pages, where each updated page can correspond to at most a specified number of shadow pages in the queue. Each shadow page can be associated with a timestamp of a latest update. At pre-specified temporal checkpoints, the system can write the shadow pages in the queue to a backup file in the order of the timestamps. Upon receiving a restoration request, the system can restore the database to a state as of the time of the checkpoint using the backup file.

Abstract: A system and method for providing a substantially constant-time copy operation for file system objects managed by a network storage server begins by generating a new file based on metadata in a source file. The system then generates a snapshot of the source file or the logical volume in which the source file resides. The system then copies each of the indirect blocks of the source file to a corresponding location in the destination file. During the copy process, a modified set of file system operations can be executed on the destination metadata container. In response to a read request directed to a target block in the destination file, the system determines if target block has been copied. If the block has not been copied, the system provides a data segment from the corresponding data block in the snapshot. Write requests are processed by generating a new data block and adding a reference to the new data block to the target location in the destination metadata container.

Abstract: When updating the data in each generation's logical units, the snapshot processing unit writes the update data in accordance with the update as forward differential data 221 to the base volume, and saves the old data that existed in the base volume before that update data was written as backward differential data in the backward differential data pool, and, when each generation's logical unit backward differential data is updated, deletes the forward differential data belonging the production LUs and the snapshots that together with those production LUs form the forward differential group. As a result of this, the amount of metadata necessary for executing a host command is able to be reduced in production LUs utilizing snapshots using the forward differential method.

Abstract: Systems and methods provide for the selective backup and rollback of software, firmware and data components of a wagering game machine.

Abstract: In one aspect, a method includes forming a virtualized grid consistency group to replicate logical units, running a first grid copy on a first data protection appliance (DPA), running a second grid copy on a second DPA, splitting to the first DPA IOs intended for a first subset of the logical units and splitting to the second DPA IOs intended for a second subset of the logical units different from the first subset of logical units.

Abstract: A point-in-time backup image is selected from a plurality of backup images of an image on a source computer system to be applied to the target computer system. A first assessment value is associated with an extent to which critical files and recovery metadata are included in the selected backup based on an include list of critical files and recovery metadata to include in the backup. A second assessment value comprises a backup status of the critical files and the recovery metadata. A third assessment value is indicative of an extent to which the selected backup satisfies requirements of a retention policy. A fourth assessment value is indicative of an extent to which computational resources and device drivers in the target computer system are compatible. An overall assessment value for the selected backup image is determined based on the determined first, second, third, and fourth assessment values.

Abstract: A system and method for avoiding duplicate backups of data in a volume backup image. A cluster of nodes is coupled to a data storage medium configured to store data corresponding to a shared volume. A node receives a request for the backup of the shared volume. In response to this request, the node queries all other nodes in the cluster for identification of a subset of the shared volume data that should be excluded from the backup. The identified subset of the data may correspond to at least a file under control of a database application or other particular application. It may be known that this identified subset of the data will be backed up by a subsequent agent-based backup operation after the volume backup. In response to receiving all query responses, the node initiates a backup corresponding to the data in the shared volume excluding the identified subset of the data.

Abstract: A system and method for generating a snapshot of data associated with one or more cloud-based applications are disclosed. Application programming interfaces (APIs) and connections associated with one or more applications registered and on a server computer and used by a company are retrieved from a table by a lookup. All data associated with the one or more applications based on the APIs and connections are also retrieved. The data associated with the one or more applications is then mapped to a client-specific representation and data format. The data associated with the one or more applications is converted to the client-specific representation and data format.

Abstract: A method performed in a computer-based storage system includes creating a copy of an active file system at a first point in time, where the active file system includes user data, metadata describing a structure of the active file system and the user data, and a first data structure describing storage locations of the user data and the metadata, in which creating a copy of the active file system includes selectively omitting a portion of the user data and a portion of the metadata from the copy.

Abstract: A method for transmitting records of changes to data from a production location to a storage location is provided. The method stores in a log, records of changes to data stored at a production location. Those records are transmitted and a transmitted records checkpoint is generated that is transmitted at the end of the transmitted records. A records checkpoint confirmation is received and the plurality of transmitted records are purged from the log.

Abstract: Systems and methods for coordinating sync points between a non-volatile memory (“NVM”) and a file system are provided. In some embodiments, a file system can issue one or more commands to control circuitry of a NVM, which can indicate whether a transaction is journaled or non-journaled. This way, the control circuitry can maintain a list of journaled transactions and corresponding LBA(s). By keeping track of journaled transactions, the control circuitry can ensure that sync points are not prematurely erased during a garbage collection process. In addition, upon detecting device failure events, the control circuitry can roll back to sync points corresponding to one or more journaled transactions.

Abstract: A method for providing rolling continuous data protection of source data is disclosed. In one embodiment, such a method includes enabling a user to select source data and establish a first interval when point-in-time copies of the source data are generated. The method further enables the user to specify a first number of point-in-time copies to retain at the first interval. The method further enables the user to specify a second number of point-in-time copies to retain at a second interval, wherein the second interval is a (n?2) multiple of the first interval. The method further enables the user to specify a third number of point-in-time copies to retain at a third interval, wherein the third interval is a (n?2) multiple of the second interval. A corresponding apparatus and computer program product are also disclosed.

Abstract: Data written in the primary logical volume of the first storage device are transmitted to the third storage device via the second storage device, the data being written in the same location as the primary logical volume within the secondary logical volume in the third storage device; when transmission of the data stops among the first to the third storage devices, the respective second storage device and the third storage device manage locations in the secondary logical volume where the data held thereby are to be written; and, when transmission of the data resumes among the first to the third storage devices, the locations in the secondary logical volume managed by the respective second and the third storage devices are aggregated, the data to be written in the respective aggregated location in the secondary logical volume being transmitted from the first storage device to the third storage device via the second storage device.

Abstract: A method for a database instance associated with a database management system includes receiving a command to perform a copy or a move on a first tenant partition from a first database instance to a second database instance destination partition. The method shuts down the first tenant partition, packs tenant-dependent data into tenant-dependent tables, acquires a data definition lock that prevents changes to metadata describing the first tenant partition, obtains tenant-specific metadata of a catalog of the first database instance, packs the first database instance catalog tenant-specific metadata into the first tenant partition, locks write transactions on tenant-specific data in the first tenant partition, creates a tenant-specific snapshot of the first tenant partition, stores the tenant-specific snapshot in a storage device external to the first database instance, performs the received command, and releases both the write transaction lock and the data definition lock.

Abstract: A system for storing data comprises a performance storage unit and a performance segment storage unit. The system further comprises a determiner. The determiner determines whether a requested data is stored in the performance storage unit. The determiner determines whether the requested data is stored in the performance segment storage unit in the event that the requested data is not stored in the performance storage unit.

Abstract: The invention relates to computer readable medium storing program code which when executed on a computer causes the computer to perform a method for creating a quick recovery volume of a primary data set used by a first computer in a backup storage system, which includes identifying a snapshot image of the primary data set generated by a snapshot application, creating the quick recovery volume of the primary data set from the snapshot image of the primary data set and controlling transfer of data from the first computer to an archival storage unit. In one embodiment, the invention provides a method for creating a quick recovery volume of a primary data set that includes creating a snapshot image of the primary data set and creating a quick recovery volume of the primary data set from the snapshot image of the primary data set.

Abstract: A system and method is provided for facilitating data collection from storage devices. A generic low level module may be provided that can handle data collection for devices that store data according to particular variants of a storage standard such as SMI-S storage standard, SNMP protocol, and/or other storage standard.

Abstract: Containers that store data objects that were written to those containers during a particular backup are accessed. Then, a subset of the containers is identified; the containers in the subset have less than a threshold number of data objects associated with the particular backup. Data objects that are in containers in that subset and that are associated with the backup are copied to one or more other containers. Those other containers are subsequently used to restore data objects associated with the backup.

Abstract: According to embodiments described herein, a backup server maintains backup data for a set of data, which includes data for a first block and a second block. Backup data for the first and second block include backup data for a plurality of versions of the first and second block. A distinct watermark is stored for each version of the first block and each version of the second block. In response to a request to perform a restoration operation on the set of data, a particular version of the first block and a particular version of the second block are selected to use in the restoration operation by comparing a restoration target with the watermarks of the version of the first block and second block. The selected version of the first block has a different watermark than the selected version of the second block.

Abstract: Techniques are described herein for capturing and restoring database session state. Production database server components save the session state of each of a plurality of database sessions. The components store workload units that are processed in these sessions. The components store updated session states in response to certain events. Thus, the components may capture multiple session states, pertaining to various different points in time, for each session. The captured session states and the captured workload are moved to a test database server. A user selects, from among the time points represented by the session states, a point in time at which the user would like workload replay to begin. Sessions are re-created on the test database server. Session states of these sessions are set to reflect the session states as they existed at the user-selected time point. Workload units are replayed in the sessions relative to the test database server.

Abstract: A system and method of managing stored data in a storage management system. The storage management system includes a storage manager, a media agent connected to the storage manager, and a primary volume connected to the media agent. Multiple snapshots are taken of the primary volume. The snapshots are indexed by associating respective information with the snapshot. The indexed snapshots are copied to a recovery volume. In this way, browsing features are enabled for the user. The user may view the snapshots in a hierarchical format, and may even view snapshot data in association with the corresponding application. The resultant recovery volume may be used to replace a primary volume.

Abstract: One embodiment of the present invention is directed to a multi-node data-storage system comprising a number C of component-data-storage-system nodes that store data pages of a data object in a mirror and in 0, 1, or more parity-encoded snapshots, the mirror comprising 2 or more replicates including a 0th replicate and each parity-encoded snapshot containing 1 or more stripes, each stripe including snapshot data pages and snapshot parity pages.

Abstract: System, method, computer program product embodiments and combinations and sub-combinations thereof for backing up an in-memory database. In an embodiment, a backup server is provided to perform backup operations of a database on behalf of a database server. A determination is made as to whether the database is an in-memory database. Database server connections are utilized during data accesses for the backup operations when the database is an in-memory database.

Abstract: Embodiments of the present invention provide a method and system, in a network storage system, for efficiently migrating a storage object (vdisk) from a first storage server (source) to a second storage server (destination) using data of a related vdisk at the destination. A related vdisk includes an earlier created vdisk (parent) from which the vdisk to be migrated (child) is generated (cloned). By virtue of the cloned relationship, the parent and child have a portion of data blocks in common. When a parent is available at the destination, only the changed data blocks between the parent and child need to be migrated for efficiently constructing the child at the destination.

Abstract: Embodiments include a checkpointing fault tolerance network architecture enables a first computer system to be remotely located from a second computer system. An intermediary computer system is situated between the first computer system and the second computer system to manage the transmission of checkpoint information from the first computer system to the second computer system in an efficient manner. The intermediary computer system responds to requests from the second computer system for updated data corresponding to memory pages selected by the second computer system, or memory pages identified through application of policy information defined by the second computer system.

Abstract: Methods and apparatus for point-in-time volumes are provided. A relationship is enabled between a source volume and point-in-time volume. Copying a data chunk to the point-in-time volume before a write operation modifies the data chunk on the source volume dynamically creates the point-in-time volume. The point-in-time volume can be accessed in read/write mode as a general purpose data storage volume. Other embodiments comprising additional features, such as a forced migration process, are also provided.

Abstract: In order for a conventional information search system to realize online updating of search indices, there would have to be provided two systems of physical storages for storing copies of indices, namely one for searching and another for updating. By means of a snapshot function provided by an OS, duplicates of original indices are created. A search engine is attached to those duplicates and is used as such, while an index update process is applied to the original index data.

Abstract: Methods and systems for database migration from a multitenant database include taking a snapshot of an original database to be migrated with a hot backup process, such that the database is still capable of answering queries during the hot backup process; maintaining a query log of all queries to the tenant database after the hot backup process begins; initializing a new database at a target server using the snapshot; replaying the query log synchronize the new database with the original database; and answering new queries with the new database and not the original database.

Abstract: A system, a method and a computer readable medium for storing data elements and related data provenance information. The data elements may be represented in a hyper-table having rows and columns which may be indexed. The data-values of the corresponding data-elements in the hyper-cells may be retrieved based on the indices. Snapshots of the indices may be generated at pre-determined time periods. Checkpoints of the hyper-table may be generated at time periods that are based on transactions on the hyper-table. The hyper-table is capable of being queried as the hyper-table existed at certain time-periods, and data-values of the data-elements may be retrieved as the data-elements existed at such time-periods.

Abstract: A system for storing encrypted data comprises a processor and a memory. The processor is configured to receive an encrypted segment. The encrypted segment is determined by breaking a data stream, a data block, or a data file into one or more segments and encrypting each of the one or more segments. The processor is further configured to determine whether the encrypted segment has been previously stored, and in the event that the encrypted segment has not been previously stored, store the encrypted segment. The memory is coupled to the processor and configured to provide the processor with instructions.

Abstract: A method, computer readable medium, and a system for reconstituting a virtual snapshot of files in a file virtualization system includes forming at a file virtualization device a virtual snapshot that includes a plurality of physical snapshots associated with one or more file storage devices participating in the virtual snapshot, receiving a request for performing an operation on one or more physical snapshots in the plurality of physical snapshots, providing the one or more physical snapshots in response to the request for performing the operation when the one or more physical snapshots exists in the virtual snapshot, and reconstituting the virtual snapshot by including the one or more physical snapshots to form a reconstituted virtual snapshot in response to the request for performing the operation when the one or more physical snapshots do not exist in the virtual snapshot.

Abstract: The number of machines in a cluster of computers running a distributed database, such as a scalable hyperlink datastore or a distributed hyperlink database, may be changed such that machines may be added or removed. The data is not repartitioned all at once. Instead, only new and merged data stores are mapped to the changed set of machines. A database update mechanism may be leveraged to change the number of machines in a distributed database.

Abstract: Systems and methods for reduced-overhead creation of persistent, point-in-time images (PPIs) are disclosed. The summary map is updated as needed when a block is newly freed or allocated after the latest PPI is taken. Therefore, PPI maps of previously created PPIs do not need to be scanned after PPI creation, thereby eliminating high latency disk reads and memory consumption for scanning. When a PPI is created, the active map and the latest PPI map are identical since the active map depicts the current allocation status of the blocks in the active file system. The active map only diverges from the PPI map when a block is allocated or freed in the active file system. Therefore, the active map can be used to update the status of blocks in the summary map when the status of a block diverges from its status as indicated in the latest PPI map.

Abstract: The subject disclosure is directed towards verifying a data recovery component of a volume snapshot service using a managed interface. The managed interface enables interoperability between the data recovery component and one or more complementary data recovery components by converting compatible instructions for the data recovery component and a complementary data recovery component into native data recovery operations for the volume snapshot service and vice versa. Via the managed interface, the complementary data recovery component emulates the native data recovery operations. Using status information associated with such an emulation, the data recovery component is verifiable.

Abstract: A storage system for storage of data written from a computer, and when a write request of data to a first logical volume is received, the data on request is stored into the first logical volume. When a first-generation snapshot creation request is received, the data stored in the first logical volume at the time of receiving the first-generation snapshot creation request is written into a pool region as data corresponding to a first-generation snapshot, and when a second-generation snapshot creation request is received, any portion of the data updated after the first-generation snapshot creation request is received but before the second-generation snapshot creation request is issued is read from the first logical volume for writing into the pool region. Such a storage system favorably implements snapshot backup with no dependency with a positive volume in terms of performance and failure, and with high capacity efficiency.

Abstract: A system includes a database instance having a data storage system with a data store area storing first and second data partitions, where the respective data partitions each include a plurality of database pages storing respective tenant-independent/-specific data and respective first/second converters associated with the respective partitions. A database management system (DBMS) to receive a request for a database object and determine whether the database object is associated with tenant-independent data or with tenant-specific data. If the database object is associated with tenant-independent data, the DBMS determines a location of first database pages associated with the database object within the first plurality of database pages based on the first converter. Or if associated with tenant-specific data, the DBMS determines a location of second database pages associated with the database object within the second plurality of database pages based on the second converter. A method is also disclosed.

Abstract: Techniques for migrating persistent data of virtual machines between and across data stores are optimized using special tracking data structures and monitoring methods. Special tracking data structures include an incremental change block tracking bitmap that indicate what blocks have been modified during a copy operation. The determination of whether any one block has been modified during the copy operation is based on whether or not the copy operation has progressed past that block. Another special tracking data structure is a Bloom filter, which provides a space-efficient data structure for keeping track of dirtied blocks. In addition, heat-based optimization techniques are applied so that blocks that are frequently updated are filtered and not transferred to the destination data store until the last iteration of the migration process.