Abstract: Setting up and supporting the computer infrastructure for a remote satellite office is a difficult task for any information technology department. To simplify the task, an integrated server system with a hierarchical storage system is proposed. The hierarchical storage system includes the ability to store data at an off-site cloud storage service. The server system is remotely configurable and thus allows the server to be configured and populated with data from a remote location.

Abstract: An undo process performed on a data object includes selecting a stored prior state of the data object; comparing the stored prior state with the current state of the data object to determine differences between the stored prior state and the current state of the data object other than the effect of the undesired editing operation; and applying the differences to the stored prior state of the data object to obtain a new state of the data object. Each prior state of the data object corresponds to an effect of one of previously performed editing operations on the data object.

Abstract: The present invention relates to a method for performing an image level copy of an information store. The present invention comprises performing a snapshot of an information store that indexes the contents of the information store, retrieving data associated with the contents of the information store from a file allocation table, copying the contents of the information store to a storage device based on the snapshot, and associating the retrieved data with the copied contents to provide file system information for the copied contents.

Abstract: Systems, methods, and media for synthesizing a view of a file system are provided herein. Methods may include receiving a request to obtain a view of at least a portion of a file system backup for a device, responsive to the request, mounting one or more backup files for the device on a backup node, generating a view of the at least a portion of a file system created from the one or more mounted backup files, the view being accessible via the intermediary node that is communicatively coupled with the backup node.

Abstract: Example embodiments provide various techniques for providing a backup functionality to a particular application. In one example, a plug-in module is selected for activation from a number of different plug-in modules. This selected plug-in module is adapted to interface with the particular application. It should be noted that each plug-in module is adapted to interface with a different application. The particular application is quiesced using the selected plug-in module. After the application has been quiesced, the backup functionality is initiated.

Abstract: A method includes initiating committing to persistent storage of a current consistency snapshot of a plurality of data objects in a redirect-on-write file system. Each of the plurality of data objects has a first copy of at least two copies of the data having a first context of at least two contexts. The method includes receiving, during committing to storage of the current consistency snapshot, an update to a data object of the plurality of data objects. The method also includes responsive to receipt of the update to the data object, creating a second copy of data of the data object from the first copy. The second copy of the data has a second context of the at least two contexts. The method includes responsive to receipt of the update to the data object, updating, based on the update, the second copy of the data of the data object.

Abstract: To preserve the contiguity of file map extents of a production file when making a series of snapshot copies, the snapshots share indirect blocks of the production file through virtual pointers. When a write to a data block of the production file is first done since the time of the most recent snapshot so that the most recent snapshot can no longer share one of the contiguous indirect blocks, a new indirect block is allocated to store the file mapping metadata for the most recent snapshot, and a virtual pointer for the snapshots is changed to point to this new indirect block. Therefore the change in the virtual pointer changes the file mapping metadata for any number of snapshots sharing the new indirect block so that the method is scalable.

Abstract: A method for managing multiple generations of an object within a distributed storage system is implemented at a computing device. The computing device receives metadata and content of a first generation of an object from a first client connected to the distributed storage system and stores the first generation's metadata and content within a first storage sub-system. The computing device receives metadata and content of a second generation of the object from a second client connected to the distributed storage system and stores the second generation's metadata and content within a second storage sub-system. The computing device independently replicates the first generation's metadata and content from the first storage sub-system to the second storage sub-system and replicates the second generation's metadata and content from the second storage sub-system to the first storage sub-system such that both storage sub-systems include a replica of the object's first and second generations.

Abstract: A method is used in recovering files in data storage systems. A set of file system blocks of a file of a file system is identified. The set of file system blocks are associated with a portion of an inode of the file of the file system. Mapping information associated with the portion of the inode is missing references to the set of file system blocks. Metadata of each file system block of the set of file system blocks is evaluated. Based on the evaluation, the portion of the inode of the file is recovered by updating mapping information associated with the portion of the inode.

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: 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: Methods and systems for cluster resource management in virtualized computing environments are described. VM spares are used to reserve (or help discover or otherwise obtain) a set of computing resources for a VM. While VM spares may be used for a variety of scenarios, particular uses of VM spares include using spares to ensure resource availability for requests to power on VMs as well as for discovering, obtaining, and defragmenting the resources and VMs on a cluster, e.g., in response to requests to reserve resources for a VM or to respond to a notification of a failure for a given VM.

Abstract: Systems, methods, and media for synthesizing a view of a file system are provided herein. Methods may include receiving a request to obtain a view of at least a portion of a file system backup for a device, responsive to the request, mounting one or more backup files for the device on a backup node, generating a view of the at least a portion of a file system created from the one or more mounted backup files, the view being accessible via the intermediary node that is communicatively coupled with the backup node.

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. A corresponding apparatus and computer program product are also disclosed herein.

Abstract: Distributed computer systems prepare and instantiate snapshots by processing sets of nodes representing computer resources that are portions of a larger system. A user may choose to prepare or instantiate a snapshot containing all or only a portion of the data within the distributed computer system, such as a template of the distributed computer system. A template snapshot may be available in an electronic marketplace for other users to purchase and instantiate into a replica of the distributed computer 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 computer-implemented method for performing live backups may include identifying a request to perform a live backup on a volume of data. The computer-implemented method may also include creating a snapshot of the volume. The computer-implemented method may further include identifying each attempt to write to the volume during the live backup. The computer-implemented method may additionally include, for each write attempt, identifying a block of data that the write attempt will overwrite and copying the block of data to a backup queue before allowing the write attempt. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Methods, systems, and computer program products are provided for performing data backup of a file system. A monitoring process is configured to include a file system representation (FSR) representing the file system, the FSR comprising a plurality of nodes, each node corresponding to a respective one of a plurality of elements of the file system. A monitoring process includes a file system representation (FSR) of a file system. The FSR comprises a plurality of nodes corresponding to a respective one of a plurality of elements of the file system. The monitoring process receives a notification of a change to a first element of the file system, caches information associated with a second element of the file system to provide cached information, and processes the FSR in response to the change.

Abstract: Provided are a method, system, and computer program product for creating a buffer point-in-time copy relationship. A point-in-time copy function is initiated to create a new point-in-time copy relationship from a source volume comprising a first volume to a target volume comprising a second volume. A buffer point-in-time copy relationship having a source volume comprising the target volume of the first pre-existing relationship and a target volume comprising a fifth volume is created in response to detecting that the target volume of the new point-in-time copy relationship is the source volume of a first pre-existing point-in-time copy relationship and detecting that the target volume of the first pre-existing point-in-time copy relationship is the source volume of a second pre-existing point-in-time copy relationship.

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: Techniques for providing on-demand validation services for wager-based virtual machines deployed in a cloud based virtual environment. In some implementations, data sources store master deployment sets containing virtual machines. The master deployment sets may be deployed to component servers to provide a gaming related software services to remote client machines. The on-demand service takes snapshots of the virtual machines in the deployment and the virtual machines in the master deployment set. The snapshots are compared to ensure that important files in the master deployment set have not been improperly modified in the deployment. In some implementations, a secure hashing algorithm creates signatures for the snapshots prior to the comparison and the signatures are compared. The validation result may be sent to a remote client that requested the validation.

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 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: A method and system for utilizing snapshots to provide copies of a database or other application or large data structure to computing devices receives a request for access to a copy of a database, and performs a snapshot of a storage volume containing the requested database. The system then clones the snapshot and mounts the snapshot to a computing device, thus enabling the computing device to access a copy of the database. In some examples, the system automatically updates copies of a database on a scheduled basis (e.g., daily or weekly basis) to refresh a database regularly.

Abstract: Distributed computer systems prepare and instantiate snapshots by processing sets of nodes representing computer resources that are portions of a larger system. A user may choose to prepare or instantiate a snapshot containing all or only a portion of the data within the distributed computer system, such as a template of the distributed computer system. A template snapshot may be available in an electronic marketplace for other users to purchase and instantiate into a replica of the distributed computer system.

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: This application describes techniques for creating a second snapshot of a first snapshot of a set of data, modifying the first snapshot, and reverting the modifications to the first snapshot. For example, portions of one or more transaction logs may be played into a database to put the database in a particular state a particular point in time. The second snapshot may then be used to revert to a prior state of the database such that additional transaction logs may be played into the database. These techniques enable the ability to put the database into multiple states as the database existed at multiple points in time. Therefore, data can be recovered from the database as the data existed at different points in time. Moreover, individual data objects in the database can be accessed and analyzed as the individual data objects existed at different points in time.

Abstract: A computer-readable recording medium stores a program that causes a computer to execute a verification support process that includes acquiring a series of data transmitted and received between apparatuses; creating a plurality of data groups by dividing the series of acquired data; detecting among the created data groups, a data group that includes given data acting as an issuance request for identification information of a transmission source; adding the given data to the beginning of subsequent data groups that are among the created data groups and transmitted after the detected data group; and outputting the subsequent data groups to which the given data has been added.

Abstract: A first epoch column pair includes a first global identification (ID) having first maximum value. A second epoch column pair includes a second global identification having second maximum value. The first epoch column pair receives first snapshots, and the first global ID increases with each of the first snapshots. When first global ID reaches first maximum value minus 1, switch to the second epoch column pair. The second epoch column pair receives second snapshots, and second global ID increases with each of the second snapshots. First global ID and first epoch column pair are reset, based on conditions. When second global ID reaches first maximum value minus 1, switch back to first epoch column pair. The first epoch column pair again receives first snapshots, and the first global ID increases with each of the second snapshots. Second global ID and second epoch column pair are reset, based on conditions.

Abstract: Migration of computer information. In one example embodiment, a method for migration of computer data includes modifying a volume boot record of a destination volume to a first state in which at least a portion of the destination volume becomes inaccessible to a standard file system, writing one or more snapshots of a source volume to the inaccessible portion of the destination volume while the volume boot record is in the first state, and restoring the volume boot record to a second state in which the inaccessible portion of the destination volume becomes accessible to the standard file system.

Abstract: An on-disk structure of a file system has the capability to maintain snapshot and file system metadata on a storage system. The on-disk structure arranges file system data sequentially on disk within regions, wherein each region comprises a predetermined amount of disk space represented by blocks. The snapshot and file system metadata is maintained within level 1 (L1) indirect blocks of the on-disk structure. Each L1 indirect block describes (i.e., represents) a corresponding region of the on-disk structure of the file system; in the case of an active region, e.g., an L1 indirect block represents an active file data portion of a large file. The L1 indirect block that references an active region also performs file block number (fbn) to disk block number (dbn) mapping for the region.

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: A database is queried as of any wall-clock time within a retention period, via undo that uses database snapshots and a list of page level modifications. The snapshot is user-identified, automatically generated, or extracted from a backup. The list is maintained in a transaction log by persisting page content before a page is re-used, persisting deleted rows before they are moved, persisting compensation log record undo information, and/or logging a full page. To rewind an entire database, the undo scans the transaction log in reverse LSN order and undoes all page modifications. Undo reverses reallocated pages, table truncation, and/or table deletion, as well as page-level modifications of a schema, metadata values, and/or system tables. An as-of query is handled using as-of page(s) from a sparse page file. If the sparse page file does not already contain the responsive page(s), they are created and added to it.

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: One embodiment is for using a sparse file as a clone. The method includes creating, by an application associated with a computer system, a snapshot of a file, such as an individual file, a collection of files, file system, directories, and so forth. Further, the method includes requesting, by the application, a clone of that created snapshot. Further still, the method includes generating, by the application, an empty sparse having at least one inode identifying the empty sparse file as the clone and pointing to the snapshot associated with the clone. Thereby, the requested clone is created using the created sparse file, which begins as an empty sparse file.

Abstract: Systems and methods for providing business continuity services after a disaster or other loss of data are provided. The system and methods include accessing, replicating, and storing customer data. In the event of a disaster or other loss of data, the stored data is used to create fully recovered systems. The systems and methods provide for a remote data center that offers protection against physical disasters. The systems and methods include providing a virtual recovered operating system environment identical to the source operating system environment in less than 8 hours after notification of a disaster.

Abstract: A method and system for building a point-in-time snapshot of an eventually-consistent data store. The data store includes key-value pairs stored on a plurality of storage nodes. In one embodiment, the data store is implemented as an Apache® Cassandra database running in the “cloud.” The data store includes a journaling mechanism that stores journals (i.e., inconsistent snapshots) of the data store on each node at various intervals. In Cassandra, these snapshots are sorted string tables that may be copied to a back-up storage location. A cluster of processing nodes may retrieve and resolve the inconsistent snapshots to generate a point-in-time snapshot of the data store corresponding to a lagging consistency point. In addition, the point-in-time snapshot may be updated as any new inconsistent snapshots are generated by the data store such that the lagging consistency point associated with the updated point-in-time snapshot is more recent.

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 database is queried as of any wall-clock time within a retention period, via undo that uses database snapshots and a list of page level modifications. The snapshot is user-identified, automatically generated, or extracted from a backup. The list is maintained in a transaction log by persisting page content before a page is re-used, persisting deleted rows before they are moved, persisting compensation log record undo information, and/or logging a full page. To rewind an entire database, the undo scans the transaction log in reverse LSN order and undoes all page modifications. Undo reverses reallocated pages, table truncation, and/or table deletion, as well as page-level modifications of a schema, metadata values, and/or system tables. An as-of query is handled using as-of page(s) from a sparse page file. If the sparse page file does not already contain the responsive page(s), they are created and added to it.

Abstract: An on-disk structure of a file system has the capability to generate snapshots and provide fast sequential read access to data containers, such as files. The on-disk structure arranges sequential portions of files on disk within regions, wherein each region comprises a predetermined amount of disk space represented by blocks and wherein the data of the files stored within each region may or may not be stored sequentially within the region. In addition, the on-disk structure accommodates a plurality of types of regions, including (i) active regions that contain active file system data for large files, (ii) snapshot regions that contain “copy out” snapshot data for the large files and (iii) metadata regions that contain metadata, as well as directories and small files.

Abstract: Technologies are provided for reclaiming a file system coupled to a block device. In these technologies, a dummy file is created. The dummy file is expanded to fill a volume in the block device. A mapping of the dummy file to locations in the volume is retrieved. When the mapping of the dummy file to the locations in the volume is retrieved, corresponding space in the volume is reclaimed. This space may include the locations in the volume corresponding to the mapping of the dummy file. When this space in the volume is reclaimed, the dummy file is deleted.

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: Techniques for maintaining mirrored storage cluster data consistency on systems with two-node, highly available storage solutions can employ an initiator-side agent operable to prevent split-brain scenarios. Split brain syndrome can be avoided, information identifying changes of synchronization states can be maintained, and both graceful and ungraceful shutdowns (or failures) of either one of the nodes or of the intelligent initiator itself can be mitigated. Technology presented herein supports load balancing and hot failover/failback in systems that may feature redundant network connectivity. Moreover, a method is supported for communicating storage cluster status between the storage nodes and the initiator.

Abstract: The system and method for providing assured recovery and replication described herein may recover a master data source from a replica data source without impacting the master data source or the replica data source, and without having to install a standby version of an application associated with the master data source. In particular, a master snapshot may be created to copy application data stored in the master data source, wherein a replication server confirms that the replica data source can recover the master data source if the master snapshot and the replica data source are consistent. The replication server may create a replica snapshot to copy the replica data source and assign an identity associated with the master data source to the replica data source to recover the master data source. As such, replication may be resumed on a virtual machine disk file associated with the replica snapshot.

Abstract: In general, the invention relates to a method for migrating a source file system residing on a source server to a destination server. The method includes sending a first snapshot of the source file system from the source server to the destination server and creating, using the first snapshot, a migrated file system on the destination server. The method further includes sequentially sending, to the destination server, a set of snapshot deltas including modifications to the source file system, updating the migrated file system using the set of snapshot deltas, determining that a freeze threshold is exceeded, freezing the source file system, sending a final snapshot delta from the source server to the destination server, updating the migrated file system using the final snapshot delta, creating a file system husk referencing the migrated file system, and thawing the source file system and the migrated file system.

Abstract: A technique is disclosed for quiescing a file system. The technique includes holding a change request, flushing the file system, and releasing the change request. Flushing may include sending a flush request, determining whether a cache associated with the file system is flushed, and in the event that the cache is not flushed, resending the flush request and determining whether the cache is flushed.

Abstract: A view object is generated in a target deployment unit in a design time environment of a metadata repository. The view object is modeled on a business object of a source deployment unit. The source deployment unit includes process components of a business application that is physically decoupled from the target deployment unit. A subset of attributes of the business object of the source deployment unit is selected. The subset of attributes includes at least an outbound agent and an inbound agent implemented by a generic messaging framework. The view object is modeled in the target deployment unit with the subset of attributes of the business object. The inbound agent of the view object is configured for receiving a replication message from the outbound agent of the business object, and the replication message includes replication data for configuring the view object only with data from the business object.

Abstract: Embodiments for space-efficient cascading point-in-time copying of source data by creating a plurality of cascading point-in-time target copies, the target copies being created at different points in time, are provided. Data is physically copied form the source to a repository to create a physical copy, and a data mapping is created that associates the physical copy with a most recent target copy.