To add a database server machine, do the following:
1. If you intend to configure the machine as a Fileset Database machine and the machine does not currently have a server entry in the FLDB, use the fts crserverentry command to create a server entry in the FLDB for the abbreviated DFS server principal of the machine. The machine already has a server entry in the FLDB if it is configured as a File Server machine. (See Making Filesets and Aggregates Available for more information about using the fts crserverentry command to create server entries.)
2. Use the dcecp group add command to add the abbreviated DFS server principal of the new database server machine to the appropriate security group (subsys/dce/dfs-fs-servers or subsys/dce/dfs-bak-servers) in the Registry Database.
3. Use the dcecp rpcgroup add command to add the name of the RPC binding of the new database server machine to the appropriate RPC server group (/.../cellname/fs or /.../cellname/subsys/dce/dfs/bak) in CDS.
4. Use the bos addadmin command to add the abbreviated DFS server principal of the new database server machine to the appropriate administrative list (admin.fl or admin.bak). This allows the synchronization site to propagate changes to the secondary sites. These administrative lists are usually updated on the cell's System Control machine, which then distributes the updated lists via the Update Server.
Alternatively, you can use the dcecp group add command to add the abbreviated DFS server principal to a security group included in the list. Note that if a group such as subsys/dce/dfs-fs-servers is included in the administrative list, the DFS server principal is already present in the list as a member of that group.
5. Copy the appropriate administrative list (admin.fl or admin.bak) to the dcelocal/var/dfs directory on the new database server machine. These administrative lists are typically propagated from the cell's System Control machine via the Update Server. Modify the Update Server as necessary if the list is propagated from the cell's System Control machine.
6. Stop and restart the appropriate database server process (flserver or bakserver) on each database server machine of that type. Restarting the existing database server processes causes the processes to read the updated RPC server group. This ensures that each Ubik coordinator agrees on the number and identities of the other database server machines of its type, which is vital to Ubik's use of a quorum of database server machines to maintain database consistency.
7. Start the appropriate database server process (flserver or bakserver) on the new database server machine.