Techniques for establishing a file system that exposes a virtual file system for backup operations

• US 8,935,209 B2
• Filed: 09/14/2012
• Issued: 01/13/2015
• Est. Priority Date: 05/11/2009
• Status: Expired due to Fees

• Current Assignee: Micro Focus Software, Inc. (Open Text Corporation)
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Oza, Dhairesh
• Primary Examiner(s): NGUYEN, PHONG H
• Application Number:
  US13/619,818
• Publication Number:
  US 20130013565A1
• Time in Patent Office: 851 Days
• Field of Search: 707/640, 707/646, 707/661, 707/800, 707/822, 707/831, 707/825, 719/318
• US Class Current: 707/640
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1466 to make the backup process non-disruptive
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Techniques for establishing a files system that exposes a virtual file system for backup operations are presented. Changes to files of a file system are maintained separately or collected and presented as a VFS. The VFS is then used to perform backup operations. Moreover, the files identified in the VFS can be customized based on search parameters, criterion, and/or criteria supplied by a user or supplied as parameters to backup and VFS mount operations.

Claims

1. A method implemented in a non-transitory computer-readable storage medium as executable instructions that process on one or more processors to perform the method, comprising:

exposing, by the processors, a list of the files having changes in a file system as an independent Virtual File System (VFS) that is used to perform a backup operation on the list of files that changed, the VFS used as a single addressable interface that bridges different file systems, wherein exposing further includes detecting event notifications at a kernel level of the OS for each of the changes, wherein detecting further includes using a File System in User Space (FUSE) module to track the event notifications from the kernel level; and

acquire, by the processors, metadata by querying inodes for the files, the metadata including data changes of each file and an increase or decrease in file size for each file after the changes.

2. The method of claim 1, wherein using further includes acquiring the VFS from the FUSE module.

3. The method of claim 1, wherein exposing further includes identifying some of the changes to some of the files as one or more changes to:

security, ownership, and name descriptors.

4. The method of claim 1, wherein exposing further includes identifying some of the changes to some of the files as one or more changes to primary data associated with those files.

5. The method of claim 1, wherein exposing further includes identifying some of the changes to some of the files as specific changes to specific metadata associated with those files and primary data associated with those files.

6. The method of claim 1, wherein exposing further includes selectively modifying the VFS.

7. The method of claim 1 further comprising, backing up, by the processors, the list by mounting the VFS.

8. A method implemented in a non-transitory computer-readable storage medium as executable instructions that process on one or more processors to perform the method, comprising:

modifying, by the processors, a file system (FS) to track changes to files as a separate linked list of inodes that form a virtual file system (VFS) that is mounted as a separate file system, and obtaining the changes by querying the files;

backing up, by the processors, the VFS incrementally and differentially for the linked list of inodes; and

providing, by the processors, copy-on-write operations for the backup operation processed on the VFS inodes.

9. The method of claim 8 further comprising, regularly receiving, by the processors, updates to the linked list of inodes from the FS.

10. The method of claim 8, wherein modifying further includes configuring the FS to track the changes as modifications to metadata for the files or as modifications to primary data for the files.

11. The method of claim 8, wherein backing up further includes presenting the VFS as a read-only restricted view VFS.