Oracle International Corporation

David Akers

Diane Lebel

Angelo Pruscino

Frederick S Glover

Timothy Mark

Teng Wang

Fred S Glover

James Beltz

Brian Tsao

In an embodiment, a computer stores source files and source clone files in a source filesystem. The source clone files are shallow copies of the source files, which initially share the same data blocks as the source files. A source file or a source clone file may eventually be modified, where some of the shared blocks are replaced by modified blocks. In a first phase, all data blocks of all source files that are not clones are replicated to a standby filesystem. A second phase compares each clone file on the source filesystem with its base file to detect a set of differed blocks. The second phase copies the differed blocks into the standby filesystem and, in the standby filesystem, applies the differed blocks to a corresponding clone file. Efficiency of keeping the standby filesystem synchronized with the source filesystem is improved by transferring, from the source filesystem to the standby filesystem, only one copy of only data blocks that are modified.

Clone-aware approach for space and time efficient replication

A method, system, and computer program product for file storage defragmentation on a cluster of nodes. The method for self-governed, contention-aware scheduling of file defragmentation operations commences by calculating a score for candidate files of a storage volume, where the score is based on a fragmentation severity value. The process proceeds to determine an amount of contention for access to a candidate file (e.g., by accessing the candidate file to record the amount of time it takes to obtain access). If the fragmentation severity value and the amount of contention suggestion a benefit from defragmentation, then the method initiating defragmentation operations on the candidate file. The method delays for a calculated wait time before performing a second defragmentation operation. Real-time monitors are used to determine when the contention is too high or when system utilization is too high. Only files that have ever been opened are considered candidates for defragmentation.

Self-governed contention-aware approach to scheduling file defragmentation

Systems, methods, and other embodiments associated with selective tag-based file backup and recovery are described. One example method includes selectively tagging a file for inclusion in a snapshot-based backup image by associating a tag with the file. The associating may include encoding file metadata with a tag. The method may include selectively adding a file to the backup image upon determining that the file has experienced a write event and that the file is associated with a tag. The method may also include receiving a request to provide a recovery file from the backup image and selectively providing the recovery file upon determining that the recovery file is associated with a recovery tag specified in the request.

Tag based backup and recovery

Growing community of inventors

Merrimack, NH, United States of America

David Akers