Building the volume databases

VLDB. The Volume Location Data Base, VLDB, is used to provide volume addressing information to workstations. Copies of the VLDB reside on the servers and are updated periodically. The VLDB lists the latest known location or locations of all on-line volumes in the system. A human readable version of the VRDB is maintained on the SCM in the file /vice/vol/VRList.

The VLDB is maintained on the SCM. When you wish to update it, run the bldvldb.sh(8) from /vice/bin/ on the SCM. The script gathers a copy of the /vice/vol/VolumeList file from all the servers, merges it into a single list, and builds a new VLDB. The updateclnt and updatesrv daemons will then propagate the new VLDB to all the servers.

Note: The createvol_rep and purgevol_rep scripts automatically invoke bldvldb.sh.

Building the VRDB. The Volume Replication Data Base, the VRDB, is used to provide information about replicated volumes to client workstations. Copies of the VRDB reside on all servers and are updated periodically. The VRDB maps each logical volume to its corresponding set of physical volumes. A human readable version of the VRDB is maintained on the SCM in the file /vice/vol/VRList. The makevrdb option to the volutil(8) command will create a new VRDB which will automatically be distributed to the other servers.

Building the VSGDB. The Volume Storage Group Data Base, VSGDB, is created during setup process and, currently, is maintained by hand. Each valid volume storage group has an entry in this data base containing an identification number and the names of the servers in the group.