Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
1999-07-16
2003-01-28
Alam, Hosain T. (Department: 2172)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000, C707S793000, C707S793000, C707S793000, C707S793000, C711S161000, C711S162000
Reexamination Certificate
active
06513051
ABSTRACT:
TECHNICAL FIELD
The invention relates generally to computer systems and data storage, and more particularly to the backing up and restoring of files of a file system.
BACKGROUND OF THE INVENTION
The contents of a file of a file system may be identical to the contents stored in one or more other files. While some file duplication tends to occur on even an individual user's personal computer, duplication is particularly prevalent on networks set up with a server that centrally stores the contents of multiple personal computers. For example, with a remote boot facility on a computer network, each user boots from that user's private directory on a file server. Each private directory thus ordinarily includes a number of files that are identical to files on other users'directories. As can be readily appreciated, storing the private directories on traditional file systems consumes a great deal of disk and server file buffer cache space.
Techniques that have been used to reduce the amount of used storage space include linked-file or shared memory techniques, essentially storing the data only once. However, when these techniques are used in a file system, the files are not treated as logically separate files. For example, if one user makes a change to a linked-file, or if the contents of the shared memory change, every other user linked to that file sees the change. This is a significant drawback in a dynamic environment where files do change, even if not very frequently. For example, in many enterprises, different users need to maintain different versions of files at different times, including traditionally read-only files such as applications. As a result, linked-file techniques would work well for files that are strictly read-only, but these techniques fail to provide the flexibility needed in a dynamic environment.
Additional problems arise any time that a distinct file is linked to its data rather than having the file metadata and actual data treated as a whole. For example, when dealing with linked files, the file data may be lost if a link to the file data is backed up, but not the data itself. As can be readily appreciated, such a situation is unacceptable in critical data backup and retrieval situations, but nonetheless may occur if the user does not know that the backed-up link is actually distinct from the data. On the other hand, if the data is automatically backed up for each link, then the amount of storage space needed to make the backup may be far larger than the amount of space that the links and data actually occupy on the machine being backed up. For example, a user may overflow a backup storage device if roughly 200 megabytes of space is needed to back up the source data for two links, each link pointing to the same 100 megabytes of file data, (i.e., the links and data occupy approximately 100 megabytes at the source). Similarly, when restoring, the amount of data on the storage device may not correspond to the amount the user expects to restore. For example, if the 200 megabytes did fit on the backup storage device, the user backed up what appeared to be 100 megabytes and thus expects that the restore program will put back 100 megabytes, not 200 megabytes. In sum, there has heretofore not been a way to properly handle the backing up and restoring of files having their data stored in a single instance representation thereof.
SUMMARY OF THE INVENTION
Briefly, the present invention provides a method and system for backing up and restoring single instance files including link files and common store files pointed to by those link files. The method and system, which may be implemented in an interface such as in a dynamic link library, receive information corresponding to a link file, such as via a function call from a backup application, and determine whether the link file has common data corresponding thereto already identified for backup. If not, the interface identifies the common data (e.g., returns a common store filename) to back up. A data structure may be used to track which common data has already been identified to the backup application. In this manner, one, but only one copy of the common data will be identified for backup.
The interface may also receive function calls specifying a link file from a restore application, whereby the interface determines whether common data corresponding to the link file needs to be restored. To this end, the interface identifies the common store data (e.g., via a common store filename) when the common data has neither been previously identified to the restore application nor is already present on the volume. A data structure may be used to track whether common data has already been identified to the backup application, and/or is known to be present on the volume. In this manner, one, but only one copy of the common data will be identified for restore, and only if the common data is not already present on the volume.
Other advantages will become apparent from the following detailed description when taken in conjunction with the drawings, in which:
REFERENCES:
patent: 5410667 (1995-04-01), Belsan et al.
patent: 5706510 (1998-01-01), Burgoon
patent: 5778384 (1998-07-01), Provino et al.
patent: 5778395 (1998-07-01), Whiting et al.
patent: 5907673 (1999-05-01), Hirayama et al.
patent: 5918229 (1999-06-01), Davis et al.
patent: 6185574 (2001-02-01), Howard et al.
patent: 0 774 715 (1997-05-01), None
patent: WO 99/09480 (1999-02-01), None
patent: WO 99/12098 (1999-03-01), None
patent: 99/12098 (1999-03-01), None
patent: WO 99/21082 (1999-04-01), None
LaLonde, Ken, “Batch daemon—README”, UNIX Batch Command, University of Toronto, pp. 1-3 (Feb. 27, 1997), ftp://ftp.cs.toronto.edu/pub/batch.tar.z printed Dec. 8, 2000.
Steere et al., “A Feedback-driven Proportion Allocator for Real-Rate Scheduling”,Third Symposium on Operating Systems Design and Implementation(OSDI '99), USENIX Association, pp. 145-158 (1999).
Copy of International Search Report from corresponding PCT Application No. PCT/US00/1890 mailed Nov. 24, 2000.
Bolosky William J.
Cutshall Scott M.
Alam Hosain T.
Hwang Joon Hwan
Law Offices of Albert S. Michalik PLLC
Microsoft Corporation
LandOfFree
Method and system for backing up and restoring files stored... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and system for backing up and restoring files stored..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for backing up and restoring files stored... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3060377