3.3

Disconnect Recovery
91
4. Select the failed (disconnected) server on the console and use the diskclear command to
wipe the database off the failed server.
The display will look similar to the following (with what you type appearing in bold):
?# diskclear -
DANGER -- This program DESTROYS all information on this computer's
data base.
Do you wish to save the current data base? (y/n): n
Are you sure you wish to CLEAR the disk? (n/y): y
? Mon Jan 3 16:18:23 2000 diskclear CLEARING DATA BASE
? Mon Jan 3 16:18:23 2000 Each dot represents 10,000 blocks. The
entire database = 1677 dots.
........10.........20.........30.........40.........50
.........60.........70.........80.........90.........100
.........110......
The diskclear will print a sequence of dots and numbers as it clears the disk. For
instance, on a full 16 gigabyte database, the dots and numbers count to 16,000. The
diskclear may take some time to complete.
5. Reconnect the failed server to the survivor.
a. After the diskclear has completed you can reconnect the servers. Select both (all)
servers on the console and type:
reconnect <failed> master=<survivor> net=ab
b. Depending on which one failed and which one is master, you would enter one of the
following commands:
reconnect a master=b net=ab
reconnect b master=a net=ab
A few moments after entering the command, the failed server will regain its normal,
named prompt. Communication and mirroring between the servers is reestablished.
6. Begin copying the database back over to the failed server.
a. Select the revived (failed) server only on the console and begin a diskcopy:
NRCS-B# diskcopy -9
Users can continue working while the diskcopy continues in the background.
7. When the diskcopy has completed, stop all servers and devices.