Novell Doc: OES 2 SP3: Novell Distributed File Services Administration Guide for Linux

5.2 BCC Enabling the VLDB Service

Use the procedure in this section to configure the DFS management context’s VLDB service in a BCC setup (cluster with Novell Cluster Services).

To setup an instance of the VLDB service in BCC:

Install and configure Novell Cluster Services and BCC on the server where you want to host the VLDB service.

For information, see the OES 2 SP3: Novell Cluster Services 1.8.8 Administration Guide for Linux or the NW6.5 SP8: Novell Cluster Services 1.8.5 Administration Guide and BCC 1.2: Administration Guide for Linux
Create a clustered NSS pool on the server.

This creates a clustered resource that is called a cluster virtual server based on the IP address you specify. For information, see Creating a Pool in the OES 2 SP3: NSS File System Administration Guide for Linux.
BCC enable the clustered NSS pool.
Create a shared NSS volume on the clustered pool.

For information, see Creating Unencrypted NSS Volumes in the OES 2 SP3: NSS File System Administration Guide for Linux.

Configure a DFS management context with the following settings:

Parameter	Description
Management Context	This container must be of type o or ou which contains all the BCC peer cluster containers.
Replica Site	Specify the cluster virtual server for the BCC enabled pool that you created in Step 2 as the replica site.
VLDB Path	Specify the location of the VLDB file as a path on the BCC enabled clustered pool’s volume that you created in Step 3. The default path is /var/opt/novell/dfs, which is on the node and not in the clustered resource. In order to be able to be failed over, the path must be changed to a volume on the clustered resource. For OES 2 SP2 or later Linux clusters, specify the path in Linux format (/media/nss/clus_volname/vldbpath). For example, for a clustered volume named dfsvol and a path of /dfs, the Linux format is /media/nss/dfsvol/dfs
VLDB startup	Deselect (disable) the Run VLDB service when the server restarts option.

Edit the cluster load script.
1. Make sure that the script mounts the volume that contains the VLDB file before you issue the vldb command.
2. Add the vldb command at the end.
  
  For Linux clusters, use the Linux form of the switch:
```
vldb -dir /vldbpath
```
  This command starts the VLDB service for the cluster. Replace vldbpath with the path to the VLDB file that you entered for the DFS management context in Step 5. The path must match exactly with what you entered for the DFS management context.
  
  In iManager, use the Clusters plug-in to edit the resource load script to comment out the add_secondary_ipaddress line, and add the virtual IP address information for the dummy0 adapter.
  
  Example of Cluster Load ---Script:
```
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs
exit_on_error nss /poolact=POOL1
exit_on_error ncpcon mount DFSVOL=253

###exit_on_error add_secondary_ipaddress 192.168.100.71

exit_on_error ip addr add 10.50.0.101/32 dev dummy0

exit_on_error ncpcon bind --ncpservername=CL1-POOL1-VS --ipaddress=10.50.0.101
vldb -dir /media/nss/DFSVOL/dfs

exit 0
```
  IMPORTANT:If you ever modify the VLDB file location, you must also modify the path in the cluster load script. For information, see Section 4.3, Modifying VLDB Settings in the Cluster Load Script.
Edit the cluster unload script to Add vldb exit command before ncpcon unbind line.

In iManager, use the Clusters plug-in to edit the resource unload script to comment out the del_secondary_ipaddress line, and add a line that deletes the virtual IP address information for the dummy0 adapter.

Example of Cluster Unload Script:
```
#!/bin/bash
. /opt/novell/ncs/lib/ncsfuncs

vldb exit
ignore_error ncpcon unbind --ncpservername=CL1-POOL1-VS --ipaddress=10.50.0.101

###ignore_error del_secondary_ipaddress 192.168.100.71

ignore_error ip addr del 10.50.0.101/32 dev dummy0

ignore_error nss /pooldeact=POOL1
exit 0
```
Add the nss admin user of every Linux node in the cluster on which VLDB is expected to run as trustees to the container configured as the Management Context in Step 5. The nssadmin user object must be in the same container as its server and the username format is servnameadmin.context. For example, the server name is server1.ou1.mycompany and the nssadmin username is server1admin.ou1.mycompany
1. In iManager, select Rights > Modify Trustees.
2. Select the container configured as the Management Context in Step 5, then click OK.
3. List of trustees for the selected container are displayed.
  
  Ensure that the nssadmin user for each node in the cluster is listed as a trustee with a minimum of Read and Compare Rights to the [All Attribute Rights] property.
4. (Conditional) If the nssadmin user for a node on which the VLDB service runs is not set as a trustee of the container, add it as a trustee and assign the required rights. To add trustee and assign rights, perform the following steps:
  1. Click Add Trustee, select the nssadmin object, then click OK.
  2. Click Assigned Rights for the nssadmin object.
  3. Assign Read and Compare to [All Attribute Rights] property, then click Done.
  4. Click Apply.
    
    Repeat Step 8.d for the nssadmin user for each cluster node.
    
    NOTE:If the Management Context is the container in which the server object for the cluster node exists, the nssadmin object for that server is a trustee of the container with Supervisor rights. Do not modify these rights for the nssadmin user.