The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jan. 24, 2006
Filed:
Jan. 29, 2002
Thomas R. Ulrich, Rancho Santa Margarita, CA (US);
James R. Schweitzer, Huntington Beach, CA (US);
Gregory D. Bolstad, Tustin, CA (US);
Jay G. Randall, Newport Beach, CA (US);
John R. Staub, Newport Beach, CA (US);
George W. Priester, Westminster, CA (US);
Thomas R. Ulrich, Rancho Santa Margarita, CA (US);
James R. Schweitzer, Huntington Beach, CA (US);
Gregory D. Bolstad, Tustin, CA (US);
Jay G. Randall, Newport Beach, CA (US);
John R. Staub, Newport Beach, CA (US);
George W. Priester, Westminster, CA (US);
Adaptec, Inc., Milpitas, CA (US);
Abstract
A system and method for replacing file system processors, also known as hot swapping, is described. The system and method operate on a fault-tolerant network file system that includes a first file server that is operably connected to a network fabric and a second file server that is operably connected to the network fabric. The fault-tolerant network file system includes a first disk array that is operably coupled to the first file server and to the second file server and a second disk array that is operably coupled to the first file server and to the second file server. First file system information is loaded on the first file server. The first file system information includes a first intent log of proposed changes to first metadata. Second file system information is loaded on the second file server. The second file system information includes a second intent log of proposed changes to second metadata. The first file server has a copy of the second metadata, and the second file server maintains a copy of the first metadata, thereby allowing the first file server to access files on the second disk array in the event of a failure of the second file server.