Abstract: Pre-update data is copied from a first storage device onto a second storage device in response to an update instruction to update data on the backup target volume on the first storage device. A copy status of each data on the backup target volume is managed with position information of the data mapped thereto. If bad data is present in the data on the backup target volume, the position information indicating the position of the bad data is searched. In accordance with the copy status managed with the position information mapped thereto, it is determined whether the pre-update data of the bad data is stored on the second storage device.

Abstract: Techniques for end-to-end tracing of database operations in source code for database applications are provided. Source code on the client side is instrumented to measure time spent on selected database operation statements (e.g., queries). The selected database operation statements can be uniquely tagged or identified. Tracing is enabled on the database application on the server side so that a log is produced, where the log includes performance (e.g., time spent) information on database operation statements that are executed. The performance information in the log is correlated to the selected database operation statements so that, among other things, the time spent on the client side and the time spent on the server side can be presented for analysis.

Abstract: A method and system for obtaining past information in a generic manner. For a certain time point, obtaining a copy of the process object, including its structure and data from recorded changes. When setting up the process object, an action rule is associated with the process object to automate that any change in the data content and/or structure is recorded with an associated time of the change. In response to a request for past information, steps are taken to acquire past data, acquire past change data, and create a temporary object to simulate the object that would have existed at the specific time requested.

Abstract: In a data processing apparatus, a snapshotting unit creates a second snapshot in a first storage space while a first snapshot of the first storage space exists in a second storage space. A storage unit stores first progress data indicating progress of physical copy to the first storage space for a current second snapshot, and second progress data indicating progress of physical copy to the first storage space for a preceding second snapshot.

Abstract: A method and system for automatically managing changes to organizational data in a unified messaging (UM) platform are disclosed. A database snapshot is retrieved from a client human resources database. The database snapshot includes human resources information organized in an organizational hierarchy. A change is detected in the database snapshot from a previous database snapshot, and organizational data in the UM platform is automatically modified to reflect the detected change in the database snapshot. When the change is detected in the database snapshot, it is possible for the UM platform to automatically compose and send a message to at least one user associated with the change including potential modifications of the organization data. The organizational data in the UM platform can then be modified only in response to receiving approval of the potential modifications of the organizational data from at least one user associated with the change.

Abstract: This method includes, in response to receipt of a snapshot request from a first node that receives an instruction to obtain a snapshot, identifying transactions in progress; transmitting data representing states of the identified transactions in progress to the first node; after the identifying, carrying out a first processing to prevent the transactions in progress from normally completing; receiving a list of first transactions whose results are reflected to snapshot data or a list of second transactions whose results are not reflected to the snapshot data; and executing copy-on-write on a basis of a specific time after removing the first transactions from among transactions to be processed in the first processing and confirming that the respective first transactions are normally completed or cancelled.

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: The present invention is devised so that snapshot data preparation processing does not end abnormally as a result of the pool region becoming full with saved data from the primary logical volume during snapshot data preparation. When the CHA receives a snapshot data preparation request, the CHA checks whether or not update information is present in the logical volume that is the object of this data preparation. If such information is present (YES in S51), a check is made from the number of slots in the in the volume control information and the updating amount count value in the update information in order to ascertain whether or not the proportion of the updating amount relative to the number of slots is equal to or greater than the threshold value in the threshold value control information (S52). If this proportion is equal to or greater than the threshold value (YES in S52), the update information is initialized (S53), and physical snapshot control is started (S54).

Abstract: A data restoration method comprising determining whether a restoration process is in progress, in response to receiving a read request to read contents from a track on a source volume (ST[i]); reading data from ST[i], in response to determining that the restoration process is not in progress; determining whether the read request was originated from a host, in response to determining the restoration process is in progress; reading the data directly from ST[i], in response to determining the read request was not originated from a host; determining whether ST[i] is designated as remote with respect to the restore operation, in response to determining the read request was originated from a host; reading the data directly from ST[i], in response to determining ST[i] is designated as local; and reading the data from a track on a target volume (TT[i]), in response to determining ST[i] is designated as remote.

Abstract: Systems and methods for cluster maintenance are presented. In one embodiment a cluster configuration method includes: maintaining configuration information associated with a first node and a second node, including cluster configuration version information; evaluating the first node as a potential configuration update node for the second node, including evaluating an indication of potential partial snapshot update availability based upon the configuration information associated with the first node and configuration information associated with the second node; performing an update type selection, including continued analysis of partial snapshot update availability; and performing an update for the second node in accordance with results of the update type selection.

Abstract: A first snapshot of a volume is created at a first point in time. A first backup operation to backup the volume to a first backup image using the first snapshot is initiated. The first backup operation terminates before completion, e.g., due to a failure. A second snapshot of the volume representing the state of the volume at a second point in time is then created. The second snapshot is used by a second backup operation to resume backing up the volume to a second backup image. The first backup image is then merged with the second backup image.

Abstract: A system includes a database instance, a data storage system, and a database management system. The data storage system stores a first data partition and a second data partition. The first data partition includes a first plurality of database pages storing tenant-independent data and a first converter associated with the first partition. The second data partition includes a second plurality of database pages storing tenant-independent data and a second converter associated with the second partition.

Abstract: In a system and method for updating a remote replicated destination file system snapshot with changes in a source file system snapshot, users and processes are redirected to a local exported snapshot of the replicated snapshot on the active file system on the destination before beginning the next update of the active file system's replicated snapshot. In this manner, an unstable replicated snapshot is not accessed. Indirection is introduced into inode lookup at the destination as the destination's active file system is being updated. The indirection can be based upon a snapshot ID that conforms to a latest exported snapshot ID.

Abstract: A computer-implemented method for tracking changes to a volume is disclosed. The method may comprise: 1) identifying a first snapshot of a volume, 2) identifying a window within which the first snapshot was created, the window beginning with a first point known to have occurred before the first snapshot and ending with a second point known to have occurred after the first snapshot, 3) identifying at least one change to the volume that occurred within the window, and 4) associating the at least one change that occurred within the window with both the first snapshot and a second snapshot created after the first snapshot. Corresponding systems and computer-readable media are also disclosed.

Abstract: Proposed are a computing system and a data management method for improving the usage efficiency of logical volumes without lowering the response performance In a computing system that includes a first storage apparatus in which first and second storage volumes are configured, a file storage apparatus for controlling the first logical volume, a second storage apparatus, and an archive apparatus for controlling the second storage apparatus, the first storage apparatus acquires a snapshot of the first logical volume at regular or irregular intervals and stores differential data in the second logical volume, specifies a file for which the consumption amount of the second logical volume exceeds a predetermined threshold, causes the first storage apparatus to acquire a snapshot of the specified file, and if a read request to read the file is supplied, generates the file on the basis of data stored in the first and second logical volumes.

Abstract: Systems and methods herein provide for protecting data using snapshots and images of those snapshots to quickly recreate data upon request. For example, a storage controller of a data storage system allocates a period of time between creating snapshots of data in a first storage volume of the data storage system. The controller then logs received write requests to the first storage volume and generates snapshot of data in the first storage volume based on the allocated period of time. Thereafter, the controller may receive a request to recreate data. The controller locates the snapshot in the first storage volume based on that request to recreate the data. In doing so, the controller generates a snapshot image in a second storage volume. The controller then retrieves logged write requests and applies them to the snapshot image to recreate the data in the second storage volume.

Abstract: A work flow is initiated and identified by a scenario identifier. A file system driver is notified to record operations on data associated with the work flow identified by the scenario identifier as raw journals without recording data content associated with the operations. The recorded operations are consolidated with previous operations as each operation is recorded in the raw journals. A system snapshot is initiated to be taken. The file system driver is notified of a point in time the system snapshot is taken. Data content associated with the consolidated recorded operations is retrieved from the system snapshot. A first packet is created from selected recorded operations and sent synchronously. A second packet including rest of the recorded operations along with associated data content are sent asynchronously with the point in time of the system snapshot.

Abstract: Improved backup and storage operations are disclosed for virtual computing environments using a backup proxy server to perform storage operations on one or more virtual machine disks. The proxy server can include a module that intercepts application programming interface (API) calls, for writing backup data to a first location, prior to the data arriving on the proxy disk. During the intercept process, the data can be compressed in memory pages of the proxy server and redirected to an alternative backup disk location. The proxy server can also include a differential engine that identifies changes to the virtual machine disk at the block level since the last full backup. The differential engine can advantageously leverage memory pages of the proxy server to compare differences between signatures of blocks of the last full backup with signatures of new blocks. Subsequently, only blocks with non-matching signatures are processed for backup.

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. In another embodiment, the invention provides a user interface screen enabling browser style browsing and recovery of quick recovery volumes and snapshot images.

Abstract: A method to store point-in-time data, comprising establishing a block size, providing source data storage comprising (S) blocks, and target data storage comprising (T) blocks. The method configures (B) source storage segments and (B) target storage segments, and receives updated point-in-time data for original point-in-time data written to an (i)th source storage segment. The method then determines if a (j)th target storage segment comprises available storage capacity to store the original point-in-time data. If a (j)th target storage segment comprises available storage capacity to store the original point-in-time data, the method writes the original point-in-time data to that (j)th target storage segment.

Abstract: A method and system for acquiring a quiesceing set of information associated with a virtual machine. A virtual machine is cloned. The cloned virtual machine has an associated persistent storage device. The state of the persistent storage device is transformed into a quiesced state of the cloned virtual machine by utilizing a shut-down process. The shut-down process is executed on the cloned virtual machine to quiesce the cloned virtual machine and the quiesceing set of information of the cloned virtual machine is automatically reduced to information stored on the persistent storage device.

Abstract: A method and apparatus for efficiently logging changes to a file system are disclosed. A file system filter driver intercepts I/O requests directed to a file system, and analyzes the I/O requests to determine whether the requests are write or modify requests directed to a file included in a list of files to be monitored for changes. If the I/O request is directed to such a file, the file system filter driver logs the I/O request to a b-tree structured change log file. Furthermore, in one embodiment, the file system filter driver is configured to log file system changes to multiple log files to coincide with snapshot operations, such that the file system changes to be included in each snapshot are included in separate log files.

Abstract: A method and system for generating and restoring a backup image are disclosed. A server receives a request, which includes a backup path, to generate a backup image. The server generates a backup image offset map that indicates a relative location where a file is stored in the backup image before file data has been written to the backup image. The server stores the backup image offset map in a portion of the backup image on a storage device. The backup image offset map comprises an array having a number of elements equal to a number of inodes on a file system that hosts a backup path, an element of the array representing an inode on the file system, and indicates the relative location where a file that is associated with a number of the inode is stored in the backup image.

Abstract: Techniques for continuous data protection can include creating snapshots of one or more underlying storage volumes upon specific file system events. Generating snapshots upon every file close event can protect the files in a storage system by keeping a snapshot of every version or modification of each file. Removal of redundant snapshots can mitigate the impact on storage capacity associated with creating these large numbers of volume snapshots upon each file close event. Additionally, file closure lists can be employed to allow generating snapshots only when a previously closed file is reopened. Such an approach can protect the previous version of a file prior to the opening of a new version of the file. Such an approach can also mitigate storage capacity impact without the creation of redundant snapshots.

Abstract: Various embodiments include one or more of systems, methods, software, and data structures that allow dual access to concurrent data in a database management system including uncommitted updated data. Some embodiments include a dual snapshot of data in a multi-version concurrency control style database, but the embodiments described herein are equally applicable to virtually any other type of database and database management system.

Abstract: In an example of an embodiment of the invention, a system for recording data generated by a client server and transmitted to a storage system is provided. The system comprises a storage system and a processor located remotely from the storage system and linked to the storage system via a network. The processor determines that a selected data processing operation is to be performed with respect to data stored in the storage system, and determines that a record of at least some of the data stored in the storage system is required prior to performing the selected data processing operation. The processor also generates a command comprising a request to generate a record of the at least some of the stored data, and transmits the command to the storage system to generate the record, via the network in accordance with Internet Protocol (IP). Examples of other systems and methods are also disclosed.

Abstract: A single native integrated system may be provided for replicating data to one or more copies of high-availability data and for replicating the data to one or more copies of backup data. The data may be replicated, in near real-time, to the one or more copies of high-availability data as changes occur to the data. The data may be replicated and later incorporated to a copy of the backup data at different points in time. The single native integrated system may have a single set of functions for replicating the data to the one or more copies of high-availability data and for replicating the data for the one or more copies of the backup data. Administrative access to the one or more copies of high-availability data may be isolated from administrative access to the one or more copies of the backup data.

Abstract: A computer migrates to the same remote controller, from among a plurality of remote virtual computers at a remote site, two or more remote virtual computers belonging to a group configured from remote virtual computers with similar remote copy patterns. In the remote controller, these two or more remote virtual computers and remote virtual computers with dissimilar remote copy patterns do not reside.

Abstract: One embodiment is a method for providing incremental backups for a source computing machine, the method including: (a) creating a first backup snapshot including a virtual machine (VM) snapshot of an initial copy of a source computing machine volume, wherein said VM snapshot includes a timestamp and a first redo log file; (b) reconfiguring and customizing said first backup snapshot to create a first bootable VM, writing changes associated with said reconfiguring and customizing into said first redo log file, then creating a first bootable snapshot including a VM snapshot of said first bootable VM, wherein said VM snapshot of said first bootable VM includes a timestamp for said first bootable VM and a redo log file; (c) performing an incremental update of said first backup snapshot or a subsequent backup snapshot, then creating a subsequent backup snapshot including a VM snapshot of said incremental update, wherein said VM snapshot of said incremental update includes a timestamp for said incremental update and

Abstract: The present invention provides a method for information recovery using a snapshot database, comprising the steps of: collecting first user log information for users of one or more user terminals; sorting effective information from the first user log information; storing the sorted effective information into the format of a snapshot database in accordance with period information; receiving recovery request information for the effective information from the user terminals; comparing and analyzing the second user log information and the effective information at the point of time where said recovery request information is received in accordance with said recovery request information; and recovering the second user log information to said effective information in accordance with the result of the analysis.

Abstract: A system for encapsulating configuration information in storage objects formatted for backup and restore comprises a processor coupled to a memory, where the memory stores instructions executable by the processor to implement a backup manager configured to generate backup versions of a plurality of storage objects (such as files or directories) of a source data set of a primary host. The backup manager may be configured to create an additional storage object that includes information collected from a designated information source in a first format, store the additional storage object within the source data set in a second format, and generate a backup version of the additional storage object.

Abstract: A method and apparatus for different embodiments of incremental garbage collection of data in a secondary storage. In one embodiment, a method comprises locating blocks of data in a log that are referenced and within a range at a tail of the log. The method also includes copying the blocks of data that are referenced and within the range to an unallocated segment of the log.

Abstract: Embodiments provide systems and methods for planning or monitoring system transformations. One embodiment of a method for planning or monitoring the transformation of a system includes developing one or more states, each state representing a system and associated with data structures representing entities comprising the system, wherein the states are ordered in a succession of states to form a scenario modeling the transformation of the system. States can be populated by reflecting one or more data structures or properties of data structures across one or more states. The method can further include collecting data associated with the system at intervals and reflecting the collected data across states. Data structures may be contained in a repository and collected data may be used to update the repository and data structures contained in the repository. A modeling tool may be utilized to display data structures in the repository according to different representations.

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: High performance, enterprise-level data protection system and method provides efficient block-level incremental snapshots of primary storage devices, and instant availability of such snapshots in immediately mountable form that can be directly used in place of the primary storage device. Related systems and applications are described, including an “Enterprise Image Destination” (EID) for backup images; a mirroring technique whereby a replacement physical primary facility may be created while working with a second storage unit as the primary source file system; and a technique for eliminating redundant data in backup images when multiple systems with partially common contents (e.g., operating system files, common databases, application executables, etc.) are being backed up. A number of examples showing “Fast Application Restore” (FAR) with the use of the invention are also provided.

Abstract: Methods and systems for rapid creation of copies of a mapped storage volume. A new copy of a mapped storage volume is created by copying the mapping table and updating meta-data associated with the new copy and any ancestral parents thereof. The physical blocks remain untouched when creating a new copy as does any meta-data associated with the physical blocks. Rather, reference meta-data associated with each physical block is updated only in response to processing of a write request to an identified block of an identified copy of the mapped storage volume. Thus copy creation is rapid as compared to prior techniques reliant on reference counters.

Abstract: In the HSM function, when supporting the file system snapshot function, a differential data volume is required for both a high-speed volume and a low-speed volume. Accordingly, when supporting the snapshot function by using a file system provided by the HSM function, a large amount of differential data volume is required. When the manager gives an instruction to acquire a snapshot, a snapshot management program executes snapshot acquisition processing to acquire a snapshot. In this processing, a snapshot reference relation building processing part copies a file storage location management table, and relates the file storage location management table to the acquired snapshot. Then, the snapshot reference relation building processing part checks a file that is migrated to a file system which does not have a differential data volume. Finally, the snapshot reference relation building processing part creates a link of the migrated file to the snapshot which is acquired previous time.

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: A system for efficient snapshot querying include: providing a first version value for each data in a history table, where the first version value indicates a beginning of a period in which the data is valid; providing at least a second version value for each data in the history table, where the second version value indicates an end of the period in which the data is valid; receiving a request for a version of a database; and retrieving the data with the first version value less than or equal to the requested version and the second version value greater than or equal to the requested version. By maintaining a history table with redundant version information, the system is able to provide efficient snapshot querying while also avoiding the overhead burden of conventional approaches. No aggregates, joins, or sub-queries are required to retrieve a snapshot.

Abstract: An apparatus and method define the concept of a “database breakpoint.” One or more conditions in the database are specified as a database breakpoint in a debug environment for debugging a computer program that accesses the database. When the database conditions exist, one or more debug functions may be performed with respect to the execution of the computer program. Examples of debug functions include halting execution of the computer program and halting operations to the database by other programs. With both the computer program and database halted, the user may then interrogate the database to determine its state, and may interrogate the program to determine its state. Database breakpoints greatly enhance the utility of a debugger by providing additional conditions for debugging a computer program that accesses a database.

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: A system for continuous data protection includes a storage device and a backup storage device. The continuous data protection procedure is performed as two parallel processes: creating an initial backup by copying a data as a file/directory from the storage device into the backup storage device, and copying the data to be written to the data storage as a part of a file/directory into the incremental backup. When a write command is directed to a file system driver, it is intercepted and redirected to the backup storage, and the data to be written in accordance with the write request, is written to the incremental backup on the backup storage. If the write command is also directed to a data (a file/directory) that has been identified for backup, but has not yet been backed up, the identified data (a file/directory) is copied from the storage device to the intermediate storage device.

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: There is provided a method of, and apparatus for, duplicating a logical drive. The method includes sequentially copying data from a source logical drive to a destination logical drive, and determining whether a write request to the source logical drive is received during the sequential copying. If so, the step of copying data in the write-requested data area to an additional storage area is carried out prior to executing the write request. It is further specified that the data in the write-requested data area is to be ignored and not copied during the sequential copying. The method further includes copying, upon completion of the sequential copying, data from the additional storage area to the destination logical drive.

Abstract: A system and method for a block based differencing algorithm which includes the ability to limit memory requirements regardless of source file sizes by splitting the source file into optimally sized blocks. The invention allows the blocks to be processed in any order allowing in-place operation. Further, the present invention allows a second stage compressor to match the compressor blocks to those used by the differencing algorithm to optimize compressor and decompressor performance.

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: Embodiments of the present invention provide methods, apparatuses, systems, and computer software products for data storage. A first copy of a logical volume is created. A second copy of the logical volume is created based on the first copy of the logical volume, such that the first and second copies are represented by respective first and second sets of pointers to physical storage locations in which data used by the copies is stored. Responsively to a corruption of at least part of the data that is used by the first copy. The first copy is restored from the second copy by replacing the first set with the pointers in the second set.

Abstract: A method, apparatus, and computer program product for setting and implementing a policy to compress the history of data on a temporal volume is described.

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: Workloads, as defined by customers, are tracked on an individual basis. This tracking enables a customer to identify the amount of resources consumed by a particular workload. The customer defines the workload to be tracked, and that workload is tracked using a Unit of Work value. The Unit of Work value ensures that there is an accounting for the resources attributable to that workload.