NetBackup™ Commands Reference Guide
- Introduction
- Appendix A. NetBackup Commands
- acsd
- add_media_server_on_clients
- backupdbtrace
- backuptrace
- bmrc
- bmrconfig
- bmrepadm
- bmrprep
- bmrs
- bmrsrtadm
- bp
- bparchive
- bpbackup
- bpbackupdb
- bpcatarc
- bpcatlist
- bpcatres
- bpcatrm
- bpcd
- bpchangeprimary
- bpcleanrestore
- bpclient
- bpclimagelist
- bpclntcmd
- bpclusterutil
- bpcompatd
- bpconfig
- bpdbjobs
- bpdbm
- bpdgclone
- bpdown
- bpduplicate
- bperror
- bpexpdate
- bpfis
- bpflist
- bpgetconfig
- bpgetdebuglog
- bpimage
- bpimagelist
- bpimmedia
- bpimport
- bpinst
- bpkeyfile
- bpkeyutil
- bplabel
- bplist
- bpmedia
- bpmedialist
- bpminlicense
- bpnbat
- bpnbaz
- bppficorr
- bpplcatdrinfo
- bpplclients
- bppldelete
- bpplinclude
- bpplinfo
- bppllist
- bpplsched
- bpplschedrep
- bpplschedwin
- bppolicynew
- bpps
- bprd
- bprecover
- bprestore
- bpretlevel
- bpschedule
- bpschedulerep
- bpsetconfig
- bpstsinfo
- bpstuadd
- bpstudel
- bpstulist
- bpsturep
- bptestbpcd
- bptestnetconn
- bptpcinfo
- bpup
- bpverify
- cat_convert
- cat_export
- cat_import
- configureCerts
- configureMQ
- configurePorts
- configureWebServerCerts
- create_nbdb
- csconfig cldinstance
- csconfig cldprovider
- csconfig meter
- csconfig reinitialize
- csconfig throttle
- duplicatetrace
- importtrace
- jbpSA
- jnbSA
- ltid
- mklogdir
- nbauditreport
- nbcallhomeproxyconfig
- nbcatsync
- NBCC
- NBCCR
- nbcertcmd
- nbcertupdater
- nbcldutil
- nbcloudrestore
- nbcomponentupdate
- nbcplogs
- nbcredkeyutil
- nbdb_admin
- nbdb_backup
- nbdb_move
- nbdb_ping
- nbdb_restore
- nbdb_unload
- nbdb2adutl
- nbdbms_start_server
- nbdbms_start_stop
- nbdc
- nbdecommission
- nbdelete
- nbdeployutil
- nbdevconfig
- nbdevquery
- nbdiscover
- nbdna
- nbemm
- nbemmcmd
- nbfindfile
- nbfirescan
- nbfp
- nbftadm
- nbftconfig
- nbgetconfig
- nbhba
- nbholdutil
- nbhostidentity
- nbhostmgmt
- nbhypervtool
- nbidpcmd
- nbimageshare
- nbinstallcmd
- nbjm
- nbkmiputil
- nbkmscmd
- nbkmsutil
- nboraadm
- nborair
- nbpem
- nbpemreq
- nbmlb
- nbperfchk
- nbplupgrade
- nbrb
- nbrbutil
- nbregopsc
- nbreplicate
- nbrepo
- nbrestorevm
- nbseccmd
- nbserviceusercmd
- nbsetconfig
- nbsmartdiag
- nbsnapimport
- nbsnapreplicate
- nbsqladm
- nbstl
- nbstlutil
- nbstop
- nbsu
- nbsvrgrp
- netbackup_deployment_insights
- resilient_clients
- restoretrace
- stopltid
- tldd
- tldcd
- tpautoconf
- tpclean
- tpconfig
- tpext
- tpreq
- tpunmount
- verifytrace
- vltadm
- vltcontainers
- vlteject
- vltinject
- vltoffsitemedia
- vltopmenu
- vltrun
- vmadd
- vmchange
- vmcheckxxx
- vmd
- vmdelete
- vmoprcmd
- vmphyinv
- vmpool
- vmquery
- vmrule
- vmupdate
- vnetd
- vssat
- vwcp_manage
- vxlogcfg
- vxlogmgr
- vxlogview
- W2KOption
- Index
Name
bptpcinfo — discover SAN devices and creates 3pc.conf file
SYNOPSIS
[-a] [-c] [-h] [-u] [-r] [-v] [-d disk_device_directory] [-t tape_device_directory] [-p physical_device] [-o output_file_name] [-o -]
The directory path to this command is /usr/openv/netbackup/bin/
DESCRIPTION
This command operates only on UNIX systems.
The bptpcinfo command discovers all the disk and the tape devices on Fibre Channel and SCSI connections. It provides information about each device (one line per device). By default, this command writes the information to the following file:
/usr/openv/volmgr/database/3pc.conf
Note:
For off-host backup (Third-Party Copy Device or NetBackup media server backup methods), a 3pc.conf file must exist at /usr/openv/volmgr/database.
At the start of a backup, using the Third-Party Copy Device or NetBackup media server method, NetBackup automatically runs this command to create the 3pc.conf file if the file does not already exist. This file is complete and you do not need to rerun this command if any of the following is true:
The backup uses the NetBackup media server backup method.
You use the Third-Party Copy Device backup method and all required devices (such as disks, tapes, and third-party copy devices) support identification descriptors.
If any of the devices does not support identification descriptors, run the bptpcinfo command manually to create the 3pc.conf file. Then edit the file as explained in the SAN Configuration chapter of the NetBackup Snapshot Client Administrator's Guide.
OPTIONS
- -a
Discovers all the disk and the tape devices on the Fibre Channel and SCSI connections. It adds entries in the
3pc.conffile (or alternate output file that is specified with the -o option). The -a option lists all devices in/dev/rdskand/dev/rmt.- -c
Checks for syntax errors in an already existing
3pc.conffile (in/usr/openv/volmgr/database). If the3pc.conffile does not exist, a message states that it cannot open the file. In that case, use other command options to create the file. Note that if -c is specified, any other options are ignored.The -c option checks for syntax errors such as the following: missing spaces between entries, missing keywords (such as a worldwide name without "w="), or a worldwide name that is not 16 digits in length. Any such errors can cause the backup to fail.
- -h
Displays the bptpcinfo usage statement.
- -u
Discovers all the disk devices and the tape devices on the Fibre Channel and SCSI connections. It also adds entries in the
3pc.conffile (or alternate the output file that is specified with the -o option) for new devices that are found. If the3pc.conffile does not exist, the -u option fails (use -a instead).Note:
To remove obsolete entries, use -r instead of -u. (The -u and -r options cannot be used together.)
- -r
Removes any obsolete entries in the
3pc.conffile (or the alternate output file that is specified with the -o option). An obsolete entry is one that no longer corresponds to any devices on the Fibre Channel or SCSI connections.Note:
The -r option does not add entries to the
3pc.conffile for new or reconfigured devices. To add entries, use the -u option. (The -u and -r options cannot be used together.)- -v
Specifies the verbose mode, which causes bptpcinfo to list information on its discovery progress. The information is written to the screen, not to the
3pc.conffile.You can select the -v option to track problems in device discovery.
- -d disk_device_directory
Discovers all disks in the specified directory (usually
/dev/rdskon Solaris or Hewlett Packard Enterprise, and/devon AIX) and creates new entries in the3pc.conffile. Or, it creates new entries in the alternate output file that is specified with the -o option by overwriting any current entries.To avoid overwriting the
3pc.conffile, use the -d option with the -u option. When -d and -u are combined, the new disk entries are added to the existing entries.- -t tape_device _directory
Discovers all tape drives in the specified directory (usually
/dev/rmton Solaris or Hewlett Packard Enterprise, and/devon AIX) and creates new entries in the3pc.conffile. Or, it creates new entries in the alternate output file that is specified with the -o option by overwriting any current entries.To avoid overwriting the
3pc.conffile, use the -t option with the -u option. When -t and -u are combined, the new tape entries are added to the existing entries.- -p physical_device
Creates an entry for a physical device in the
3pc.conffile, if the specified device is discovered. Or, it creates new entries in the alternate output file that is specified with the -o option by overwriting any current entries.To avoid overwriting the
3pc.conffile, use the -p option with the -u option. When -p and -u are combined, the new entry is added to the existing entries.- -o output_file_name
-o specifies an alternate (usually temporary) path for the bptpcinfo command output. If this option is not specified, the default is
/usr/openv/volmgr/database/3pc.conf.- -o -
Sends the output to the screen. Note the space before the second hyphen.
EXAMPLES
Example 1 - Discover all the source and the destination devices on the SAN and create the required 3pc.conf file in /usr/openv/volmgr/database.
# bptpcinfo -a
Example 2 - Discover all the source and the destination devices on the SAN, and send the output to the screen.
# bptpcinfo -a -o -
Sample output:
devid [p=devpath] [s=sn] [n=npid] [l=lun] [w=wwpn] [i=iddesc] 1 p=/dev/rdsk/c1t11d3s2 s=SEAGATE:ST19171N:LAE82305 l=3 2 p=/dev/rdsk/c1t13d4s2 s=SEAGATE:ST19101W:NH022724 l=4 3 p=/dev/rdsk/c1t20d0s2 s=HITACHI:OPEN-9:60159003900 l=0 4 p=/dev/rdsk/c1t20d1s2 s=HITACHI:OPEN-9:60159000000 l=1 5 p=/dev/rdsk/c1t20d2s2 s=HITACHI:OPEN-9:60159000100 l=2 6 p=/dev/rdsk/c1t20d3s2 s=HITACHI:OPEN-9-CM:60159001C00 l=3 7 p=/dev/rdsk/c1t20d4s2 s=HITACHI:OPEN-9:60159002B00 l=4 8 p=/dev/rdsk/c1t20d5s2 s=HITACHI:OPEN-9:60159002C00 l=5
Example 3 - Discover the devices in the /dev/rmt directory (/dev on AIX) and send the output to the screen:
On Solaris or Hewlett Packard Enterprise:
# bptpcinfo -t /dev/rmt -o -
Sample output:
devid [p=devpath] [s=sn] [n=npid] [l=lun] [w=wwpn] [i=iddesc] 0 p=/dev/rmt/0cbn s=QUANTUM:DLT8000:CX949P0164 l=1 i=10200E09E6000000868 1 p=/dev/rmt/1cbn s=QUANTUM:DLT8000:CX949P1208 l=2 i=10200E09E6000001381 2 p=/dev/rmt/4cbn s=QUANTUM:DLT8000:CX940P2790 l=2 i=1031000005013E000D3 3 p=/dev/rmt/7cbn s=QUANTUM:DLT7000:TNA48S0267 l=1 4 p=/dev/rmt/19cbn s=QUANTUM:DLT8000:PKB02P0989 l=1 i=10200E09E6000030C36 5 p=/dev/rmt/20cbn s=QUANTUM:DLT8000:PKB02P0841 l=2 i=10200E09E6000030DC5
On AIX:
# bptpcinfo -t /dev -o -
Sample output:
devid [p=devpath] [s=sn] [n=npid] [l=lun] [w=wwpn] [i=iddesc] 0 p=/dev/rmt0.1 s=STK:L20:LLC02203684 l=1 1 p=/dev/rmt5.1 s=QUANTUM:DLT8000:CXA49P1113 l=1 i=10200E09E6000034A57 2 p=/dev/rmt6.1 s=QUANTUM:DLT8000:PXB13P4180 l=2 i=10200E09E600004B70B 3 p=/dev/rmt7.1 s=STK:9840:331002059900 l=4 i=103500104F0004817E5 4 p=/dev/rmt9.1 s=QUANTUM:DLT8000:PXB33P0850 l=9 i=1036005013000B0526942333350 5 p=/dev/rmt10.1 s=QUANTUM:DLT8000:CX949P1208 l=10 i=1036005013000B0526939343950
Example 4 - Create a 3pc.conf file that describes all devices on the SAN, and send the output to an alternate file:
# bptpcinfo -a -o /usr/openv/volmgr/database/3pc_alt1.conf
NOTES
Note the following items when you use the bptpcinfo command:
Run the bptpcinfo command when no backups are in progress. If a backup operation uses or reserves a device, bptpcinfo may be unable to obtain information on it. It omits such a device from the output.
If you do not want to overwrite the existing
3pc.conffile, include the -o option and specify the wanted location.If you have a host that runs Veritas SANPoint Control, do the following: Use the bpSALinfo command to add the worldwide name and LUN values for each device in the
3pc.conffile. If you do not have SANPoint Control, you must edit the new entries in the3pc.conffile. To edit, manually add the worldwide name WWPN) and LUNs for each device.For more about SAN Configuration, see the NetBackup Snapshot Client Administrator's Guide.
FILES
/usr/openv/volmgr/database/3pc.conf