Pathname translation in a data replication system

• US 7,962,455 B2
• Filed: 12/15/2009
• Issued: 06/14/2011
• Est. Priority Date: 12/19/2005
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Erofeev, Andrei
• Primary Examiner(s): TO, BAOQUOC N
• Application Number:
  US12/638,933
• Publication Number:
  US 20100094808A1
• Time in Patent Office: 546 Days
• Field of Search: None
• US Class Current: 707/672
• CPC Class Codes: G06F 16/166 File name conversion
• CPC Class Codes: G06F 16/184 implemented as replicated file system
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Performing data management operations on replicated data in a computer network. Log entries are generated for data management operations of an application executing on a source system. Consistency point entries are used to indicate a time of a known good, or recoverable, state of the application. A destination system is configured to process a copy of the log and consistency point entries to replicate data in a replication volume, the replicated data being a copy of the application data on the source system. When the replicated data represents a known good state of the application, as determined by the consistency point entries, the destination system(s) may perform a storage operation (e.g., snapshot, backup) to copy the replicated data and to logically associate the copied data with a time information (e.g., time stamp) indicative of the source system time when the application was in the known good state.

Claims

1. A method for performing pathname translation in a data replication system, the method comprising:

processing a log entry from a log file associated with a source system with one or more computer processors, wherein the log entry identifies a data management operation associated with an inode wherein the inode is a child of one or more parent inodes;

obtaining path data for the inode from a database associated with the data replication system comprising a first short inode name and a parent inode identifier associated with the one or more parent inodes;

obtaining a second short inode name associated with the parent inode identifier from the database;

constructing from at least the first and second short inode names, path data comprising an absolute pathname that corresponds to the inode; and

storing the absolute pathname and the data management operation associated with the log entry on a destination system.

2. The method of claim 1, wherein the destination system uses the absolute pathname to replicate data associated with the data management operation.

3. The method of claim 1, further comprising storing in association with the inode, a short inode name and a name of a parent inode.

4. The method of claim 1, wherein the constructing is performed in an application space external to a kernel space of the source system.

5. The method of claim 1, additionally comprising generating the log entry in the log file with a filter driver.

6. The method of claim 1, wherein the inode is associated with a virtual file system.

7. The method of claim 1, wherein the inode and the one or more parent inodes are associated with a virtual file system.

8. The method of claim 1, additionally comprising populating a database with the path data.

9. The method of claim 8, wherein said populating comprises recording a static image of a file system of the source system.

10. A system for performing pathname translation during data replication in a computer network, the system comprising:

a log file of log entries associated with a source system;

at least a first log entry in the log file system identifying at least one inode on the source system and at least one data management operation, wherein the inode has one or more parent inodes; and

a module executing in one or more computer processors that is configured to obtain path data for the inode from a database associated with the data replication system comprising a first short inode name and a parent inode identifier for the one or more parent inodes, wherein the module is further configured to obtain a second short inode name associated with the parent inode identifier from the database and construct an absolute pathname from at least the first and second short inode names that corresponds to the inode, and wherein the module is further configured to store the data management operation and the absolution pathname on a destination system.

11. The system of claim 10, wherein the destination system uses the absolute pathname to replicate data associated with the data management operation.

12. The system of claim 10, further comprising a database configured to store a short inode name and a parent inode in association with the inode.

13. The system of claim 10, wherein the module constructs the absolute pathname in an application space external to a kernel space of the source system.

14. The system of claim 10, additionally comprising generating log entries in the log file with a filter driver.

15. The system of claim 10, wherein the inode is associated with a virtual file system.

16. The system of claim 10, wherein the inode and the one or more parent inodes are associated with a virtual file system.

17. The system of claim 10, wherein the module is further configured to populate a database with the path data.

18. The system of claim 17, wherein populating the database comprises recording a static image of a file system of the source system.