Search <book_title>...

Veritas NetBackup™ Commands Reference Guide

Last Published: 2017-07-21

Product(s): NetBackup (8.0)

Introduction
Appendix A. NetBackup Commands
1. acsd
2. add_media_server_on_clients
3. backupdbtrace
4. backuptrace
5. bmrc
6. bmrconfig
7. bmrepadm
8. bmrprep
9. bmrs
10. bmrsrtadm
11. bp
12. bparchive
13. bpbackup
14. bpbackupdb
15. bpcatarc
16. bpcatlist
17. bpcatres
18. bpcatrm
19. bpcd
20. bpchangeprimary
21. bpclient
22. bpclimagelist
23. bpclntcmd
24. bpclusterutil
25. bpcompatd
26. bpconfig
27. bpdbjobs
28. bpdbm
29. bpdgclone
30. bpdown
31. bpduplicate
32. bperror
33. bpexpdate
34. bpfis
35. bpflist
36. bpgetconfig
37. bpgetdebuglog
38. bpimage
39. bpimagelist
40. bpimmedia
41. bpimport
42. bpinst
43. bpkeyfile
44. bpkeyutil
45. bplabel
46. bplist
47. bpmedia
48. bpmedialist
49. bpminlicense
50. bpnbat
51. bpnbaz
52. bppficorr
53. bpplcatdrinfo
54. bpplclients
55. bppldelete
56. bpplinclude
57. bpplinfo
58. bppllist
59. bpplsched
60. bpplschedrep
61. bppolicynew
62. bpps
63. bprd
64. bprecover
65. bprestore
66. bpretlevel
67. bpschedule
68. bpschedulerep
69. bpsetconfig
70. bpstsinfo
71. bpstuadd
72. bpstudel
73. bpstulist
74. bpsturep
75. bptestbpcd
76. bptestnetconn
77. bptpcinfo
78. bpup
79. bpverify
80. cat_convert
81. cat_export
82. cat_import
83. configurePorts
84. create_nbdb
85. csconfig
86. duplicatetrace
87. importtrace
88. jbpSA
89. jnbSA
90. ltid
91. mklogdir
92. nbauditreport
93. nbcatsync
94. NBCC
95. NBCCR
96. nbcertcmd
97. nbcertupdater
98. nbcomponentupdate
99. nbcplogs
100. nbdb_admin
101. nbdb_backup
102. nbdb_move
103. nbdb_ping
104. nbdb_restore
105. nbdb_unload
106. nbdbms_start_server
107. nbdbms_start_stop
108. nbdc
109. nbdecommission
110. nbdelete
111. nbdeployutil
112. nbdevconfig
113. nbdevquery
114. nbdiscover
115. nbdna
116. nbemm
117. nbemmcmd
118. nbexecute
119. nbfindfile
120. nbfirescan
121. nbftadm
122. nbftconfig
123. nbgetconfig
124. nbhba
125. nbholdutil
126. nbhypervtool
127. nbjm
128. nbkmsutil
129. nboraadm
130. nbpem
131. nbpemreq
132. nbperfchk
133. nbplupgrade
134. nbrb
135. nbrbutil
136. nbregopsc
137. nbreplicate
138. nbrestorevm
139. nbseccmd
140. nbsetconfig
141. nbsnapimport
142. nbsnapreplicate
143. nbsqladm
144. nbstl
145. nbstlutil
146. nbsu
147. nbsvrgrp
148. resilient_clients
149. restoretrace
150. stopltid
151. tl4d
152. tl8d
153. tl8cd
154. tldd
155. tldcd
156. tlhd
157. tlhcd
158. tlmd
159. tpautoconf
160. tpclean
161. tpconfig
162. tpext
163. tpreq
164. tpunmount
165. verifytrace
166. vltadm
167. vltcontainers
168. vlteject
169. vltinject
170. vltoffsitemedia
171. vltopmenu
172. vltrun
173. vmadd
174. vmchange
175. vmcheckxxx
176. vmd
177. vmdelete
178. vmoprcmd
179. vmphyinv
180. vmpool
181. vmquery
182. vmrule
183. vmupdate
184. vnetd
185. vxlogcfg
186. vxlogmgr
187. vxlogview
188. W2KOption

Name

bptpcinfo — discover SAN devices and creates 3pc.conf file

SYNOPSIS

bptpcinfo [-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.conf file (or alternate output file that is specified with the -o option). The -a option lists all devices in /dev/rdsk and /dev/rmt.

-c

Checks for syntax errors in an already existing 3pc.conf file (in /usr/openv/volmgr/database). If the 3pc.conf file 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.conf file (or alternate the output file that is specified with the -o option) for new devices that are found. If the 3pc.conf file 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.conf file (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.conf file 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.conf file.

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/rdsk on Solaris or Hewlett Packard Enterprise, and /dev on AIX) and creates new entries in the 3pc.conf file. 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.conf file, 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/rmt on Solaris or Hewlett Packard Enterprise, and /dev on AIX) and creates new entries in the 3pc.conf file. 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.conf file, 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.conf file, 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.conf file, 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.conf file, 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.conf file. If you do not have SANPoint Control, you must edit the new entries in the 3pc.conf file. 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