1 02/27/85 reconstruct_registry
2
3 Syntax as a command: reconstruct_registry registry_names
4 -control_args
5
6
7 Function: recovers a current copy of RCP Resource Management
8 registries after a catastrophic system failure causing the loss of one
9 or more registries. It assumes that the registry to be reconstructed
10 is a consistent earlier copy of the registry desired, and that the RCP
11 Resource Management journal contains a record of all operations
12 performed on the registry since the time represented by the earlier
13 copy.
14
15
16 Arguments:
17 registry_names
18 are the entrynames of the registries to be reconstructed. The star
19 convention is accepted. If the suffix .rcpr is not given, it is
20 assumed.
21
22
23 Control arguments:
24 -pathname path -pn path
25 to specify the directory in which the registries reside. If this
26 control argument is not specified, the registries are sought in
27 >sc1>rcp.
28
29
30 Notes: An explanation of the creation and maintenance of checkpointed
31 registry copies can be found in the documentation of the copy_registry
32 command.
33
34 The prescribed sequence of operations is to delete the damaged
35 registries; copy the desired checkpointed registries into place; and
36 invoke the reconstruct_registry command to update the registries. The
37 command locates the RCP Resource Management journal relative to the
38 directory in which the registries to be updated reside.
39
40
41 If an online checkpoint copy of a system registry is not available, a
42 copy of the registry may be retrieved from a system backup tape. In
43 this case, the file retrieved must be from a time that is more recent
44 than the last time the RCP Resource Management journal was reset see
45 the documentation of the copy_registry command.
46
47 The reconstruction of system registries must only be performed from the
48 Initializer, in the "standard" environment, before the answering
49 service is activated.
50
51
52 Access required: This command requires access to the rcp_sys_ gate.