Abstract: A virtualization platform provides fault tolerance for a primary virtual machine by continuously transmitting checkpoint information of the primary virtual machine to a collector process, such as a backup virtual machine. When implemented on a hardware platform comprising a multi-processor that supports nested page tables, the virtualization platform leverages the nested page table support to quickly identify memory pages that have been modified between checkpoints. The backup virtual machine provides feedback information to assist the virtualization platform in identifying candidate memory pages for transmitting actual modifications to the memory pages rather than the entire memory page as part of the checkpoint information. The virtualization platform further maintains a modification history data structure to identify memory pages that can be transmitted simultaneous with the execution of the primary virtual machine rather than while the primary virtual machine has been stunned.

Abstract: In accordance with a first aspect of the present invention, an edge node is provided with the storage destination management information that is corresponded to the edge node. The storage destination management information includes the information that indicates a storage destination for a core node of a file that has been written to a file storage region (an edge storage region) for an edge node that is corresponded to the information and includes the information that indicates a recall date that is a date that has been read by the edge node. The edge node judges whether or not there is an old file (a file before an update) in an edge storage region for the edge node based on the storage destination management information that is corresponded to the edge node and the storage destination information that is corresponded to another edge node, and create a stub for only an old file without creating a stub for a file after an update (a latest file).

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: Embodiments include a computer program product and an apparatus for cloning files across different filesets and maintaining the clone files. After a clone file is created from a file, a write request targeting the clone file can be handled. It is determined that the write request indicates the clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. It is then determined that the data block at a current location cannot be modified. The write request is implemented with respect to the data block at a different location. It is indicated that the data block at the different location can be modified for subsequent write requests that indicate the clone file.

Abstract: File system backups are performed by copying information describing changes in the file system since a previous point in time. To restore data, a virtual restored file system (VRFS) structure is created corresponding to a snapshot of data copied from the file system that is stored in the backup file system. A client can read the data stored in the backup file system pointed at by the VRFS structure as well as write to the backup file system. Multiple clients can share blocks of data stored on the backup file system via the same VRFS structure or via multiple VRFS structures. If a client writes to a data block pointed at by a VRFS, a copy of the data block is made to which the client makes changes so that the data in the original data blocks is saved for other clients.

Abstract: Various technologies and techniques are disclosed for extracting data from databases of content management applications. Input is received from a user to connect to a database of a content management application. A connection is established to the database. When the database is not part of a current live instance of the content management application, an emulation is performed so that the database is treated like it is actually attached to the current live instance of the content management application. The user is able to browse the database. Unattached databases of a content management application can be managed using one or more commands, such as using an object model or command line. Orphaned databases can be detected and deleted from the content management application.

Abstract: A computer implemented method for cloud bursting applied to a database includes employing a database live migration using a database hot backup capability to support database cloud bursting without client service interruption in multitenant databases, ascertaining a critical time to start/redo the database cloud bursting to a public cloud so as to meet a service level agreement SLA while leveraging a private cloud for the database to a maximum level, and determining tenants of the database to burst into the public cloud to responsive to costs and benefits.

Abstract: The disclosed embodiments disclose techniques for executing a cloud command for a distributed filesystem. Two or more cloud controllers collectively manage distributed filesystem data that is stored in one or more cloud storage systems; the cloud controllers ensure data consistency for the stored data, and each cloud controller caches portions of the distributed filesystem. During operation, a cloud controller presents a distributed-filesystem-specific capability to a client system as a file in the distributed filesystem (e.g., using a file abstraction). Upon receiving a request from the client system to access and/or operate upon this file, the client controller executes an associated cloud command. More specifically, the cloud controller initiates a specially-defined operation that accesses additional functionality for the distributed filesystem that exceeds the scope of individual reads and writes to a typical data file.

Abstract: A method and apparatus for providing a volume image backup of selected objects is provided. In one embodiment, a method for creating volume image backups using selected objects of a source volume, comprises processing metadata and mapping information regarding at least one object of a source volume, wherein the mapping information is used to identify at least one data block within the source volume for the at least one object, wherein the at least one object is selected from a plurality of objects configuring a file system hierarchy of at least one image file using the metadata and storing the at least one data block in the at least one image file using the mapping information.

Abstract: Techniques for providing a differential backup from a storage image are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for providing a differential backup from a storage image comprising identifying one or more dirty blocks in a storage image, creating a differential backup data structure, and transmitting the one or more dirty blocks to a data management process utilizing the differential backup data structure to provide a differential backup.

Abstract: Improving file system reliability in storage mediums after a data corrupting event using file system journaling is described. In one embodiment, a method, which includes scanning beyond an active transactions region within the file system journal to locate additional valid transactions for replay to bring the storage medium into a consistent state; the scanning performed until an invalid transaction is reached.

Abstract: A computer system issues a batch read operation to a tablet in a first replication group in a distributed database and obtains a most recent version of data items in the tablet that have a timestamp no great than a snapshot timestamp T. For each data item in the one tablet, the computer system determines whether the data item has a move-in timestamp less than or equal to the snapshot timestamp T, which is less than a move-out timestamp, and whether the data item has a creation timestamp less than the snapshot timestamp T, which is less than or equal to a deletion timestamp.

Abstract: Systems and methods are provided for backing up out-of-band storage. A protection policy is activated for out-of-band storage at a remote host, wherein the out-of-band storage is not physically accessible by the computing device, such that the out-of-band storage is not in communication with the remote host through the computing device. A backup request is transmitted to the remote host comprising data indicative of a volume on the out-of-band storage to back up according to the protection policy. A response to the backup request is received comprising staging disk requirements for the volume, the staging disk requirements comprising a required size for a staging disk to back up the volume. A staging disk is determined based on the response. The staging disk is presented to the remote host. A backup result is received comprising data indicative of whether a backup of the volume to the staging disk succeeded.

Abstract: Systems and methods are provided for backing up database storage. A protection policy for database storage is activated at a remote host, wherein the database storage is not physically accessible by the computing device, such that the out-of-band storage is not in communication with the remote host through the computing device. A backup request is transmitted to the remote host comprising data indicative of a volume on the database storage to back up according to the protection policy. A response to the backup request is received comprising staging disk requirements including a required size for a staging disk. A staging disk is determined based on the response. The staging disk is presented to the remote host so that the remote host can perform a backup of the volume to the staging disk using a database backup tool provided by a vendor of the database storage.

Abstract: Searching cached log blocks. A method includes performing a first search on cached log blocks for a log block having a first log block ID. The log blocks are cached and organized into sequentially ordered log buffers in memory. Adjacent sequentially ordered log buffers are double linked to each other. Each log buffer includes a complete range of log blocks from a starting log block ID to an ending log block ID. As part of the first search one or more links are followed, forward and/or backward, to one or more other log buffers. The method may further include determining that the first log block is not found by following one or more links forward and/or backward to one or more other log buffers and as a result, follow one or more covering pointers to one or more log buffers to search for the first log block.

Abstract: Techniques are disclosed for quiescing a file system. One technique comprises freezing a file system, flushing a memory associated with the file system, and thawing the file system. One technique comprises receiving a request targeted to a file system and intercepting the request.

Abstract: Embodiments of the invention include systems and methods for providing writable snapshot functionality for file systems. Pointer-based snapshots can be taken of an active version of the file system resulting in either (1) a read-only snapshot image and a new active version of the file system resulting from a read-only snapshot operation; or (2) a read-only snapshot image and two new active versions of the file system resulting from a writable snapshot operation. The two active file systems generated from writable snapshot operations are each independently and concurrently writable. Various techniques are also presented for handling multiple, concurrently active file systems. For example, novel techniques are described for allowing snapshot restore, compaction, and other functionality to operate in an environment having multiple read-only and writable versions of the file system.

Abstract: Migrating data from an old storage device to a new storage device includes transferring the data from a first logical device on the old storage device to a second logical device on the new storage device, determining replication relationships for the first logical device, transferring the replication relationships; and transferring logical devices used for the replication relationships from the old storage device to the new storage device. The replication relationships may include a clone of the first logical device. Migrating data from an old storage device to a new storage device may also include suspending writes to the first logical storage device prior to transferring the data for the first logical storage device. The replication relationships may include at least one snapshot.

Abstract: A method and systems of a time ordered view of backup data on behalf of a host are disclosed. In an embodiment, a method to provide a time-ordered snapshot view on behalf of a host of a specified portion of a backup of a first storage system data container stored at a second storage system includes initiating an order at the host to obtain a view of a data container. The order specifies a date and time of the ordered view. The method further includes receiving the order at a server adapted to assemble and enable access to the ordered view, and at the server, accessing the second storage system according to the date and time of the ordered view and accessing an applicable data write representing a data change to the data container.

Abstract: In one general aspect, an apparatus can include a completion identifier configured to identify, for completion processing, a large object (LOB) deleted from an auxiliary table within a DB2 database environment based on a space map record associated with the large object where the auxiliary table functions as an auxiliary space to a base table. The apparatus can also include a completion analyzer configured to identify a resource where an image of the large object is stored at a time before the deletion of the large object from the auxiliary table.

Abstract: A distributed system for creating a checkpoint for a plurality of processes running on the distributed system. The distributed system includes a plurality of compute nodes with an operating system executing on each compute node. A checkpoint library resides at the user level on each of the compute nodes, and the checkpoint library is transparent to the operating system residing on the same compute node and to the other compute nodes. Each checkpoint library uses a windowed messaging logging protocol for checkpointing of the distributed system. Processes participating in a distributed computation on the distributed system may be migrated from one compute node to another compute node in the distributed system by re-mapping of hardware addresses using the checkpoint library.

Abstract: A federated configuration management database includes a plurality of management data repositories, and a backup destination determination unit that determines backup destination management data repositories for backing up data overlapping among the plurality of management data repositories at specific management data repositories and that notifies each of the management data repositories of the data to be backed up.

Abstract: Data duplication may be reduced in cloud storage. First snapshots of one or more remote volumes may be received via a network. Responsive to and/or based on the first snapshots, unique clusters and duplicate clusters may be identified among the valid clusters of the remote volumes. The unique clusters and single instances of the duplicate clusters may be stored in a backup file, such that the backup file is devoid of duplicate clusters. Second snapshots of the one or more remote volumes may be received via the network. Responsive to the second snapshots, the clusters in the backup file that are no longer valid may be utilized to store the valid clusters in the one or more remote volumes not yet stored in the backup file.

Abstract: Decreasing disk costs make it possible to take frequent snapshots of past storage system states and retain them for a long duration. Existing snapshot approaches offer no satisfactory solution to long-lived snapshots. Split snapshots are an approach that is promising because it does not disrupt the current state storage system in either the short or the long run. An unsolved problem has been how to maintain an efficient access method for long-lived split snapshots without imposing undesirable overhead on the storage system. Skippy is a new approach that inexpensively indexes long-lived snapshots in parallel with snapshot creation. An embodiment of Skippy uses append-only index data structures to optimize writes while simultaneously providing low-latency snapshot lookup. Performance evaluations of Skippy indicate that this new approach is effective and efficient. It provides close-to-optimal access to long-lived snapshots while incurring a minimal impact on the current-state storage system.

Abstract: A method for migrating extents between extent pools in a tiered storage architecture maintains a data access profile for an extent over a period of time. Using the data access profile, the method generates an extent profile graph that predicts data access rates for the extent into the future. The slope of the extent profile graph is calculated and used to determine whether the extent will reach a migration threshold within a specified “look-ahead” time. If so, the method calculates a migration window that allows the extent to be migrated prior to reaching the migration threshold. In certain embodiments, the method determines the overall performance impact on the source extent pool and destination extent pool during the migration window. If the overall performance impact is below a designated impact threshold, the method migrates the extent during the migration window.

Abstract: A method for migrating extents between extent pools in a tiered storage architecture maintains a data access profile for an extent over a period of time. Using the data access profile, the method generates an extent profile graph that predicts data access rates for the extent into the future. The slope of the extent profile graph is calculated and used to determine whether the extent will reach a migration threshold within a specified “look-ahead” time. If so, the method calculates a migration window that allows the extent to be migrated prior to reaching the migration threshold. In certain embodiments, the method determines the overall performance impact on the source extent pool and destination extent pool during the migration window. If the overall performance impact is below a designated impact threshold, the method migrates the extent during the migration window. A corresponding apparatus and computer program product are also disclosed herein.

Abstract: An information processing device includes a storage unit which stores information, and a processor which performs processes including generating a first snapshot of the information, and storing first pointer information indicating a storage position of the information associated with the first snapshot in the storage unit, monitoring completion of a writing process on the information when the first snapshot is generated during the writing process, generating a second snapshot of the information when the completion of the writing process is detected, and storing, in the storage unit, second pointer information indicating a storage position of the information associated with the second snapshot; and replacing the first pointer information stored in the storage unit with the second pointer information.

Abstract: A digitally signed file system in which data, metadata and files are objects, each object having a globally unique and content-derived fingerprint and wherein object references are mapped by the fingerprints; the file system has a root object comprising a mapping of all object fingerprints in the file system, such that a change to the file system results in a change in the root object, and tracking changes in the root object provides a history of file system activity.

Abstract: A data storage system includes a generic snapshot interface, allowing for integration with a wide variety of snapshot-capable storage devices. The generic interface can be a programming interface (e.g., an application programming interface [API]). Using the snapshot interface, storage device vendors can integrate their particular snapshot technology with the data storage system. For instance, the data storage system can access a shared library of functions (e.g., a dynamically linked library [DLL]) provided by the vendor (or another by appropriate entity) and that complies with the specifications of the common programming interface. And by invoking the appropriate functions in the library, the data storage system implements the snapshot operation on the storage device.

Abstract: A method includes applying a write Input/Output (I/O) queue interval to a Logical Unit (LU) member of a consistency group (CG). The method also includes marking each write I/O with a timestamp and suspending I/O from the participating storage array to the LU member of the CG upon the participating storage array receiving a snapshot request from a master storage array. The method further includes determining whether the snapshot request timestamp is within the write I/O queue interval of the participating storage array.

Abstract: A flashcopy of a source storage volume to a target storage volume is initiated. The content of the source storage volume is stored on the target storage volume in a space efficient manner. The space requirement of the stored content on the target storage volume is monitored. The flashcopy is terminated when the space requirement reaches a predetermined level. The stored content on the target storage volume is copied to a backup storage medium. A new flashcopy of the source storage volume is initiated.

Abstract: A flashcopy of a source storage volume to a target storage volume is initiated. The content of the source storage volume is stored on the target storage volume in a space efficient manner. The space requirement of the stored content on the target storage volume is monitored. The flashcopy is terminated when the space requirement reaches a predetermined level. The stored content on the target storage volume is copied to a backup storage medium. A new flashcopy of the source storage volume is initiated.

Abstract: Techniques for migrating persistent data between and across data stores are implemented using monitoring methods. The method includes classifying frequently updated blocks of persistent data to distinguish those blocks from less frequently updated blocks of persistent data. The less frequently updated blocks are copied from the source data store to the destination data store, such that persistent data is copied to the destination data store in the absence of the persistent data of the frequently updated blocks. The method further includes identifying a modified set of the less frequently updated blocks that are modified during the copying. The modified set of less frequently updated blocks is copied from the source data store to the destination data store, without copying the frequently updated blocks. It is then determined whether to copy the frequently updated blocks of persistent data from the source data store to the destination data store.

Abstract: A mechanism performs a metadata image backup of a hierarchical storage management (HSM) file system. Concurrent with performing the metadata image backup of the HSM file system, the mechanism identifies a set of resident files that are not yet stored off-line in the HSM file system. The mechanism identifies immutable files within the set of resident files to form an optimized set of resident files and passes the optimized set of resident files to a traditional backup system. The traditional backup system backs up file data for the set of resident files. Responsive to detecting an inability to restore a migrated managed state of a file, the mechanism unsets an immutable bit of the file attribute, restores file data for the file using the traditional backup system, and sets the immutable bit attribute of the file.

Abstract: In one embodiment, a system, includes logic for creating a snapshot of first data stored on a source storage system, wherein the snapshot is a logical copy of the first data stored on the source storage system with respect to data content and data structure; logic for copying the snapshot to a target storage system; logic for copying the first data represented by the snapshot from the source storage system to the target storage system; logic for detecting one or more write operations affecting data on the source storage system; logic for detecting one or more collisions affecting the first data on the source storage system, logic for setting a consistency group interval; and logic for altering the consistency group interval to minimise collisions affecting data on the source storage system. Other systems and computer program products for dynamic consistency group formation are also described.

Abstract: Software, firmware, and systems are described herein that migrate functionality of a source physical computing device to a destination virtual machine. A non-production copy of data associated with a source physical computing device is created. A configuration of the source physical computing device is determined. A configuration for a destination virtual machine is determined based at least in part on the configuration of the source physical computing device. The destination virtual machine is provided access to data and metadata associated with the source physical computing device using the non-production copy of data associated with the source physical computing device.

Abstract: A method for dynamic consistency group formation, in one embodiment, includes creating a snapshot of first data stored on a source storage system with respect to data content and data structure, copying the snapshot to a target storage system, detecting one or more write operations affecting data on the source storage system while copying the first data, detecting one or more collisions affecting the first data on the source storage system, wherein a collision occurs whenever the write operations affect the first data prior to the first data being written, setting a consistency group interval which represents an interval duration between successive snapshot create-and-copy events, and altering the consistency group interval to minimize collisions affecting data on at least one of the storage systems. Other methods for dynamic consistency group formation are also described.

Abstract: Techniques for normalizing a database as part of a database restore. Embodiments may receive a database restore request indicating a previous state to restore a database to. Responsive to the request, embodiments may restore the database to the previous state using backup data associated with the previous state, and normalize the restored database using historical database usage data based on one or more previous database operations.

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 data storage environment can include one or more virtual clients instantiated on a host proxy computing device. The virtual clients may have only indirect access to a storage device, and may access the storage device via the proxy computing device. For example, the proxy computing device receives storage operation requests from one of the virtual clients, such as a request to create, mount or revert a snapshot of virtual client data. The proxy computing device generally acts as an intermediary between the virtual clients and the storage device to carry out the snapshots or other storage operations. The proxy computing device may further receive a notification upon completion of the storage operations, and transmits relevant data to the requesting virtual client regarding the storage operation.

Abstract: The present invention relates to a system that includes one or more logical volumes for storing data; a snapshot producing section for producing snapshots for the logical volumes based on a pre-scheduled snapshot acquisition time; a remote copy section for remote copying difference data for the snapshots based on pre-scheduled remote copy start times; and a scheduling section for re-scheduling the time of one or more of an Nth snapshot acquisition time, an remote copy start time, and an (N+1)th remote copy start time, in such a manner that remote copying starting at the Nth remote copy start time finishes by the (N+1)th remote copy start time.

Abstract: Handling a database request includes providing a first database manager on a storage device containing data for the database, generating the database request external to the storage device, providing the database request to the first database manager on the storage device, and the first database manager servicing the database request by obtaining data internally from the storage device and processing the data within the storage device to provide a result thereof, wherein portions of the data that are not part of the result are not provided externally from the storage device. Handling a database request may also include providing a host having a database application running thereon. The database request may be generated by the database application. Handling a database request may also include providing a second database manager on the host, where the second database manager communicates with the first database manager to provide the database request.

Abstract: A high-performance and highly-reliable snapshot management apparatus and method, and a storage system are provided that can prevent the adverse influence of overhead when they retain a multiplicity of snapshots. An operational volume is set in a storage area provided by a first storage apparatus and a plurality difference volumes are set in a storage area provided by a second storage apparatus. In response to data writing to the operational volume, difference data is saved in the difference volumes and management tables for it are created, with each snapshot being managed according to the management tables. Each management table is divided according to one or more snapshots in accordance with the snapshot creation time. The second and any following management tables store specified inheritance information to inherit the content of the preceding management tables.

Abstract: Methods, software suites, and systems of generating a recovery snapshot and creating a virtual view of the recovery snapshot are disclosed. In an embodiment, a method includes generating a recovery snapshot at a predetermined interval to retain an ability to position forward and backward when a delayed roll back algorithm is applied and creating a virtual view of the recovery snapshot using an algorithm tied to an original data, a change log data, and a consistency data related to an event. The method may include redirecting an access request to the original data based on a meta-data information provided in the virtual view. The method may further include substantially retaining a timestamp data, a location of a change, and a time offset of the change as compared with the original data.

Abstract: The present invention relates to a system and method of data restoration, for instance, after the occurrence of a user error. In particular, snapshot database can be maintained that stores a copy of database data. The snapshot database does not have to store a complete copy of all data on a source database, but rather shares data that is common to both but not necessarily identical. If an error occurs on the primary database then the database can be reverted back to a point in time prior to the error by replacing source database files with snapshot files. Additionally, an undo component can be employed in conjunction with the snapshot to approach an error to a finer grained point in time. In brief, the present invention can restore a database much faster and simpler, while utilizing less space and resources than conventional data restoration technologies.

Abstract: One challenge to continuous data protection (CDP) is the resources required for storage. Typically, when setting up replication, a production volume and replica are set up and initialized to copy data from the production volume to the replica. However, instead of taking a clone of the volume, there are significant advantages to taking an array-based snapshot of the volume and leveraging capabilities inherent to the snapshot to improve data protections systems using CDP. To leverage the benefits of snapshots in a CDP system, as described below, example embodiments of the present invention use multiple snapshots. Bookmarks are created to indicate the point in time each snapshot was create so that a newer snapshot may be used for replication as data is applied to the replica.

Abstract: A supervisory control system includes a supervisory control target device and a supervisory control device. The supervisory control device is configured such that an attribute usage flag that indicates whether the supervisory control device supports any changes in the attributes due to adding of a function, and an attribute effectiveness flag which indicates whether the supervisory control target device supports the changes, are added, as information concerning the attributes that undergo the changes, to a definition of the instance which the supervisory control device retains. Further, the supervisory control device includes a control unit which, on a basis of data of the attribute usage flag and attribute effectiveness flag relating to the attributes undergoing the changes due to adding of a function, determines whether the supervisory control target device supports a new function or whether supervisory control based upon the new function is effective.

Abstract: Methods and apparatus for organizing a plurality of versions of a file in a file system. The plurality of versions of the file are stored in a data structure having a hierarchical organization that reflects relationships among the plurality of versions. Each version of the plurality of versions is assigned a name that identifies its position in the hierarchical organization. The hierarchical organization of the data structure and the descriptive naming convention used for the plurality of versions in the data structure facilitates deleting a version while retaining other versions derived from the version following the deletion of the version, and enables a staged initialization of the data structure upon system start-up.

Abstract: An information retrieval system having: a client adapted for accessing a plurality of file sets stored on one of a plurality of file servers; a plurality of file servers configured to operate with a federated file system namespace; and a memory for storing re-direction information accessible by the client for identifying a request issued by the client for a file set at a first location in the namespace where the file set is located at a second, different location on one of the file servers and wherein the client in examining the re-direction information in the memory, re-directs the request to the second location in accordance with the re-direction information.

Abstract: A system uses one or more processors and an interface to a backup repository to generate a set of backup objects for a point in time, store the set of backup objects in the backup repository, and store mapping information usable to retrieve appropriate backup objects when desired. A first map relates one or more applications to objects used by the applications. A second map relates the objects to corresponding data blocks or other data locations on volumes. A third map relates the data locations to corresponding backup objects for the point in time.