Initializes the Backup Server
Synopsis
bakserver [-adminlist filename] [-verbose] [-help]
Options
-adminlist filename
Specifies the file that contains principals and groups authorized to execute bakserver RPCs (usually using bak commands). If
this option is omitted, the bakserver obtains the list of authorized users from the default administrative list file, dcelocal/var/dfs/admin.bak.
-verbose
Directs the bakserver process to provide a detailed report on what it is doing by displaying messages on standard error.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
The help and apropos commands available with all command suites are also available with the bakserver command. See the bos help and bos apropos pages for examples of using these commands.
Description
The Backup Server (bakserver process) communicates with the Backup Database to perform dump and restore operations. The bakserver process must run
on all machines that house a copy of the Backup Database. It is usually started and controlled by the BOS Server; if it is not, execute the bakserver process as a background process. The
binary file for the bakserver process resides in dcelocal/bin/bakserver.
The first time it is initialized, the bakserver process creates the Backup Database in dcelocalvar/dfs/backup; all Backup Database files have a root name of bkdb. The bakserver process also creates the dcelocal/var/dfs/admin.bak administrative list file if the file does not already exist.
The principals and members of groups in the admin.bak administrative list are authorized to issue bak commands (which are used for tasks such as examining the database and dumping and restoring data). The list must also include the abbreviated DFS server principals of all Backup Database machines to allow for the proper distribution of changes via the Ubik database synchronization mechanism.
Because the Backup Database is a replicated database, the admin.bak administrative lists for all bakserver processes in a cell must contain the same principals and groups.
It is recommended that all system administrators using the Backup System be included on the following lists: the admin.bak file on all machines housing the Backup Database; the admin.fl file on all machines housing the Fileset Location Database (FLDB); and the admin.ft file on all File Server machines.
When it is started, the bakserver process makes a ubik_ServerInit call to register its existence as a server process with the Ubik coordinator. It then listens for incoming RPCs to which to respond.
Each time it is started, the bakserver process also creates the dcelocal/var/dfs/adm/BakLog event log file if the file does not already exist. It then appends messages to the file. If the file exists when the bakserver process is started, the process moves it to the BakLog.old file in the same directory (overwriting the current BakLog.old file if it exists) before creating a new version to which to append messages.
Privilege Required
The issuer must be logged in as root on the local machine.
Output
If problems are encountered during initialization, the bakserver process displays error messages on standard error output. The bakserver process keeps
an event log in the file dcelocal/var/dfs/adm/BakLog.
If run with the -verbose option, the bakserver process provides a detailed report on what it is doing by displaying messages on standard error.
Related Information
Files: admin.bak(4dfs)