What are the command options for nbfdrv64,when using san-clients?

[xhawk]

After  san-client is enabled on NBU5220, NBU5220 works as a FT media sever, we can see the FT processes as below:

nbu52201:/ # bpps -x|grep nbf
root     13016     1  0 21:22 ?            00:00:05 /usr/openv/netbackup/bin/nbftsrvr
root     13043 13016  3 21:22 ?        00:00:24 /usr/openv/netbackup/bin/nbfdrv64 -m=0xfc08002 -v=3 -s=256K -p=20 

What are the  command options here for nbfdrv64?

-m=0xfc08002    stands for what?

-v=3                    stands for what?

-s=256K             stands for SIZE_DATA_BUFFERS_FT?

-p=20                 stands for FT-Pipes (FT Connections)?

-----------------------------------------------------------------------------------------------------------------------------------------------------------

I tried to change "Maximum concurrent FT connections" to 16 using NBU Java GUI concole, in Media server host properties,

and then restarted th NBU processes, but nbfdrv64's command option for -p is still 20. Should I use nbftadm to change this?

How do I know the current FT configuration?

Thanks...

[Mark_Solutions · Accepted solution]

You could try

nbftconfig -changeserver -Me mediaservername -l 16

check with the following first to make sure what you see if correct:

nbftconfig -listservers -Me mediaservername (-v if you wish)

[CRZ]

I can't answer your question (hopefully Mark has), but this Usage statement will tell you about all those command line switches:

# nbfdrv64

@(#)$Source: src/nb/ftserver/FATServerMain.cpp,v $ $Revision: 1.34.102.1 $
FATServerMain - FATServer daemon child process for Linux/Solaris

usage:  FATServerMain [-d] [-l] -m=<shmid> [-s=<bufSegSize>] [-v]

where:  -d=<bsilevel>    enable BSI STDF (scsi target device function) logging
                0 - minimum
                1 - fatal
                2 - emergency
                3 - fault
                4 - alert
                5 - warn
                6 - notice
                7 - info
                8 - verbose
                9 - debug
        -l               limit number of luns per port to support to 1
        -m=<shmid>       shared memory id
        -p=<defPipes>    default number of pipes to support
        -s=<bufSegSize>  buffer segment size (64K..512K)
                         0   => use default of 256K
                         64K, 128K, 256K, or 512K
        -v=<loglevel>    enable verbose FAT pipe process logging

[xhawk]

Thanks,

It's production system, I just did not try to type the command.

but even if I tried to change the number of FT-Pipes to "16" using NBU-Java-GUI-Console, or using command nbftconfig, The nbfdrv64's command option -p is still 20, so which one of the FT-Pipes value is in effect?

I guess the one using nbftconfig or GUI is the value in effect.

and  nbfdrv64's command option -p=20 is determined by the startup scripts which is fixed and do not take input value.