Nonintrusive update of files

• US 6,560,614 B1
• Filed: 11/12/1999
• Issued: 05/06/2003
• Est. Priority Date: 11/12/1999
• Status: Expired due to Term

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: XOsoft Inc. (Broadcom, Inc.)
• Inventors: Shtilman, Leonid, Kogan, Leonid, Zakharov, Michael, Barboy, Dimitry
• Primary Examiner(s): Homere, Jean R.
• Assistant Examiner(s): Wassum, Luke S.
• Application Number:
  US09/439,980
• Time in Patent Office: 1,271 Days
• Field of Search: 707/200-202, 707/203, 707/8, 707/204, 717/168-173
• US Class Current: 707/611
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: Y10S 707/922 Communications
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Updating a file which is currently open is accomplished by allowing current users to continue accessing the original file while redirecting new users to an updated version. When user activity permits, the updated version is substituted for the original file. An auxiliary program detects when a server application attempts to access an out-of-date file version and redirects the access call to the up-to-date file version. When no users are accessing the out-of-date file version, the up-to-date version of the file is substituted thereby allowing access to the most recent file version without creating errors for users who are accessing the older file version. New updates of files are transferred from a master site to a temporary location, accessible intermediate location, and finally to a permanent location.

Claims

1. A method of updating a subject file stored in a target location in computer storage, comprising the following steps:

recognizing if an updated version of said subject file exists;

copying said updated version of said subject file to a temporary location;

determining if said subject file is presently being accessed to determine a use status;

if said subject file is not in use, copying said updated version from said temporary location to said target location;

if said subject file is presently in use, transferring said updated version from said temporary location to an intermediate location;

redirecting new requests for said subject file to said updated version located in said intermediate location, and

wherein said determining step is repeated until said updated version is copied into said target location, said transferring to said intermediate location step occurring only during an initial determination of said use status and skipped for subsequent iterations of said determining step.

2. A method of updating a subject file as per claim 1, wherein access to said subject file is denied during transfer from said intermediate location to said target location.

3. A method of updating a subject file as per claim 2, wherein said denying step comprises a locking function of shared memory containing said intermediate location.

4. A method of updating a subject file as per claim 1, wherein said recognizing step further comprises a monitoring thread, said copying step further comprises a working thread, and copying to said temporary location step further comprises a transfer thread.

5. A method of updating a subject file as per claim 4, wherein said monitoring thread comprises the steps of creating a system snapshot, comparing said subject file with said snapshot, determining differences and, if differences exists, signaling the existence of an updated version of said subject file.

6. A method of updating a subject file as per claim 4, wherein said working thread comprises the steps of:

recognizing said updated version, creating a job task file and associated ID, recognizing batch requirements, compressing of the updated version if compressible, and transference to said transfer thread.

7. A method of updating a subject file as per claim 6, wherein said transfer thread comprises the steps of:

receiving and transferring said job task file and associated ID, detecting and reporting of faults, recognizing batch requirements, compressing of the updated version if compressible, and transference to said temporary location.

8. A method of updating a subject file as per claim 1, wherein said method repeats the steps for a plurality of subject files to be updated.

9. A method of updating a subject file as per claim 1, wherein said updated version of said subject file is stored in computer storage at a master site.

10. A method of updating a subject file as per claim 9, wherein said temporary, intermediate, and permanent locations are located remotely from said master site.

11. A method of updating a subject file as per claim 10, wherein said temporary, intermediate, and permanent locations are located remotely on a mirror site of said master site.

12. A method of updating a subject file as per claim 10, wherein said master site comprises a web site and said temporary, intermediate, and permanent locations are located remotely from said web site at one or more distributed web servers.

13. A method of updating a subject file as per claim 1, wherein said method of updating is implemented locally or remotely on one or more computer-based systems, across networks or existing communication mediums.

14. A method of updating a subject file as per claim 1, wherein said method of updating is implemented across networks element comprising any of LANs, WANs, cellular, Internet or Web based networks.

15. A computer media product implementing a method of updating a subject file stored in a target location, said computer media product comprising computer programmable code implementing:

recognizing if an updated version of said subject file exists;

copying said updated version of said subject file to a temporary location;

determining if said subject file is presently being accessed to determine a use status;

if said subject file is not in use, copying said updated version from said temporary location to said target location;

if said subject file is presently in use, transferring said updated version from said temporary location to an intermediate location;

redirecting new requests for said subject file to said updated version located in said intermediate location, and

wherein said determining step is repeated until said updated version is copied into said target location, said transferring to said intermediate location step occurring only during an initial determination of said use status and skipped for subsequent iterations of said determining step.

16. A computer media product implementing a method of updating a subject file stored in a target location as per claim 15, wherein access to said subject file is denied during transfer from said intermediate location to said target location.

17. A computer media product implementing a method of updating a subject file stored in a target location as per claim 15, wherein said method repeats the steps for a plurality of subject files to be updated.

18. A computer media product implementing a method of updating a subject file stored in a target location as per claim 15, wherein said method of updating is implemented locally or remotely on one or more computer-based systems, across networks or existing communication mediums.

19. A method of updating a subject file as per claim 15, wherein said method of updating is implemented across networks element comprising any of LANs, WANs, cellular, Internet or Web based networks.

20. A method of updating a subject file as per claim 15, wherein said updating method is performed between a web site and one or more distributed web servers.

21. A system for updating a subject file while allowing continued access to said file, said system comprising:

an originating file location for an updated version of said subject file;

a temporary location for storing a copy of said updated subject file;

a determining element to indicate a positive or negative usage status of said subject file, the positive or negative usage status being a result of determining if said subject file is presently being accessed;

a destination file location receiving said copy of said updated subject file directly if said usage status is negative,

if otherwise positive, an intermediate location for receiving an accessible copy of said updated subject file until said usage status is reversed to negative, thereby

said destination file location receiving said copy of said updated subject file from said intermediate location, wherein said destination file location receives said copy only during an initial determination of said usage status and is skipped for subsequent iterations of said determination.

22. A system for updating a subject file while allowing continued access to said file, as per claim 21, wherein said originating file location comprises a master site.

23. A system for updating a subject file while allowing continued access to said file, as per claim 22, wherein said temporary, intermediate, and destination locations are located remotely from said master site.

24. A system for updating a subject file while allowing continued access to said file, as per claim 22, wherein said temporary, intermediate, and destination locations are located remotely on a minor site of said master site.

25. A system for updating a subject file while allowing continued access to said file, as per claim 24, wherein said mirror site further comprises:

a shared memory, remote server software, new updated data available monitor, replicator and substitution queue.

26. A system for updating a subject file while allowing continued access to said file, as per claim 22, wherein said master site comprises a web site and said temporary, intermediate, and destination locations are located remotely from said web site at one or more distributed web servers.