The jukebox file server is the core of iXOS-JUKEMAN. It controls the
devices, and replies to NFS requests and to requests from the iXOS-JUKEMAN
local file system for NT. The server and all the programs and files it needs
are in the JUKEMAN directory. All paths described here are relative to the
JUKEMAN directory.
The server cdnfsd runs as a daemon and receives requests from NFS
clients, from cdadm and from the iXOS-JUKEMAN native file system for
NT. It creates logfile.txt for messages and a database
volumes for disk names and properties. It needs a file
server.lic containing the license key (to use the IFS it also needs a
valid writer.lic) and a file server.cfg containing the server
configuration.
To enable task distribution and efficient service to a large number of clients,
the server splits into separate threads. The number of threads increases with
the number of devices. They share text and data to minimize load on the
computer.
The server controls devices for handling disks and exports the disks in a
single large file system in which each disk is represented by a directory. NFS
clients just need a single mount, and PC clients connect a single network
drive. The server hides the physical positions of the disks. Each disk is
represented by a subdirectory, whether it is in a storage slot or in a drive.
Clients don't know if a disk is actually stored in a jukebox, a tower or is a
copy stored in another jukebox. They experience faster access to the disk
because the server chooses the jukebox with less load.