eDirectory with one million objects occupies around 2.5GB of disk space; so, large DIBs need a lot of disk space. In such instances, eDirectory 8.7.3 or later offers a custom configuration option for DIBs. This option enables you to use the mount path for DIB location in case of disk space constraints.
Now the problem becomes how to mount the DIB on a separate Solaris server and access it for further operations. With no permissions set, the problem below would be reported:
bash-2.05# mount 220.127.116.11:/export/home7/mamatha /sc01 mount: 1831-011 access denied for 18.104.22.168:/export/home7/mamatha mount: 1831-008 giving up on: 22.214.171.124:/export/home7/mamatha The file access permissions do not allow the specified action.
The /etc/dfs/dfstab file on Solaris contains information like the following example:
# share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource] # .e.g, # share -F nfs -o rw=hostname -d "home dirs" /export/home11/mamatha
Note: Here the -o option is the read, read-write, etc. permission. You can also specify the hostname (rw=hostname), where hostname is the name of the server from where one has to access this machine.
This would limit the share to that particular server. If you want to access from any server then one can simply specify “-o rw”. The -d “text” is the description here.
In order to work with the DIB in a mount path on Solaris from any UNIX machine, you need to follow these steps:
1. Edit the file /etc/dfs/dfstab on Solaris with the below mentioned information inorder to mount and access the DIB.
share -o root=hostname,rw=hostname -d "home dirs" dir_pathname
Example: Suppose you need to access the DIB on Solaris from a given UNIX machine (st-nf-aix-1p-59.blr.novell.com). Then the /etc/dfs/dfstab contents should be:
share -o root=st-nf-aix-1p-59.blr.novell.com,rw=st-nf-aix-1p-59.blr.novell.com -d "home dirs" /export/home7/mamatha
2. After editing the above file, restart the NFS server using the following commands:
bash-2.05# /etc/init.d/nfs.server stop bash-2.05# /etc/init.d/nfs.server start
3. Mount from any UNIX machine. For example:
bash-2.05# mount 126.96.36.199:/export/home7/mamatha /sc01
Now you can mount to this shared directory and access it for further operations.
Note: This can be especially useful for Testers when there are disk space issues.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.