Abstract: Database management is described. A source data structure is copied to create a new data structure. Changes to the source data structure that occur during and after creation of the new data structure are accumulated in a file before they are added to the new data structure. Changes included in the file are subsequently applied to the second data structure.

Abstract: Provided are a method, system, and computer program product for creating a buffer point-in-time copy relationship for a point-in-time copy function executed to create a 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. Detection is made that the target volume of the new point-in-time copy relationship is a source volume of a first pre-existing point-in-time copy relationship having as a target volume a third volume. Detection is also made that the target volume of the first pre-existing point-in-time copy relationship is a source volume of a second pre-existing point-in-time copy relationship having as a target volume a fourth volume.

Abstract: In one embodiment, a user or client device is connected to a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. According to one embodiment, the system stores representations of the snapshots that govern a file or directory and its descendants within metadata associated with that file or directory. In one embodiment, before modifying a file or directory, the system updates the representations of the governing snapshots by traversing the metadata of ancestors of the file or directory.

Abstract: A method, system and computer program product for generation and management of incremental backups of VEE file system using bitmaps. The proposed method allows users to roll back to any previous version or state of the VEE file system and to instantiate this version using the data encapsulated in virtual disk storage (i.e. file system) of the VEE. A number of VEEs run on a Host Operating System of the computer system. One of the VEEs implemented on the computer system is designated to generation and management of backups of the virtual disk data of the other VEEs without freezing the file system during the entire backup process. A special tracing application runs on the designated VEE for generating the bitmap of a file system snapshot. The user can also set up a time for generating a backup or create a schedule for automatically generating the backups at critical points.

Abstract: In a storage system, one or more storage apparatuses provide a management computer with a first volume for storing data from the management computer, provide a host computer with a second volume for storing data from the host computer, and manage a volume address for the one or more storage apparatuses to manage the first volume and the second volume in the one or more storage apparatuses. The management computer issues a command specifying an arbitrary volume address to the one or more storage apparatuses, and designates, when receiving a normal response from the arbitrary volume address, a volume with the arbitrary volume address as the second volume.

Abstract: In one embodiment, a user or client device is connected to a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. In one embodiment, the metadata comprises mini-snapshots for directories representing a path from the root of the file system to the root of the snapshot. The mini-snapshots serve as stand-ins for portions of the file system which are not included in the snapshot, but which permit access to the snapshot data in an intuitive way.

Abstract: A system and method for legacy system component incremental migration from a legacy system to a new system comprises a read-only ghost or shadow in the new system. When changes are made in the legacy system, the changes are incrementally and automatically migrated to the new system allowing the legacy system and the new system to maintain availability during the migration. The concept of “mastership” is used where a component exists in the “New System”, but is actually mastered in the “Legacy System”. By allowing a sub-component to exist as a read-only ghost or shadow in the new system, and still be mastered/edited in the legacy system, a one-way bridge is provided so that the two systems can interact. The synchronization of the legacy system component is managed so that the ghost component is automatically updated when changes are made to the legacy system component and there is little maintenance that the user needs to do to create the bridge between the two systems.

Abstract: Provided is a method and system for performing volume migrations while retaining persistent point in time data of the migrated volume. Specifically, by using a collective persistent point in time data map that describes a collection of persistent point in time data of a volume to be migrated, the collective persistent point in time data map and volume data can be migrated during a quiesced period of user activity. Then, during a non-quiesced period of user activity, the persistent point in time data can be transferred to the location of the migrated volume in real-time.

Abstract: Disclosed are a storage control apparatus, a storage control program, and a storage control method that collect the backup of storage data in units of generation at low cost. A storage control apparatus that creates a generation backup of a storage, comprising: a first copy section that creates a snapshot of at least one of all data stored in the storage at an indicated time point and difference data stored in the storage in an indicated time period; a second copy section that creates a mirror of at least one of all data stored in the storage and difference data stored in the storage in an indicated time period; and a controller that causes one of the first and second copy sections to copy all data stored in the storage and causes the other to copy difference data between generations stored in the storage.

Abstract: A method, system, and computer-readable medium to maintain consistent, up-to-date copies of primary data. Primary data is maintained on a primary node, and point-in-time snapshots of the primary data are maintained on a secondary or remote node. Read operations can be directed to read some or all data from the remote node. When part of the data on the primary node becomes unavailable due to corruption, device failure, or communication failure, unavailable data can be read from the secondary node. When the determination is made that an unavailable portion of the data exists, a third data storage accessible by the first host can be created. Each subsequent change to the data in the first data storage can be written only to the third data storage. If an updated portion of the data is to be read, the updated portion can be read from the third data storage.

Abstract: A method, system, computer system, and computer-readable medium for maintaining up-to-date, consistent copies of primary data without the need to replicate modified data when the data were modified as a result of an operation that is not an application-driven write operation captured during replication. Selected storage management operations are performed on the primary and secondary data stores at points in time when the data are the same to ensure that the data stored within the data stores remain consistent. These selected storage management operations include operations that produce modified data stored in the primary data store, where a portion of the modified data are not replicated to a secondary node. Other types of storage management operations are selected to be performed on both the primary and secondary data stores, where the operations do not directly change data in the primary data store, but may affect data stored in the primary data store.

Abstract: Provided are a backup data management system and a backup data management method capable of facilitating the management of backup data that is multiplexed between different storage apparatuses. The backup data management system includes a storage apparatus having a volume to be used by a host computer, at least one storage apparatus having volumes, and a management computer. The management computer creates a copy pair so that a snapshot of the volume included in a backup group is stored in all the volumes included in the backup group, and sets all copy pairs included in the designated backup group to a PAIR status when there is a creation request of the snapshot of the volume.

Abstract: A computer system with read/write access to storage devices creates a snapshot of a data volume at a point in time while continuing to accept access requests to the mirrored data volume by copying before making changes to the base data volume. Multiple snapshots may be made of the same data volume at different points in time. Only data that is not stored in a previous snapshot volume or in the base data volume are stored in the most recent snapshot volume.

Abstract: A partial replication step shot method. The method includes receiving a first snapshot at a first time from a replication source and receiving a set of data objects from the replication source that have been modified during a time period between the first time and a subsequent second time. A second snapshot is generated at the second time on the replication source by using the set of data objects. An application is mounted onto the second snapshot prior to the set of data objects being received to completion.

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 data storage system includes a storage device divided into a plurality of blocks for storing data for a plurality of volumes, and a processor to execute instructions for maintaining a block map corresponding to the data stored on the storage device. The storage system may be part of a storage system network. The block map stores reference data indicating which of the volumes reference which blocks on the storage device, and which blocks on the storage device are unallocated. The reference data may include, for groups of one or more blocks, a first value identifying the oldest volume in which the group of blocks was allocated and a second value identifying the newest volume in which the group of blocks was allocated. The volumes may include one or more snapshots.

Abstract: A method begins by a processing module obtaining a directory file and determining a new snapshot identifier (ID) for the directory file. The method continues with the processing module identifying a version of a filename to associate with the new snapshot ID and updating the directory file by associating the snapshot ID to the version of the filename to produce an updated directory file. The method continues with the processing module dispersed storage error encoding the updated directory file to produce a set of encoded updated directory file slices and sending the set of encoded updated directory file slices to a dispersed storage network (DSN) memory for storage.

Abstract: A method, system, apparatus, and computer-readable medium are provided for taking snapshots of a storage volume. According to aspects of one method, each snapshot is represented as a unique sequence number. Every fresh write access to a volume in a new snapshot lifetime is allocated a new section in the disk, called a provision, which is labeled with the sequence number. Read-modify-write operations are performed on a sub-provision level at the granularity of a chunk. Because each provision contains chunks with valid data and chunks with invalid data, a bitmap is utilized to identify the valid and invalid chunks with each provision. Provisions corresponding to different snapshots are arranged in a linked list. Branches from the linked list can be created for storing writable snapshots. Provisions may also be deleted and rolled back by manipulating the contents of the linked lists.

Abstract: One embodiment is a method that builds a target database with transaction logs from an online source database. The transaction logs include both existing data in the source database and updates that occur to the source database while the target database is being built.

Abstract: A method and device for managing snapshot data is provided. Snapshots may be created having a preserved data area and a write data area. The preserved data area is used to maintain snapshot data corresponding to the point-in-time when the snapshot was created while the write data area is used to facilitate host read/write access to the snapshot. By maintaining two separate areas, the snapshot can be written to without altering the point-in-time representation of the snapshot.

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: The invention is a reorganization system having a reorganization application, a database management system, and one or more database files. The reorganization application communicates with the database management system and the one or more database files to reorganize an object, such as, for example, a table or index, while providing one or more clients substantially continuous access to the object. The reorganization application employs one or more trigger locks to synchronize the data in an original table and a reorganized table. The one or more trigger locks block select data modification operations while allowing one or more read-only operations and structural modification operations.

Abstract: In general, in one aspect, the invention relates to a method for taking a snapshot of a service instance, including transitioning the service instance to a new state, determining whether to take the snapshot based on the new state, obtaining a property composition of the service instance, and taking the snapshot using the property composition, if the snapshot is to be taken.

Abstract: An executing database instance includes a first plurality of database pages associated with a previous state of the database instance, a cache storing a current converter of the executing database instance, the current converter not representing the first plurality of database pages, and a database management system. The database management system is to receive a request for access to the first plurality of database pages, and perform a database task using one or more of the first plurality of database pages while the database instance is executing.

Abstract: Performing data management operations on replicated data in a computer network. Log entries are generated for data management operations of an application executing on a source system. Consistency point entries are used to indicate a time of a known good, or recoverable, state of the application. A destination system is configured to process a copy of the log and consistency point entries to replicate data in a replication volume, the replicated data being a copy of the application data on the source system. When the replicated data represents a known good state of the application, as determined by the consistency point entries, the destination system(s) may perform a storage operation (e.g., snapshot, backup) to copy the replicated data and to logically associate the copied data with a time information (e.g., time stamp) indicative of the source system time when the application was in the known good state.

Abstract: Disclosed herein is a method for controlling a storage device controller connected to a storage device provided with a plurality of storage volumes for storing data respectively and an information processing apparatus for requesting an input/output of data so as to receive an input/output request from the information processing apparatus and execute an input/output processing of the data for each of the plurality of storage volumes. The method brings one (primary) of the plurality of storage volumes into correspondence with another (secondary) in which a copy of data is to be written when the data is written in the primary volume so as to form a pair group consisting of a plurality of pairs, each having such a primary volume and such a secondary volume.

Abstract: A storage system including: a storage device for storing a file; a plurality of file systems for managing the file; and a plurality of NAS servers that control access from a client to the file systems via a global namespace formed by grouping local namespaces for the one or more file systems; wherein, each NAS server includes a memory to store global namespace management information including global paths of the file systems; one NAS server of the NAS servers accepts a request to obtain snapshots of the file systems from external of the storage system; the one NAS server instructs itself and the other NAS servers to obtain snapshots of the file systems; the one NAS server and the other NAS servers obtain the snapshots of the file systems, and inform the one NAS server of snapshot identifiers and of local paths of the snapshots; the one NAS server makes snapshot management information including global paths of the snapshots based on each of the snapshot identifiers received from the other NAS servers and each

Abstract: A temporary file is identified. The temporary file includes a data block containing a first file image. A determination is made whether the temporary block has been included in a previous snapshot. Responsive to receiving a modification of the temporary block that has been included in the previous snapshot, a modified first image is created. The modified image is stored in the original file block, and the original image is copied to a newly allocated block. The original first block is updated to include a reference to the second block.

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: In one embodiment, a user or client device communicates with a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. In some embodiments, systems and methods intelligently choose whether to use copy-on-write or point-in-time copy when saving data in a snapshot version of a file whose current version is being overwritten. In some embodiments, systems and methods allow snapshot users to return from a snapshot directory to the immediate parent directory from which the user entered into the snapshot.

Abstract: Systems and methods for information storage replication are presented. In one embodiment a replication method includes performing an intelligent synchronization process of selected portions of a primary image and intelligent verification of the accuracy of the replication. The intelligent synchronization process can include forwarding information if the information is in use (e.g., has been altered, written to, etc.) and the intelligent verification can be performed on the information in use.

Abstract: Embodiments described herein adapt static-image and clone technology to provide a simulated dynamic image to an application requesting a dynamic image. A storage system is configured to backup its file system by taking a first static image of the file system at a point in time. A clone of the first image may then be produced, the clone containing any subsequent changes to the file system and a reference pointer to the first image. A second static image of the clone is then produced. An application may request, from the storage system, an image of the file system. In response, the second static image may be presented to the application as a simulated dynamic image.

Abstract: A system and method of creating a snapclone for on-line point-in-time complete backup in a virtualized storage system is disclosed. In one embodiment, a method for creating a snapclone for on-line point-in-time complete backup in a virtualized storage system includes receiving a copy operation directed to one or more identified segments of an original virtual disk, in response to the copy operation, substantially sequentially copying the one or more identified segments to a snapclone virtual disk, clearing bits in an in-memory sharing bitmap associated with already copied one or more identified segments, and writing the cleared bits in the in-memory sharing bitmap to a disk resident virtual disk metadata associated with the snapclone virtual disk upon receiving a current write I/O operation while the copy operation is in progress. The received current write I/O operation is targeting data outside the LBA range of the already copied one or more identified segments.

Abstract: A replicated database instance can be provisioned that provides primary and secondary replicas that can be provisioned in different data zones or geographical locations. The database can be installed on the primary replica, and both the primary and secondary replica can have installed a block level replication mechanism that allows any I/O operation to be replicated by between the primary and secondary replicas. Any failure or outage of the primary replica can be addressed by performing a failover operation to the secondary replica. A DNS name or other such approach can be used such that the name can be aliased to the secondary replica during a failover, such that there is no action needed on the part of the customer to utilize the “new” primary replica. The creation of the database and provisioning of the replicated instance can be initiated using a Web service call to a control environment.

Abstract: Synchronous mirroring of data stored in a first storage system is performed by storing a mirror copy of the data at a remote second storage system. A first snapshot of the data stored in the first storage system is created, and a second snapshot of the mirror copy in the second storage system is created. A first signature of the first snapshot and a second signature of the second snapshot are calculated, and the first and second signatures are compared to verify whether or not the data in the first storage system is identical to the mirror copy in the second storage system.

Abstract: Information from multiple databases is retrieved and stored on a database storage system. Multiple point-in-time copies are obtained for each database. A point-in-time copy retrieves data changed in the database since the retrieval of a previous point-in-time copy. A virtual database (VDB) is created by creating a set of files in the data storage system. Each file in the set of files created for a VDB is linked to the database blocks on the database storage system associated with a point-in-time copy of the source database. The set of files associated with the VDB are mounted on a database server allowing the database server to read from and write to the set of files. Workflows based on VDBs allow various usage scenarios based on databases to be implemented efficiently, for example, testing and development, backup and recovery, and data warehouse building.

Abstract: Information from multiple databases is retrieved and stored on a database storage system. Multiple point-in-time copies are obtained for each database. A point-in-time copy retrieves data changed in the database since the retrieval of a previous point-in-time copy. A virtual database (VDB) is created by creating a set of files in the data storage system. Each file in the set of files created for a VDB is linked to the database blocks on the database storage system associated with a point-in-time copy of the source database. The set of files associated with the VDB are mounted on a database server allowing the database server to read from and write to the set of files. Workflows based on VDBs allow various usage scenarios based on databases to be implemented efficiently, for example, testing and development, backup and recovery, and data warehouse building.

Abstract: A device and method for connection to a host and transferring data between the host and data storage assembly. The device is preferably a storage system which initializes a logical unit (LUN) in the storage assembly. A persistent memory stores a data representation of clean areas in the LUN. The storage system receives data to be written from the host to a destination area in the LUN, and determines if the destination area in the LUN is a clean area or a dirty area as indicated in the persistent memory. The storage system effects a snapshot copy of data from the destination area in the LUN to an archive storage device of the storage assembly only if the destination area is not entirely a clean area. Bandwidth is likewise reduced in LUN copy and reconstruction operations.

Abstract: A system according to one embodiment includes at least one processor configured to: receive a request to perform a snapshot of data associated with an application running on multiple servers; instruct I/O Freezers on different servers to freeze data requests from instances of the application running on the servers; and instruct the I/O Freezers to initiate snapshot processing on the data associated with the application so that the I/O Freezers perform the snapshot processing within the same window of synchronization.

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: A data replication system comprises a NAS controller and a storage system. In a first embodiment, after a NAS system takes a snapshot of a volume, the NAS system changes the referral information within the volume. Also, as an additional way to ensure the consistency after taking a snapshot, the NAS System returns the changed referral information based on a referral management table when clients access a referral within the snapshot volume so that clients can access an appropriate volume. In a second embodiment, after a volume on a NAS system is replicated by remote copy to a remotely deployed NAS system, the remotely deployed NAS system returns the changed referral information based on a referral management table when clients access a referral within the replicated volume so that clients can access an appropriate volume.

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: A method for performing multiple merge operations with a source data structure and a plurality of destination data structures, in which the source data structure is scanned one time in order to obtain source data that is then used for multiple merge operations. The source data is then used consecutively in order to merge the source data into the one or more destination data structures. Each merge is performed using the same scan of the source data structure and within the same execution of a database command.

Abstract: The present invention describes a technique for using shadowing object for approval control in an object-oriented software environment. The technique calls a business operation and determines whether the business operation needs to be approved. If the business operation needs to be approved, a shadowing business object and a shadowing connector corresponding to the original business object and the connector are created, and the business operation is performed on the shadowing business object and connector, and all results are stored in the shadowing business object, and all messages to be sent are buffered in the connector. If the business operation is approved, the original business object is replaced by the shadowing business object. The technique is flexible, efficient, easy to be modified and supplemented.

Abstract: Provided are a method, system, and article of manufacture for converting backup copies of objects created using a first backup program to backup copies created using a second backup program. A plurality of backup copies of versions of an object are created using a first backup program, wherein the object has an object name. The first backup program is used to restore at least one of the backup copies to a restored version of the object having a name different from the object name. A second backup program is used to create a backup copy of each restored version of the object. A name of a designated object is assigned to each backup copy created using the second backup program. Metadata of each backup copy created using the second backup program is updated with metadata for the designated object.

Abstract: A storage system including: a disk device including an original volume and a plurality of snapshot generations; and a storage control unit which includes a processor unit. The processor unit receives write data to a storage area of the original volume, and determines whether data stored in the storage area of the original volume is already copied to the snapshot volume or not; if the data stored in the storage area of original volume is not already copied to snapshot volume, the processor unit copies the data from original volume to the snapshot volume, when a use capacity of the snapshot volume is larger than threshold amount by the copy, the processor unit indicates a specified snapshot generation, the processor unit migrates data of the specified snapshot generation from the snapshot volume to tape device; the processor unit deletes information of the specified snapshot generation in the snapshot volume.

Abstract: The correspondence relationship between local paths in local namespaces for snapshots FS0-SNAP0, FS1-SNAP0, and FS2-SNAP0 of file systems FS0, FS1, and FS2 and global paths in a global namespace for those snapshots is defined so that the directory configuration in the global namespace of the snapshots FS0-SNAP0, FS1-SNAP0, and FS2-SNAP0 becomes the same as the directory configuration in the global namespace of the file systems FS0, FS1, and FS2.

Abstract: A snapshot management device and snapshot management method whereby a snapshot is obtained on a regular basis, the amount of difference between two obtained snapshots is detected and, when the detected difference amount is smaller than a threshold value, of the two snapshots, the snapshot obtained earlier than the other is deleted, thereby contributing to the improved convenience.

Abstract: In one embodiment, a user or client device communicates with a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. In some embodiments, systems and methods intelligently choose whether to use copy-on-write or point-in-time copy when saving data in a snapshot version of a file whose current version is being overwritten. In some embodiments, systems and methods allow snapshot users to return from a snapshot directory to the immediate parent directory from which the user entered into the snapshot.

Abstract: A set of probabilities may indicate the chance of finding the latest version of a data item in any particular data image layer of a data image. A client may use the set of probabilities to request the data item from one or more layers that have a higher probability of having that version of the data item. A client may query more recently created layers to determine whether they have a version of the data item. If any of the more recently created data image layers has a version of the data item, a client may request the data item from the most recent of the more recently created layers and may discard any data returned from the originally requested layer. A client may update the historical probabilities based on which layers contain versions of the data item.