Abstract: A method, system and program product for centrally managing computer backups are provided. Specifically, backup data is received to a backup system from at least one computer system in one or more formats. Once received, the backup data is converted from the format in which it was received to a central format, and then communicated to a central system. Once received by the central system, the converted backup data can be analyzed, and reports based thereon can be generated.

Abstract: Information, such as files received from a client, etc., is stored in a storage system, such as a content addressable storage system. A file server receives data from a client and chunks the data into blocks of data. The file server also generates metadata for use in forming a data structure. The blocks of data are stored in a block store and a copy of the data blocks and the metadata are locally cached at the file server. A commit server retrieves the metadata. In at least one embodiment, the metadata is retrieved from an update log shared between the file server and the commit server. Based on the retrieved metadata, the commit server generates a version of a data structure. The data structure is then stored at the block store.

Abstract: A transaction safe file system uses two sets of file allocation tables and bitmap images to perform file modifications on one of the sets while the other set remains a last known good set. After a modification is complete, a pointer is changed to the newly modified set, and the newly modified set becomes the last known good set. The sets are then synchronized. The file allocation table is used to define cluster chains while the bitmap image is used to determine if a cluster is free or not. In some operations, only the bitmap image may need to be manipulated. The file system may be used in a transaction safe mode as well as a non-transaction safe mode.

Abstract: Methods and apparatuses for configuring logging of a deployment of an enterprise component are described herein. In one embodiment, in response to a request for deploying an enterprise component, a logging configuration process extracts logging configuration information from a logging configuration file associated with the enterprise component and configures the logging for the respective enterprise component being deployed. The logging configuration file is designed exclusively for configuring logging of the enterprise component. Thereafter, the deployment information of the enterprise component is logged based on the extracted logging configuration information when the enterprise component is deployed. Other methods and apparatuses are also described.

Abstract: A log collection utility (LCU) operable in a storage area network (SAN) to identify the various types of log files generated in the SAN, compute the location of each of the log files, and collect the log files for consolidation and analysis in a common repository. A designator file enumerates log files for collection. The LCU generates a discovery script for each host, and the hosts generate an identity of each of the log files via execution of the discovery script. The LCU generates a collection script operable to gather the each of the log files. The LCU thus gathers a plurality of log files generated by dissimilar applications and nodes in the SAN via a declarative mechanism that specifies the types of log files via a log file designator, and generates executable scripts that collects the log files in a manner that is agnostic to operating systems, platforms, and directory structures.

Abstract: A system and a method for managing log information. The system includes an input module that receives log information on a data renewal and a control module that stores a renewed data image based on the received log information when a page area where the renewed data exists is a hotspot, wherein the control module manages a hotspot control list (HSCL) including hotspot managing information and address information on a storage area in which the renewed data image is stored.

Abstract: A generational journaling data store can synchronize write accesses so that previous generation masters do not corrupt current generation journals. A master maintains a journal and accesses a data store on behalf of clients. When a master disappears a new master must take its place to ensure reliable and continuous access to the data store. Without generations, a previous master can reappear and corrupt journals and data stores. With generations, a newer generation journal can not be corrupted by a previous generation master.

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: The present invention provides a method for generating a backup of a database file that is suitable for a hard recovery operation. A snapshot of the database file is generated and the log and/or patch files associated with the database are stored in a backup location. Additionally, the header and/or footer information of the database is stored, thereby enabling a restored snapshot of the database to be converted into a file suitable for a hard recovery operation.

Abstract: This invention is a system and method for assisting the performance of incremental copying of data in a data storage environment and includes a tracking mechanism. In one embodiment, the tracking mechanism is implemented in such a way that it is able to track changes while allowing access to production data by carrying out unique methodology. In other embodiments, implementations include a system, a computer program product, or an apparatus, wherein each embodiment is configured for carrying out the steps involved in the methodology.

Abstract: One or more random access-type storage devices comprise a volume group and a journal volume. The volume group contains a volume pair configured from a primary volume and a secondary volume. Whenever data is received from a host device, this received data is written in the primary volume, a journal containing the write sequence of the data and the data is produced, and the journal is written in a journal volume. A plurality of journals accumulated in a journal volume are written in a sequential access-type storage device. Based on the write sequence recorded in each of the plurality of journals recorded in the sequential access-type storage device, the data of the journals is restored to the primary volume for storing the data and to a secondary volume from which the volume pair is configured.

Abstract: A log structured content addressable deduplicated data storage system may be used to store deduplicated data. Data to be stored is partitioned into data segments. Each unique data segment is associated with a label. The storage system maintains a transaction log. Mutating storage operations are initiated by storing transaction records in the transaction log. Additional transaction records are stored in the log when storage operations are completed. Upon restarting an embodiment of the data storage system, the transaction records from the transaction logs are replayed to recreate the state of the data storage system. The data storage system updates file system metadata with transaction information while a storage operation associated with the file is being processed. This transaction information serves as atomically updated transaction commit points, allowing fully internally consistent snapshots of deduplicated volumes to be taken at any time.

Abstract: Systems and methods are presented that facilitate automatic database backup and restore for databases resident in personal computing devices, and which are transparent to a user, utilizing database page mirroring. Modifications to a data page in a data file can be validated and written to a backup, or mirror, database and then subsequently written to an original database after a predetermined time. An I/O latch on a mirrored data page can be limited to a duration of a single I/O write operation to facilitate sequential data page writing to each of the databases while mitigating potential for both databases to be written simultaneously, which can detrimentally affect data quality during a recovery operation.

Abstract: A backup is performed by a client at a time when a backup server is unable to process the backup. The client maintains a cache including a root tag vector and hash entries. The client begins a backup by writing the root tag vector to a journal file and breaking files into pieces. For each piece, the client performs a hash and compares the resulting hash to entries in the cache. If the hash does not match any entries, the client records a request in the journal file to add the corresponding piece of data to an archive. After completing the backup, the journal file can be sent to the server. Before processing the journal file, the server validates the root tag vector. If the root tag vector is valid, the server processes each of the requests to add data. Otherwise, the server discards the journal file.

Abstract: Methods and systems of providing a rating of a recruiter are disclosed herein. A plurality of job listings to be posed is received from a recruiter. One or more modifications of at least one of the plurality of job listings are received within a period of time. A modification rate indicative of a rate at which a recruiter modifies job listings is calculated. The modification rate can be calculated by dividing the number of the one or more modifications by the number of the plurality of job listings posted by the recruiter. A recruiter profile can be tagged with a high modification indicator if the calculated modification rate is higher than a predetermined modification threshold.