TY - GEN
T1 - Implicit replication in a network file server
AU - Bhide, Anupam
AU - Elnozahy, Elmootazbellah N.
AU - Morgan, Stephen P.
PY - 1990
Y1 - 1990
N2 - The design and implementation of a highly available network file server (HA-NFS) is reported. It is implemented on a network of workstations from the IBM RISC System/6000 family. HA-NFS servers preserve the semantics of the NFS protocol and can be used by existing NFS clients without modification. Therefore, existing application programs can benefit from high availability without alteration. HA-NFS achieves storage reliability by (optionally) replicating files on different disks. However, all copies of the same file are controlled by a single server, reducing the cost of ensuring consistency. To achieve server reliability, each server is implicitly replicated by a backup that can access the server's disks if the server fails. During normal operation, the backup monitors the liveness of the server but does not maintain information about the server's internal state. Each server maintains a disk log that records state information normally kept in memory. The disk log also records the changes to file-system structures. If the server fails, the backup will take over the server's disk, use the disk log to restore the server's file system to a consistent state, and reconstruct the server's prefailure volatile state. The backup will then impersonate the failed server and service requests on its behalf. The failure of the server is oblivious to the clients, which continue to send their requests to the failed server's address. Since the backup itself is a server for a different set of disks, operation continues with reduced performance. If two networks are available, the network can be implicitly replicated.
AB - The design and implementation of a highly available network file server (HA-NFS) is reported. It is implemented on a network of workstations from the IBM RISC System/6000 family. HA-NFS servers preserve the semantics of the NFS protocol and can be used by existing NFS clients without modification. Therefore, existing application programs can benefit from high availability without alteration. HA-NFS achieves storage reliability by (optionally) replicating files on different disks. However, all copies of the same file are controlled by a single server, reducing the cost of ensuring consistency. To achieve server reliability, each server is implicitly replicated by a backup that can access the server's disks if the server fails. During normal operation, the backup monitors the liveness of the server but does not maintain information about the server's internal state. Each server maintains a disk log that records state information normally kept in memory. The disk log also records the changes to file-system structures. If the server fails, the backup will take over the server's disk, use the disk log to restore the server's file system to a consistent state, and reconstruct the server's prefailure volatile state. The backup will then impersonate the failed server and service requests on its behalf. The failure of the server is oblivious to the clients, which continue to send their requests to the failed server's address. Since the backup itself is a server for a different set of disks, operation continues with reduced performance. If two networks are available, the network can be implicitly replicated.
UR - http://www.scopus.com/inward/record.url?scp=0025554190&partnerID=8YFLogxK
M3 - Conference contribution
AN - SCOPUS:0025554190
SN - 0818620854
T3 - Proceedings - Workshop on the Management of Replicated Data
SP - 85
EP - 90
BT - Proceedings - Workshop on the Management of Replicated Data
PB - Publ by IEEE
T2 - 1990 Workshop on the Management of Replicated Data
Y2 - 8 November 1990 through 9 November 1990
ER -