HP CIFS Server 3.0k Administrator's Guide version A.02.04

Swap Space Requirements
Due to the one-process-per-client model of HP CIFS, perhaps the most stringent requirement
imposed on the system is that of swap space. HP-UX reserves a certain amount of swap space
for each process that is launched, to prevent it from being aborted in case it needs to swap out
some pages during times of memory pressure. Other operating systems, only reserve swap space
when it is needed. This results in the process not finding the swap space that it needs, in which
case it has to be terminated by the OS.
Each smbd process will reserve about 2 MB of swap space and depending on the type of client
activity, process size may grow up to 4 MB of swap space. For a maximum of 2048 clients, 4 *
2048 or about 8 GB of swap space would be required. Therefore, HP recommends configuring
enough swap space to accommodate the maximum number of simultaneous clients connected
to the HP CIFS server.
Memory Requirements
Each smbd process requires approximately 2 MB of memory on HP-UX 11i v1 and 4 MB on
HP-UX 11i v2. For 2048 clients, therefore, the system must have at least 8 GB of physical memory.
This is over and above the requirements of other applications that will be running concurrent
with HP CIFS.
Step 1: Installing HP CIFS Server Software
If the HP CIFS Server software has been pre-installed on your system, you may skip Step 1 and
go directly to "Step 2: Running the Configuration Script".
If you want to use the CIFS File System Module (CFSM) feature on an HP-UX release 11i v3
system, see section “Procedures for Updating a New Version When Using CFSM” for detailed
procedures before you update to a new version of HP CIFS Server.
HP CIFS Server Upgrades:
If you are upgrading an existing HP CIFS Server configuration, HP recommends that you create
a backup copy of your current environment. The SD install procedure may alter or replace your
current configuration files. All files under /var/opt/samba, /etc/opt/samba and /opt/samba must be
saved in order to ensure that you will be able to return to your current configuration, if necessary.
For example:
$ stopsmb
or if winbind is in use, then do:
$ stopsmb -w
$ mkdir /tmp/cifs_save
$ tar -cvf /tmp/cifs_save/var_backup.tar /var/opt/samba
$ tar -cvf /tmp/cifs_save/etc_backup.tar /etc/opt/samba
$ tar -cvf /tmp/cifs_save/optsamba_backup.tar /opt/samba
Do not use the -o option with the tar command. This will ensure proper file ownership.
If a problem with the upgrade does occur, use SD to remove the entire HP CIFS Server product
and restore your previous backup version. Once this is done, you may restore the saved
configuration files and the HP CIFS Server. For example:
$ tar -xvf /tmp/cifs_save/var_backup.tar
$ tar -xvf /tmp/cifs_save/etc_backup.tar
$ tar -xvf /tmp/cifs_save/optsamba_backup.tar
This procedure is not intended to replace a comprehensive backup strategy that includes user
data files.
24 Installing and Configuring the HP CIFS Server