 |
 |
|
|
|
|
Title: |
US6144999:
Method and apparatus for file system disaster recovery
[ Derwent Title ]

|
Country: |
US United States of America

|
| |
Inventor: |
Khalidi, Yousef A.; Cupertino, CA
Talluri, Madhusudhan; Fremont, CA
Dion, David; Seattle, WA
Swaroop, Anil; Loma Linda, CA

|
Assignee: |
Sun Microsystems, Incorporated, Palo Alto, CA
other patents from SUN MICROSYSTEMS, INC. (551495) (approx. 3,879)
News, Profiles, Stocks and More about this company

|
Published / Filed: |
2000-11-07
/ 1998-05-29

|
Application Number: |
US1998000087261

|
IPC Code: |
Advanced:
G06F 11/20;
Core:
more...
IPC-7:
G06F 13/00;

|
ECLA Code: |
G06F11/20L4M8A;

|
U.S. Class: |
Current:
709/219;
714/E11.107;
Original:
709/219;

|
Field of Search: |
709/203,212,213,217,218,219,223,224,225,242
707/010,200,201,202,204
714/015

|
Priority Number: |
| 1998-05-29 |
US1998000087261 |

|
Abstract: |
A file disaster recovery system that employs geographical replication of data from a local site to remote site in a such a manner that file requests from clients of the local site can be handled by a file server on the remote site following a failover from the local site to the remote site. Geographical data replication software running on a local server checkpoints to a log in local stable storage all information on file operations that change the file state of the local file system. According to a selected mode, the local geographical data replication software flushes information in the log pertaining to the file operations since the last flush to the remote site. At the remote site, compatible remote geographical data replication software running on a remote file server receives the flushed log and replicates in sequence order the file operations represented in the flushed log. The results of the operations are stored on remote stable storage. The local and remote servers can be clusters or single servers. There is no need for commonality, except for operating and file systems, between the local and remote sites. Because operations are replicated and not low level, formatted data, the local and remote stable file storage can be completely different.

|
Attorney, Agent or Firm: |
Pennie & Edmonds LLP ;

|
Primary / Asst. Examiners: |
Meky, Moustafa M.;

|
INPADOC Legal Status: |
Show legal status actions
Family Legal Status Report

|
Family: |
Show 8 known family members

|
First Claim:
Show all 56 claims |
What is claimed is:
1. A geographical data replication system comprising:
- a local primary server configured to run a first high availability file system (FHAFS) and a local file system;
- a local secondary server coupled to the local primary server configured to run the local file system and respond to FHAFS mini-transactions initiated by the local primary;
- first dual-ported file storage coupled to the local servers with which the local servers interact via the local file system;
- at least one client configured to issue local file system requests to the local primary;
- the local primary being configured in accordance with the FHAFS to checkpoint to the local secondary mini-transactions conveying application state, enabling the local secondary, when the local primary fails, to take over operations of the local primary consistent with the checkpointed application state, the local secondary only being active when the local primary is inactive;
- a local server that is whichever of the local primary and secondary is active configured to intercept the local file requests and to determine which of the local file requests is one of a first set of file requests that will alter file state of the local file system; and
- a log file stored on the first dual-ported file storage in which the local server writes operations and data required to serve the first set of file requests, the local server being configured to periodically flush the log file to a remote site, enabling the remote site, when the local site fails, to serve the local file requests with little or no loss of the file state;
- such that, when it is active, the local primary is configured to pass file checkpoints to the local secondary server in conjunction with the mini-transaction checkpoints issued by the FHAFS, enabling the local secondary, when the local primary fails, to complete uncompleted local file requests and to handle subsequent local file requests consistent with the file and application state.

|
Background / Summary: |
Show background / summary

|
Drawing Descriptions: |
Show drawing descriptions

|
Description: |
Show description

|
Forward References: |
Show 57 U.S. patent(s) that reference this one

|
 |
 |
|
|
|
|
Foreign References: |
None

|
Other Abstract Info: |
DERABS G2000-207276

|
Other References: |
"Solaris MC File System Framework", Vlada Matena, Yousef A. Khalidi, Ken Shirriff, 20 pages, Oct. 1996, Sun Microsystems Laboratories, SMLI TR-96-57.
"White Paper-NFS", 12 pages, .TM.1994-1997 Sun Microsystems, Inc. Palo Alto CA 94303, http://www.sun.com/solaris/wp-nfs 18.html.
"Building Distributed Process Management on an Object-Oriented Framework", Ken Shirriff, Sun Microsystems, 16 pages, Jan. 12, 1998, http://www.sunlabs.com/research/solaris-mc/doc/process-usenix.doc. html.
"Using DFS Without DCE/LFS (Episode)", Chuck E. Lever, 7 pages, Jan. 1994, Center for Information Technology Integration: Technical Report Series 1986-1997, Report 94-2.
"DFS Server for Window NT", Transarc, Pittsburgh PA 15219, 4 pages, Jan. 12, 1998, http://www.transarc.com/afs/transarc.com/public/www/Public/ProdServ/Product/DFS/dfsnt/dfsservent.html.

|


|
Nominate this for the Gallery...

|
|