Release Update provides fixes for VERITAS NetBackup (tm) Enterprise Server / Server 6.5 on OpenVMS clients.

Article:TECH129355  |  Created: 2010-01-27  |  Updated: 2010-01-06  |  Article URL
Article Type
Technical Solution



Release Update provides fixes for VERITAS NetBackup (tm) Enterprise Server / Server 6.5 on OpenVMS clients.


  April 22, 2010
  The Symantec NetBackup 6.5.6 OpenVMS Client

  The NetBackup 6.5.6  OpenVMS  client  release  update  is  now
  available  for  HP  Integrity (IA64), Alpha (AXP) and VAX sys-


  -- There are no pack dependencies for this release.



  This  release contains the following new features, changes and

  1. Support for all 6.5.2 to 6.5.6 master and media servers.

  2. This release will backup and restore all previous  versions
  of a file correctly.

  3.  Browse backup requests from the client, for the NBU direc-
  tory and  restore  commands,  are  now  made  to  the  servers
  vnetd/bprd  service  ports.  Such requests, do not require the
  client to be authorized as a server.

  4. The NBU directory, backup and restore  commands  (with  the
  /LOG  qualifier)  can display a very long list of OpenVMS file
  specifications.  Such lists,  can  overwhelm  the  client  log
  files  with unnecessary detail. This release will not log file
  specification lists to the client log file.

  5. The NBU directory /TOTAL qualifier will display  a  summary
  of  the found files, without displaying any of the file speci-

  6. The NBU directory /ALL qualifier will search  all  backups,
  not just the most recent, for a given file specification.

  7.  The  NBU  directory /IMAGE command now displays the backup
  expiration date.

  8. Connections to the server can use  either  non-reserved  or
  reserved source port numbers.  Connections which require a re-
  served port are assigned the port number randomly, instead  of
  sequentially, from the client reserved port window.

  The sequential assignment of client reserved ports can be very
  inefficient.  For example,  each  process  on  a  multi-stream
  backup  will attempt to bind() to all the previous streams re-
  served ports.  The random assignment of reserved  ports  will,
  in  most  cases, efficiently assign an available reserved port

  9. Connections to the server, which do not required the socket
  to be bound to a reserved port, are now efficiently assigned a
  source port from the IP stacks ephemeral port range.  Firewall
  administrators  should only block destination connection ports
  (as these are critical) and leave open  the  source  ports  of
  those  connections.  Only the bpcd, bprd and vnetd destination
  ports, between the client and the  server,  need  to  be  left

  10. A backup policy for more than one client will use the same
  backup selection list for all  clients.  In  such  cases,  the
  backup  selection  list  should  specify  logical device names
  which translate to the individual client real device names.

  Some clients may have more devices than others. Clients  which
  have  less  devices  should  assign  the unused logical device
  names to the NL: device.  Backups from this device will always
  be successful and backup nothing.

  11.  Immediate  command requests from the server, which do not
  send a disconnect request, can cause the client  BPCD  process
  to  hang whilst waiting for such a request.  This release will
  terminate the client BPCD process after the completion of  any
  immediate command request.

  12.  The  percent  (%)  character is an OpenVMS wildcard for a
  single character within a file or directory name.  It  can  be
  specified  in  an ODS-5 file or directory name, but it must be
  preceded by the circumflex (^) character.  This  release  will
  backup and restore ODS-5 file or directory names which contain
  the percent (%) wilcard character.

  13. Support for the NBU>  RESTORE/DISK_MEDIA_SERVER  qualifier
  and  value.  This qualifier provides the same functionality as
  the bprestore -disk_media_server option.  It is only useful in
  cases  where  the NetBackup domain spans multiple sites and in
  such cases it can be used to restore from  a  specified  local
  media server.

  14.  Support for the NBU> BACKUP/SINCE qualifier and date-time
  value.  Specify this qualifier to backup files with a revision
  date  and  time  greater than or equal to the specified /SINCE

  In addition to the date-time standard keywords, support is al-
  so provided for /SINCE=WEEK (since last week) and /SINCE=MONTH
  (since last month).

  15. The backup /EXCLUDE qualifier can specify a comma separat-
  ed  list  of, usually wildcarded, file specifications enclosed
  within parentheses ().  File specifications  that  start  with
  the at sign (@) are an indirect reference to a file which con-
  tains a list of file specifications to exclude.  This  release
  only supports indirect exclude list file names that start with
  the at sign (@) character.

  16. This release will restore files with the same "contiguous"
  or  "contiguous  best  try"  attributes as the files they were
  backed up from.  Specify the restore /CONTIGUOUS qualifier  to
  restore  files  with the "contiguous" file attribute.  Specify
  the restore /NOCONTIGUOUS qualifier to restore files  with  no
  contiguous  file  attributes.   Specify  the restore /BEST_TRY
  qualifier to restore files with the "contiguous best try" file

  17.  The  NBU>  DIR/IMAGE/SINCE  command  will now default the
  /SINCE qualifier value to TODAY.  This command will only  list
  the  backups with a backup date and time from the start of TO-

  18. Output files created with the NBU> /OUTPUT=file-name qual-
  ifier are now created as StreamLF files.

  19.  The  NBU>  SHOW LOG command will show the contents of the
  current daily log file.  Specify the /OUTPUT=file-name  quali-
  fier to redirect this output to a local file.

  20. This release supports non-vnetd connections from the serv-
  er correctly.  This corrects  the  "can't  connect  to  client
  (status  58)" error when the master or media server is config-
  ured to connect to the client daemon port only.

  21. This release corrects an error where the NBU restore  com-
  mand  finds  the files to restore, in the servers catalog, but
  the client initiated restore does not;  resulting  in  a  hung

  File  searches  of the server catalog by the NBU directory and
  restore commands are, by default, not  case  sensitive.   This
  allows  users to search for, and restore, all occurrences of a
  particular file name, regardless of its case.

  If the NBU directory or restore commands do not find the exact
  case  of  the files you want, then specify the /CASE_SENSITIVE
  qualifier.  Case sensitivity is then  applied  to  the  entire
  file  specification, including the device and directory names.
  Depending on the current process parse style, it may be neces-
  sary  to  enclose  a  case  sensitive  file  specification  in

  22. This release corrects an error where the NBU> SHOW  CLIENT
  command fails when connecting to a MultiNet TCP/IP stack.

  23.  This release corrects an error where the NBU> BACKUP com-
  mand /SERVER=name qualifier truncates the server name to three

  24.  This  release correctly implements point 16 above.  Files
  which are backed up with the contiguous attribute are restored
  with  the contiguous attribute.  This was a restore (and not a
  backup) error; that is, existing backups of  contiguous  files
  are restored as contiguous files.

  25.  File name entries within a directory contain a pointer to
  the file-header, which contains the file attributes.   Entries
  without a file-header pointer can be listed, for example, with
  the $ DIRECTORY command, but their file attributes cannot; nor
  can  such files be opened.  The $ ANALYZE/DISK device: command
  will show all such files on a device.

  This release corrects a potential infinite loop  on  a  backup
  when processing such directory entries, where the same file is
  continuously reported as not found; specifically,  the  status

  26. The NBU$CLIENT_NAME logical can be used to name a particu-
  lar node in an OpenVMS cluster which shares  a  common  system
  disk.   Please see, the "OpenVMS Cluster Installation" section
  of the NetBackup User's Guide for OpenVMS.

  27. Indirect backup lists can  be  specified  by  preceding  a
  backup  file specification with the at sign (@) character.  In
  which case, the contents of the file are used to backup a list
  of backup file specifications.

  Indirect  backup lists can be specified in a policy backup se-
  lections list, recursively in an indirect backup list,  or  as
  an NBU> command line backup file specification. For example:

  NBU> backup/log @file_list.lis/ignore=(inter,noback)

  which  will  use  the  contents of the file "file_list.lis" to
  backup a list of backup file specifications.   Backup  command
  line  qualifiers are applied to all backup file specifications
  in an indirect backup file list.

  28. Support for the *.*;* and *.*.* wildcard file name,  type,
  and version syntax.

  29. Improved accuracy of status values returned to DCL command

  30. This release contains an updated NBU.HLB  library  in  the
  nbu_help.bck  backup  save-set.   Extract  the backup save-set
  from the zip archive and set the following file attributes:

  $ SET FILE/ATT=(RFM:FIX,LRL:32256,RAT:NONE) nbu_help.bck

  and extract the NBU.HLB library:

  $ backup/log nbu_help.bck/save []/new

  Copy the NBU.HLB library to the SYS$HELP: directory:

  $ cop nbu.hlb sys$help:

  Type the NBU> HELP command for help.


  There are no known issues with this release update.


  1. Download the NB_VMS_6.5.6_<6 digit number>.zip file into  a
  temporary directory.

  - where <6 digit number> is an internal tracking identifier

  2. Extract the NB_VMS_6.5.6_<6 digit number>.zip file.


  This release supports a very wide range of OpenVMS versions on
  different platforms including HP Integrity (IA64), Alpha (AXP)
  and  VAX systems.  The following OpenVMS versions are support-

  Supported OpenVMS Versions
  System                     From             To
  HP Integrity (IA64)        V8.2             V8.3
  HP Alpha (AXP)             V6.1             V8.3
  VAX Systems                V5.5             V7.3

  1. OpenVMS client release updates are zip archives that can be
  unzipped on your OpenVMS system.

  NOTE: If unzip is not already installed on  your  system,  and
  you want to install the archive quickly, you can unzip the ar-
  chive on any other UNIX or Windows system and then SSH/SCP  or
  FTP the executables to your OpenVMS system.

  This  release  update  zip archive contains the following exe-
  cutables for HP Integrity (IA64), Alpha (AXP)   and  VAX  sys-

  File Name                 Platform
  BPCD_I64.EXE     HP Integrity (IA64) BPCD service executable
  BPCD_AXP.EXE     Alpha (AXP) BPCD service executable
  BPCD_VAX.EXE     VAX BPCD service executable
  NBU_I64.EXE      HP Integrity (IA64) command line executable
  NBU_AXP.EXE      Alpha (AXP) NBU command line executable
  NBU_VAX.EXE      VAX NBU command line executable

  2. Unzip the archive using the following command:

  $ unzip
      extracting: bpcd_i64.exe
      extracting: bpcd_axp.exe
      extracting: bpcd_vax.exe
      extracting: nbu_i64.exe
      extracting: nbu_axp.exe
      extracting: nbu_vax.exe

  3. Copy the executable for your platform, or if you are  on  a
  mixed  cluster install the executable for each platform in the
  cluster, or copy the executables  for  all  platforms  to  the
  NBU$DIR directory:


  The NetBackup logicals names should already  be  defined,  for

  $ sh log nbu*








  4. After you have installed the release update, check that the
  newly installed version of BPCD is the one you  intended,  and
  that it is the same version as the NBU command line utility:

  NBU> sh vers
  %NBU-I-VERSION, Symantec NetBackup OpenVMS Client V6.5.6

  and show the client BPCD version

  NBU> sh client
  Patch Level:            6.5.6

  The  NetBackup  User's Guide for OpenVMS, which is included in
  this release as a PDF document, contains a more detailed  dis-
  cussion of the OpenVMS client.

Attachments (8.1 MBytes)

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices