Abstract: A transactional file system wherein multiple file system operations may be performed as a transaction. An application specifies that file system-related operations are to be handled as a transaction, and the application is given a file handle associated with a transaction context. For file system requests associated with a transaction context, a file system component manages operations consistent with transactional behavior. Transactions over a network are facilitated. Remote files may be accessed within a transaction via a redirector protocol. A redirector on a client computer system communicates with an agent on a server computer system to relay and maintain transactional information on both systems.

Abstract: A method for restoring a file which has been deleted from a data storage system is described. A set of twin pointers is created by copying from the latest pointers in the active file system at a time of restoration. A new set of pointers is created. A pointer from the twin pointers is compared with a pointer from a snapshot of the active file system made at a time earlier than the deletion of the file. In response to a pointer from the snapshot pointing to a different data block than the pointer from the twin pointers, writing the snapshot pointer into the new set of pointers. Writing the new set of pointers into the active file system at the time of restoration to restore the file to the active file system.

Abstract: A restoration technique includes storing a collection of blocks having (i) a first baseline of blocks defining a file at a first time within a predefined window, (ii) older blocks, and (iii) newer blocks. The technique further includes providing a direction signal to restore the file at a particular time from the collection of blocks. The direction signal has an older direction value when the particular time is older than the first time and (ii) a newer direction value when the particular time is newer than the first time. The technique further includes forming, from the collection of blocks, a second baseline of blocks from the first baseline of blocks and additional blocks. The additional blocks are either (i) the older blocks or (ii) the newer blocks depending on the direction value. The second baseline defines the file at the particular time.

Abstract: A method for data recovery of a data set migrated from a first storage media to a second storage media, where the data set includes a header record and multiple control records interleaved with corresponding data blocks. The header record is examined to identify a number of control records and data blocks comprising the data set. Next, the control records and data blocks are examined in order, starting with an initial data block, until a first data block is identified due to its failure to match the attribute included in the associated control record. Then the control records and data blocks are examined in reverse order, starting with a last data block, until a second data block is identified due to its failure to match an attribute included in the associated control record. Lastly, each data block from the first data block to the second data block are set to a lost data value.

Abstract: An active device attaches a sequential number representing a notification number to update record information for recording an event that data is stored, then notifies a preliminary device of the update record information, and, accumulates the update record information. The active device again makes the notification. The preliminary device monitors the update record information of which the active device notifies and detects, based on regularity of the sequential numbers attached to the respective pieces of update record information, missing reception of the update record information. When detecting the missing reception of the update record information, the preliminary device makes a request for retransmitting the update record information and notifies of information about matching data stored in a first storage unit of the active device with data stored in a second storage unit of the preliminary device.

Abstract: A setup module saves disk signatures identifying cluster disks for at least one source volume to a device distinct from the cluster disks. A copy module copies data with a volume-level restore from at least one snapshot volume to the at least one source volume, overwriting the disk signatures identifying the cluster disks so that the cluster disks cannot be accessed. A reset module rewrites the saved disk signatures to the cluster disks.

Abstract: A system and method for examining content of a client computer operating system is provided. Layout information of data related to a data container stored within the client computer is retrieved, where the layout information is implemented in terms of native operating system semantic of the client computer. The layout information is transmitted to a storage system. The storage system reconstructs the layout information of the data container stored within the client computer in a shadow volume implemented in terms of native operating system semantic of the storage system.

Abstract: Log file amnesia detection is accomplished by associating a unique identifier with each record in a log file, where each record receives a unique log sequence number. Multiple time intervals are associated with the log file with different events triggering the beginning of a new time interval. The log file implementation marks the beginnings of these multiple time intervals with a unique identifier. Every time an event occurs that triggers a new time interval a new unique identifier is generated. This unique identifier will be associated with the records in the log file that are created thereafter until the next unique identifier gets generated, marking the beginning of a next time interval. Log file amnesia can be identified when a log client requests information about a record and then comparing the unique identifier and log sequence number of the record with all records in the log file.

Abstract: A storage management system is provided. The storage management system may includes a data collector configured to receive storage management information for storage. The storage manager includes an agent configured to collect storage management information for a storage object and to communicate the storage management information to the data collector. The storage management system includes a user interface configured to display the storage management information for the storage objects.

Abstract: A method, apparatus, and program product restore database data having dependencies or ordering sensitivities, or that incorporates a database index. Unresolved dependencies are identified in response to an attempt to restore data in a computer. The data restoration is deferred and the data is cached when it has an unresolved dependency. After the dependency is resolved, the data restoration is completed. The unresolved dependency may be based-on data that must be restored or created prior to completing restoration. Deferred data is cached in memory and tracked in a deferred operation table. Data that is deferred may be accessed so long as operations that access the underlying based-on data are denied.

Abstract: This invention involves tracking and backing all the information that a user generates on its computer devices (including embedded devices) in real time. The local user server records all user actions and gestures (via various means that include TV cameras). All of this information (user actions and saved files in a computer) is then sent to a remote server via the Internet. This remote server has a virtual map of all the embedded devices on a computer that the person uses. The remote server immediately starts to interpret the user's actions (including user gestures). In one implementation, the invention stores user actions that are related to data generation (e.g. actions that called some links where data is stored, or executed some programs that generated data). In another variant the remote server generates and downloads the same files that are downloaded on the local user computer devices.

Abstract: A method and apparatus for managing data loss due to policy violations in temporary files is described. In one embodiment, the method includes monitoring, by a client agent, information content on a client for violations of a policy. The method further includes determining, by the client agent, that a violation of the policy has occurred for content of a temporary file of an application. In one embodiment, the policy violation of the temporary file is correlated, by the client agent, with an original file of the application.

Abstract: Architecture that facilitates the restoration of a cluster database in a scalable way using backups (e.g., SQL database backups) and a partition rebuild mechanism to achieve a high level of partition level data consistency, even when restore fails on individual machines and/or machine failure occurs. The architecture restores replicas of the partitions in consideration that the backups may be created at different points and at different times. Optimized parallelism is achieved in restoring each database machine using local backups, which eliminates cross-machine network traffic. Thus, fast recovery of the distributed database can be accomplished on the order of hours over thousands of machines and terabytes of data.

Abstract: Atomic renaming and moving of data files, while permitting lock-free look-ups to the data files, is disclosed. A temporary record may be created within a hash chain encompassing a record for a data file and corresponding to a location of the data file within a computer file system. The temporary record is linked within the hash chain so that the temporary record points to the same records to which the record for the data file points. The record for the data file is renamed with a new name, and/or moved to a new location within the computer file system, and the temporary record is removed from the hash chain. Before the temporary record is removed, look-ups of the data file resolve to the temporary record, the temporary record causing the look-ups to wait until the record for the data file has been renamed and/or moved and the temporary record removed.

Abstract: A file management method of a server is implemented on a Linux operating system of the server. The method includes the steps of determining if there is a file deleted; when the result is yes, searching for an actual disk block location at which the deleted file is originally located and then recovering the deleted file; moving the recovered file to a predetermined location; and changing an access privilege level of the Linux operating system.

Abstract: Techniques provide a file plan including a plurality of containers, wherein each container is capable of providing management information for record information objects assigned to the container, wherein the record information objects represent documents, wherein one of the containers points to a physical record. An electronic record associated with the physical record is stored. The physical record is automatically associated with the electronic record by updating the file plan.

Abstract: Tokens corresponding to data units written to a rewritable file system are stored, where an ordering relationship is maintained among the tokens, where the ordering relationship is such that a first token corresponding to a first data unit is of a lesser numerical value in comparison to a second token corresponding to a second data unit, and where the first data unit is written at an earlier point in time in comparison to the second data unit. The rewritable file system is reverted to an indicated point in time based on the ordering relationship that is maintained among the stored tokens.

Abstract: The present invention is a recording method for recording, data to a disc shaped record medium 10 corresponding to a hierarchical file system, the method comprising the steps of recording management information for managing a hierarchical structure of the file system to a particular area 16 of the disc shaped record medium, treating an unused area of the particular area 16 as a particular file, and recording information with respect to an initial location and an initial length of the particular file and information with respect to a current location and a current length of the particular file to the particular area 16.

Abstract: A reservation management system includes at least one processing node that includes a memory and a processor. The at least one processing node further includes a set of reservation processing and transaction modules that manage and process reservation requests and inquiries. At least one general purpose database is communicatively coupled to the at least one processing node. The at least one general purpose database includes a set of pre-allocated tables of fixed length records. At least one persistent storage device is communicatively coupled to the at least one processing node. The general purpose database persistently stores the set of pre-allocated tables of fixed length records on the at least one persistent storage device.

Abstract: Disclosed herein is data replication and recovery method in an asymmetric clustered distributed file system, which divides the storage space of a data server into main partitions and sub-partitions, and separately manages main chunks and sub-chunks in the main partitions and the sub-partitions, thus efficiently processing chunk replication and recovery. In the disclosed method, when a failure occurs in a data server in an asymmetric clustered distributed file system, a failed partition is reported to all data servers including other partitions of a volume to which the partitions of the failed data server belong. Accordingly, other data servers can simultaneously perform the recovery of chunks using the information of their own main chunks and sub-chunks. As a result, when a failure occurs in a data server, all related data servers can simultaneously participate in data recovery, thus more promptly and efficiently coping with the failure.

Abstract: This invention provides a system and method for managing backup and restore operations on a storage system, typically between source storage system and destination storage system using a backup management client that employs a version of the Network Data Management Protocol to interface with the destination file server and generate an “index” of data structures (such as directories and files) from directly from scanning the trees of PCPIs stored on the destination. The management client includes a command line interface for entry of instructions by a user or application and a web-based user interface and allows the index to be displayed as a series of web pages on a graphical user interface. The index can be browsed and selected data structures can be restored to a source filer/file server as desired. All back-ups/PCPIs can be contemporaneously browsed, allowing greater flexibility in selecting a best backup image to restore.

Abstract: Various technologies and techniques are disclosed for supporting parallel nested transactions in a transactional memory system. For example, pessimistic reads are supported. A pessimistic duplication detection data structure is created for a parallel nested transaction. An entry is made into the data structure for each pessimistic read in the parallel nested transaction. When committing the parallel nested transaction, new pessimistic read locks are passed to an immediate parent, and an entry is made into a separate pessimistic duplication detection data structure of the immediate parent with synchronization between sibling transactions. The pessimistic duplication detection data structures can also be used for upgrades from pessimistic reads to write locks. Retry operations are supported with parallel nested transactions. Write abort compensation maps can be used with parallel nested transactions to detect and handle falsely doomed parent transactions.

Abstract: A three tiered data synchronization system including a client, an enterprise data server, a synchronization server, and a pre-fetch data store. The client can have an associated client data store and the enterprise data server can have an associated server data store. The synchronization sever can intermittently and bidirectionally synchronize data within the client data store with data within the server data store. The pre-fetch data store can maintains data specific to synchronization requests that is used by the synchronization server when performing synchronization operations responsive to detected synchronization requests. The data specific to synchronization request used by the synchronization server is stored within the pre-fetch data store before the corresponding synchronization requests are detected by the synchronization server.

Abstract: A system and method for optimizing a storage system to support short data object lifetimes and highly utilized storage space are provided. With the system and method, data objects are clustered based on when they are anticipated to be deleted. When an application stores data, the application provides an indicator of the expected lifetime of the data, which may be a retention value, a relative priority of the data object, or the like. Data objects having similar expected lifetimes are clustered together in common data structures so that clusters of objects may be deleted efficiently in a single operation. Expected lifetimes may be changed by applications automatically. The system automatically determines how to handle these changes in expected lifetime using one or more of copying the data object, reclassifying the container in which the data object is held, and ignoring the change in expected lifetime for a time to investigate further changes in expected lifetime of other data objects.

Abstract: A DBA may pre-generate database recovery jobs on a convenient schedule at a local site, then recover a database at a disaster recovery site. Archive log files for the database that are generated in the interim between recovery job generation and recovery job execution are automatically incorporated into the recovery job when it executes, extending the recovery point closer to the time of the disruption that triggered the need or desire for recovery.

Abstract: An approach is provided for configuring a content object. A service receives a request, from a user, to configure a content object at a device. The service then causes, at least in part, a change to a state of the content object based on the request. The content object is related to a content playlist, and a configuration of the content object is stored at a host.

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

Abstract: Database management systems and program products that exploit time dependent sequential database management system processes to ensure presentation of the same data or view to one or a plurality of users through sequencing asynchronous database management operations such as recovery and replication. Sequencing is accomplished through the use of entries in sequential logs, including transaction logs, recovery logs, and other data recovery tools and applications. Uses include managing data migration and data replication.

Abstract: One embodiment is a method that stores user interface events and file system events to capture text snippets visible on an output device. Similar text snippets are merged into a context graph that is used to locate a document from a query.

Abstract: A method for assisting an administrator to identify files suspected of causing instability on a personal computer comprises periodically creating file content sharing logs concurrently with archiving files of a plurality of personal computers by de-duplicating, when a notification is received regarding instability of a personal computer, then analyzing archive file content sharing log of the personal computer made immediately after receiving the notification for unique system and program files, missing files and newly installed files to generate an instability report. A missing or corrupted file can be restored back on the unstable personal computer by performing a backup restore operation on the unstable personal computer.

Abstract: In one embodiment, there is provided a method for a media storage device to manage digital content. The method comprises determining if there is digital content to be categorized into one or more galleries; automatically categorizing said digital content into the one or more galleries; and for digital content categorized into a gallery with an auto-publish flag, sending at least one of said digital content and a derivative form of said digital content to a server.

Abstract: An extensible markup language document management method includes: receiving a document recovery request from a user; and recovering a version of the document as required by a user from the current version of the document, in accordance with the change records for the document. An extensible markup language document management system includes: a rollback control module, adapted to recover a version of a document as required by a user from the current version of the document, in accordance with change records for the document, upon receiving a document recovery request from the user.

Abstract: Systems, methods and articles of manufacture are disclosed for synchronizing a primary data system with an auxiliary data system that processes data for the primary data system. In one embodiment, how current the primary data system and the auxiliary data system are may be determined. Requests sent from the primary data system that were not processed by the auxiliary data system may be determined. The requests may be resent to the auxiliary data system for processing.

Abstract: A computer-implemented method, apparatus, and computer-usable program code for preserving file locks while moving a software partition from an origination network file system client data processing system to a destination network file system client data processing system is provided. A request for a file is received. A determination is made as to whether the request is for a file that is within a software partition. Responsive to a determination that the request is for a file within a software partition, a determination is made as to whether the request is a lock request. Responsive to a determination that the request is a lock request, a determination is made as to whether the software partition is being restarted. Responsive to a determination that the software partition is being restarted, the lock request is blocked from being sent to a remote network file system server.

Abstract: Exemplary embodiments provide a computer implemented method, apparatus, and computer-usable program code for moving a software partition from an origination network file system client data processing system to a destination network file system client data processing system. Responsive to receiving a request to perform a checkpoint operation on a software partition, network file system related mount information for the software partition is gathered. Determined ports of a network are unblocked. Unwritten data on the origination network file system client data processing system is synchronized with a remote network file system server. The network is re-blocked. A checkpoint file is generated and stored. The checkpoint file is sent to the destination network file system data processing system.

Abstract: The present invention relates to a system for restoring a file from a snapshot, where a version of the file exists in both an active file system and the snapshot. A twin inode is created in the active file system and comparisons are made between block pointers of the twin inode and the snapshot. If there is a match, the block pointer of the twin inode is moved to the active file system. If there is not a match, a determination is made whether the snapshot block pointer exists in the active file system. If the snapshot block pointer does not exist in the active file system, it is copied to the active file system. If it does exist, then the actual data block pointed to by the snapshot block pointer is copied to the active file system. In this way, a file may be restored without the need to always copy every individual data block or inode from the snapshot.

Abstract: To reduce operational and management costs during normal operations while recovering a database without loss and maintaining on-line performance on a site. A first system includes a primary storage system (103) that stores a DB (107) and a main computer (100) that executes a primary DBMS (101), which provides a DB. A second system includes a secondary (113) that receives from the primary storage system (103) a copy of a log, which shows update differences of the DB (107), and stores a secondary DBMS (117), and a subset (500) that recovers the secondary DB (117) according to the log that is copied from the primary storage system (103). When a failure occurs in the first system, the first system is switched to the second system. A second computer (110) that executes a second DBMS (111) is added to the second system, and the secondary DB (117) that is recovered or is being recovered in the subset (500) is taken over to the second computer (110).

Abstract: A method and apparatus for maintaining an amount of reserve space using virtual placeholders. In one embodiment, a method of using placeholders for log files to maintain an amount of reserve storage space comprises determining a first required log file, wherein the first required log file is to be used to recover a database volume, generating at least one placeholder for representing at least one required log file in a log volume and storing the first required log file and the at least one placeholder in a portion of the log volume, wherein the at least one placeholder is used to control a size of the portion of the log volume.

Abstract: Methods and apparatus for generating a report from hierarchically formatted data are disclosed. First, a data source including one or more files having a hierarchical file format is identified, where each of the files includes one or more data elements. A relational database model is obtained, where the relational database model includes one or more virtual tables, each of the virtual tables including one or more virtual columns. The relational database model is then mapped to the hierarchical file format. A query may be obtained using the virtual relational database. Data is then obtained from the virtual relational database corresponding to the query, thereby enabling a report including the data to be generated.

Abstract: Methods and systems for recovering data utilize a command line interface of a data-processing system, run by an operating system such as Linux, Unix, DOS, Windows, Mac and the like, to recover and manage inadvertently deleted data. Desired data such as files, folders, and the like can be initially identified from a command line interface. The desired data can then be automatically saved in a memory location of the data-processing system, in response to identifying the desired data from the command line interface. The data can then be automatically recovered from the memory location of the data-processing system for display within the command line interface, if the desired data is inadvertently deleted. Additionally, a user can be permitted to specify a plurality of recycling rules presented through a graphical user interface dialog or other graphical user interface device.

Abstract: A cluster manager is configured to manage a plurality of copies of a mid-tier database as a mid-tier database cluster. The cluster manager may concurrently manage a backend database system. The cluster manager is configured to monitor for and react to failures of mid-tier database nodes. The cluster manager may react to a mid-tier database failure by, for example, assigning a new active node, creating a new standby node, creating new copies of the mid-tier databases, implementing new replication or backup schemes, reassigning the node's virtual address to another node, or relocating applications that were directly linked to the mid-tier database to another host. Each node or an associated agent may configure the cluster manager to behave in this fashion during initialization, based on common cluster configuration information. Each copy of the mid-tier database may be, for example, a memory resident database. Thus, a node must reload the entire database into memory to recover a copy of the database.

Abstract: A quorum-based server power-down mechanism allows a manager in a computer cluster to power-down unresponsive servers in a manner that assures that an unresponsive server does not become responsive again. In order for a manager in a cluster to power down servers in the cluster, the cluster must have quorum, meaning that a majority of the computers in the cluster must be responsive. If the cluster has quorum, and if the manager server did not fail, the manager causes the failed server(s) to be powered down. If the manager server did fail, the new manager causes all unresponsive servers in the cluster to be powered down. If the power-down is successful, the resources on the failed server(s) may be failed over to other servers in the cluster that were not powered down. If the power-down is not successful, the cluster is disabled.

Abstract: One new file and one old file are sequentially compared from the heads of the files on a predetermined data unit basis. If a data match is found, transfer information showing a position and a data length of the old file is output. If a data mismatch is found by the sequential comparison, the old file is searched in both directions from the data position where the mismatch had been found in the old file, thereby finding a portion which matches with the data of the new file. If the matching portion can be found, shift information up to the matching portion on the old file is output. If the matching portion cannot be found, new data is added to transfer replacement information showing a length of data of the mismatching portion of the old file at a position until the matching portion can be found, and the resultant transfer replacement information is output.

Abstract: The present invention provides a centralized management mode backup disaster recovery system, which comprises: a control console (104) for performing centralized control on a data container (105), a backup process module (103), storage medium (101), and a standby machine (102) through respective control operations; a production server (108) responsible for controlling and managing data circulation between the production server and the storage medium in unit of data blocks; a backup process module (103) for backing up data to storage space allocated for the production server (180) by the storage medium (101) through an mirror technique and a synchronous or asynchronous technique or any other backup methods; the storage medium (101) for storing data and allocating a logic unit (200) to the production server (108) for data storage; the standby machine (102) for storing system data of the production server (108) and completing automatic running and setting of the standby machine (102) through the control console

Abstract: A method is provided which enables to know a location of copied document data without the use of a server or others. Document data that is data used for reconstructing a document is managed by combining, in one document object, the document data along with relationship information for identifying other document data generated by reproducing the document data. Likewise, when a reproduction process is performed, the other document data is managed by combining, in one document object, the other document data along with relationship information for identifying the reproduction.

Abstract: Systems and methods for facilitating more efficient timestamping in a lazy timestamping transaction time database environment are described herein. A recovery log component can store timestamp information of a transaction in a commit record of the transaction, wherein the commit record of the transaction is included in a recovery log. A volatile reference count component can update reference count data of the transaction in a volatile timestamp table to reflect a number of records of the transaction that do not persistently include timestamp information. Further, a checkpoint component can update timestamp information for a batch of transactions, wherein the timestamp information is updated in a record of the persistent timestamp table to ensure that the timestamp information persists in the record of the persistent timestamp table before the commit record of the transaction that contains the transaction's timestamp information is deleted from the recovery log.

Abstract: A first code-format converting unit extracts data from database management apparatuses that manage databases having same contents, and converts a code format of the extracted data into a common code format. A mismatch-resolving-data generating unit generates mismatch-resolving data for resolving a data mismatch between the database management apparatuses, from the data with the code format converted. A second code-format converting unit converts a code format of the generated mismatch-resolving data into a code format corresponding to the databases. A database updating unit reflects the mismatch-resolving data with the code format converted to the databases.

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 Networked Data Shadowing System comprises a memory module that is connected to a plurality of monitored computer systems via an existing communication medium to store the shadowed data. The memory module includes one or more memory devices for data storage as well as software, including a control software component that is automatically installed on the monitored computer systems when the monitored computer system is first connected to the memory module, as well as associated module software for maintaining a record of the data stored on the memory devices and controlling the operation of the memory devices. The Networked Data Shadowing System operates autonomously and achieves a significant amount of data storage efficiency by implementing a “data de-duplication” process to avoid storing multiple copies of the same files.

Abstract: A system, method, and computer program product for improving physical lock acquisition for database transaction logs are described herein. In an embodiment, the method operates by receiving a request for a transaction log page and determining whether a requested log page is newly-allocated or already exists. A determination is made regarding whether the last log page is being modified. A physical lock is taken on the requested log page when it has been determined that the requested log page is not newly-allocated and that the last log page is not being modified. Operations on the last log page are synchronized without a physical lock when it is determined that the requested log page is newly-allocated or that the last log page is being modified.