The Symantec NetBackup 7.1_ET2323007 OpenVMS client release update is
now available
for HP Integrity (IA64), Alpha (AXP) and VAX systems from Veritas
support:

ftp://ftp.emea.veritas.com/pub/support/Products/NetBackup_OpenVMS/NB_VMS_7.1_ET2323007.zip

I would like to add that we are working on testing HP Integrity (IA64)
10GbE networking with OpenVMS 8.4.

The RELEASE_NOTES are as follows:


   March 24, 2011
   The Symantec NetBackup 7.1_ET2323007 OpenVMS Client

   ==============================================================
   The Symantec NetBackup 7.1_ET2323007  OpenVMS  client  release
   update  is  now available for HP Integrity (IA64), Alpha (AXP)
   and VAX systems.
   ==============================================================


   ==============================================================
   PACK DEPENDENCIES
   ==============================================================

   -- There are no pack dependencies for this release.

   I.   NEW FEATURES AND ENHANCEMENTS
   II.  KNOWN ISSUES
   III. MD5SUM's
   IV.  DOWNLOAD INSTRUCTIONS
   V.   INSTALLATION INSTRUCTIONS

   ==============================================================
   I.   NEW FEATURES AND ENHANCEMENTS
   ==============================================================

   This  release contains the following new features, changes and
   enhancements:-

   1. Support for 7.0, 7.0.1 and 7.1 master and media servers.

   2. This release will report a successful backup, instead of  a
   partially  successful  backup,  for backup selections where no
   files are found.

   3. This release corrects an error on checkpoint enabled  back-
   ups which hang and eventually fail.

   4. In addition to the above, this release will resume suspend-
   ed checkpoint enabled backups correctly.

   5. This release will only backup the data used in a file,  in-
   stead of the entire file allocation.  For devices with a large
   cluster size and a large number of small  files  this  release
   should improve backup performance.

   6.  This release includes md5sum executables which can be used
   to check the validity of a CD/DVD or release update  download.
   For example, the NetBackup 7.1 OpenVMS client install ISO (see
   section 5 of the installation instructions below).

   7. This release will not allow the length of the  disk  backup
   AST  QIO  request queue to grow larger than the current TCP/IP
   AST stack queue performance.  This prevents the backup process
   (even  with  very large astlm and biolm quotas) from consuming
   the entire systems resources.

   8. Support for the BPCD_GET_CHARSET_RQST server request.

   9. The server "EMM status: disk volume resource request failed
   (status 800)" status is now reported to DCL command procedures
   as an error status (and not a  success).  New  system  message
   files  have been provided for HP Integrity, Alpha and VAX sys-
   tems.

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

   11. 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
   SS$_NOMOREFILES.

   12. OpenVMS cluster nodes which share a common bootable system
   disk  also  share  a common bp.conf (NBU$CONFIG) configuration
   file.   In  such  a  case  it  is  not  possible  to  set  the
   CLIENT_NAME (in the bp.conf file) for an individual node.

   This  release  supports the NBU$CLIENT_NAME logical name which
   can be defined to the client name of an individual node.

   13. 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.

   14.Support for all server admin bptestbpcd command client  re-
   quest codes.

   15.  This release queues backup data to the TCP/IP stack asyn-
   chronously. This means, that client backup  data  send()'s  to
   the  media  server  nolonger block - they are simply queued as
   AST QIO requests.  This keeps the TCP/IP stack busy and allows
   the  client  to  spend  more  time processing the file system.
   This should improve backup performance.

   The length of the AST QIO queue is limited by  the  biolm  and
   astlm  quotas (whichever is lower).  The astlm should be equal
   to or greater than the biolm quota.

   16. Support  for  the  /PROGRESS  qualifier  which  shows  the
   progress  of  a  backup or restore most clearly when specified
   without the /LOG qualifier. For example:

   NBU> backup/prog dka100:[000000...]
   %NBU-I-CONNECT, from titan (192.168.0.67,49156) to omega
(192.168.0.21,13720)
   %NBU-I-BACKBID, titan_1276267802 11-JUN-2010 09:50:02
   %NBU-I-BKFSPEC, dka100:[000000...]*.*;*/PROGRESS
   %NBU-I-PROGRES,   2.9 GB (5702104 blocks) in 0 00:01:00 secs
(48657.95 KB/sec)
   %NBU-I-PROGRES,   5.9 GB (11628027 blocks) in 0 00:02:00 secs
(49612.92 KB/sec)
   %NBU-I-PROGRES,   9.3 GB (18220698 blocks) in 0 00:03:00 secs
(51827.76 KB/sec)
   %NBU-I-PROGRES,  12.5 GB (24458649 blocks) in 0 00:04:00 secs
(52178.45 KB/sec)
   %NBU-I-PROGRES,  15.8 GB (30956497 blocks) in 0 00:05:00 secs
(52832.42 KB/sec)
   %NBU-I-PROGRES,  19.2 GB (37579376 blocks) in 0 00:06:00 secs
(53446.22 KB/sec)
   %NBU-I-PROGRES,  21.4 GB (41921996 blocks) in 0 00:07:00 secs
(51104.91 KB/sec)
   %NBU-I-PROGRES,  23.5 GB (46029030 blocks) in 0 00:08:00 secs
(49097.63 KB/sec)
   %NBU-I-PROGRES,  26.2 GB (51184597 blocks) in 0 00:09:07 secs
(47909.53 KB/sec)
   %NBU-I-PROGRES,  27.6 GB (54016640 blocks) in 0 00:10:07 secs
(45562.64 KB/sec)
   %NBU-I-PROGRES,  29.8 GB (58349324 blocks) in 0 00:11:07 secs
(44789.89 KB/sec)
   %NBU-I-NETWORK,  30.3 GB (59293184 blocks) in 0 00:11:20 secs
(44644.28 KB/sec)
   %NBU-I-ASTUSED, used 800 of 800 biolm quota (astlm 1600)
   %NBU-S-NETBACK, saved 87500 files (59293184 blocks)
   %NBU-S-SERVMSG, the requested operation was successfully completed
(status 0)
   NBU>

   17. This release shows the ASTUSED usage (as shown above) on a
   backup  or  restore.   Both  will  try  and use as much of the
   available biolm and astlm quota as  possible.   The  available
   quota  is  most  efficiently used when backing up or restoring
   large files.  Systems which  consistently  use  their  maximum
   quota may have the capacity to improve performance by increas-
   ing the available quota.

   18. The NBU_HELP.BCK backup save-set contains an updated  help
   library.  Set the save-set file attributes:

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

   extract the NBU.HLB library:

   $ backup/log nbu_help.bck/save []/new
   %BACKUP-S-CREATED, created DKB100:[VERITAS]NBU.HLB;2
   $

   and copy it to the SYS$HELP: directory:

   $ cop nbu.hlb sys$help:
   %COPY-S-COPIED, DKB100:[VERITAS]NBU.HLB;2 copied to SYS$SYSROOT:
[SYSHLP]NBU.HLB;8 (48 blocks)
   $

   Type the NBU> HELP command for help.



   ==============================================================
   II.  KNOWN ISSUES
   ==============================================================

   There are no known issues with this release update.


   ==============================================================
   III. MD5SUM's
   ==============================================================

   $ md5sum *.exe
   972db6c4fe375404c2301909c323a722  BPCD_AXP.EXE;1
   83e8959233203ae7b394e3ed810b2872  BPCD_I64.EXE;1
   d23ca9e2fdc50886eafafdc74e5a90b3  BPCD_VAX.EXE;1
   667d4148793444b43c4467783473ec2a  MD5SUM_AXP.EXE;1
   b3aacd804b551615e96b38001807d352  MD5SUM_I64.EXE;1
   0934c2a7bc00ef49d458d7b536a0c095  MD5SUM_VAX.EXE;1
   dbf2a5333ea96bfe1e479725963e8079  NBUAXPMSG.EXE;1
   5d9a72b6631f2683a46146cea2016185  NBUI64MSG.EXE;1
   e898ac7ad92e3a9b13e2d47f52f28799  NBUVAXMSG.EXE;1
   972db6c4fe375404c2301909c323a722  NBU_AXP.EXE;1
   83e8959233203ae7b394e3ed810b2872  NBU_I64.EXE;1
   d23ca9e2fdc50886eafafdc74e5a90b3  NBU_VAX.EXE;1
   $


   ==============================================================
   IV.  DOWNLOAD INSTRUCTIONS
   ==============================================================

   1. OpenVMS client release updates are available from support:

   ftp://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/

   File  names  which  start  with  the prefix NB_VMS are OpenVMS
   client release updates.



   ==============================================================
   V.   INSTALLATION INSTRUCTIONS
   ==============================================================

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

   Supported OpenVMS Versions
   --------------------------------------------------------------
   System                     From             To
   --------------------------------------------------------------
   HP Integrity (IA64)        8.2              8.3
   HP Alpha (AXP)             6.1              8.3
   VAX Systems                5.5              7.3
   --------------------------------------------------------------


   1.  OpenVMS  client release updates are zip archives which can
   be unzipped on OpenVMS or any other system.  The archive  con-
   tains  updates  for  HP Integrity (IA64), Alpha (AXP)  and VAX
   systems.

   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:

   $ unzip NB_VMS_7.1_<six digit number>.zip
    ...
       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. And copy the executables for all platforms, or just the ex-
   ecutables for the current platform, to a new higher version in
   the netbackup directory:

   $ COPY/LOG BPCD*.EXE,NBU*.EXE  SYS$SYSDEVICE:[OPENV.NETBACKUP]

   The executables for each platform have different  names  which
   represent  the  executable  architecture, where the last three
   characters are I64 for HP Integrity, AXP for Alpha and VAX for
   VAX.

   The  NetBackup  logicals  names should already be defined, for
   example:

   $ sh log nbu*

   (LNM$PROCESS_TABLE)

   (LNM$JOB_80DB3000)

   (LNM$GROUP_000001)

   (LNM$SYSTEM_TABLE)

     "NBU$BPCD" = "NBU$DIR:BPCD_AXP.EXE"
     "NBU$CONFIG" = "NBU$DIR:BP.CONF"
     "NBU$DIR" = "SYS$SYSDEVICE:[OPENV.NETBACKUP]"
     "NBU$LOGS" = "SYS$SYSDEVICE:[OPENV.NETBACKUP.LOGS]"

   (LNM$SYSCLUSTER_TABLE)

   (DECW$LOGICAL_NAMES)
   $

   Define the NBU symbol as a foreign command (include the  lead-
   ing $ character):

   $ NBU :== $NBU$BPCD

   the  NBU  command will now run the current NBU$BPCD executable
   for your system.

   4. After you have installed the release update, check that the
   newly  installed version of BPCD is the one that you intended,
   type the NBU command:

   $ NBU
   NBU> sh vers
   %NBU-I-VERSION, Symantec NetBackup OpenVMS Client V7.1_ET2323007

   and show the client BPCD version

   NBU> sh client
    ...
   Patch Level:            7.1_ET2323007
    ...

   The patch level and version should be the same.

   5. Install the md5sum DCL command by  copying  the  executable
   for your system to the sys$common:[sysexe] directory.

   For  example, on a HP Integrity system copy the MD5SUM_I64.EXE
   executable:

   $ copy MD5SUM_I64.EXE sys$common:[sysexe]

   and define the MD5SUM symbol as a foreign command (include the
   leading $ character):

   $ md5sum :== $sys$common:[sysexe]md5sum_i64.exe

   The  md5sum  command  can  be  used to check the validity of a
   CD/DVD download. For example, a download of the the  NetBackup
   7.1 OpenVMS client install ISO shows the following md5sum:

   $ md5sum NetBackup_71_OpenVMS.iso
   81d6fb2b4032e8fc1baddfb94211d055  NetBackup_71_OpenVMS.iso;1
   $

   6.  The  NetBackup User's Guide for OpenVMS, which is included
   in this download as a PDF document, contains a  more  detailed
   discussion of the OpenVMS client.


alan_fay@symantec.com

On Mar 25, 5:09 pm, Alan Fay <alan_...@symantec.com> wrote:

> [...]
> The RELEASE_NOTES are as follows:
>  [...]

   I'm reluctant to complain about one of the all-too-rare
relevant postings here, but you couldn't just post a link?
(Is the browser-free audience so large?)

On Mar 25, 5:46=A0pm, Steven Schweda <sms.antin...@gmail.com> wrote:
> On Mar 25, 5:09 pm, Alan Fay <alan_...@symantec.com> wrote:
>
> > [...]
> > The RELEASE_NOTES are as follows:
> > =A0[...]
>
> =A0 =A0I'm reluctant to complain about one of the all-too-rare
> relevant postings here, but you couldn't just post a link?
> (Is the browser-free audience so large?)


Steven,

The link should be:

ftp://ftp.emea.veritas.com/pub/support/Products/NetBackup_OpenVMS/NB_VMS_7.=
1_ET2323007.zip

I'm not sure why browsers are saying this is redirect -- its not. If
you are not sure just go to the complete directory:

ftp://ftp.emea.veritas.com/pub/support/Products/NetBackup_OpenVMS/

and select the file that you want.

Alan

On Mar 25, 6:15 pm, Alan Fay <alan_...@symantec.com> wrote:

> I'm not sure why browsers are saying this is redirect -- its not.

   It depends on what you're browsing.  Google Groups, for
example, fiddles with hyperlinks, so that what you see is not
exactly where you're sent.  (This allows them to collect info
on who follows what to where, among other things.)  Any decent
browser should show you what's about to happen before you
actually click on a link.

   Everything's complicated.

On Mar 25, 8:19=A0pm, Steven Schweda <sms.antin...@gmail.com> wrote:
> On Mar 25, 6:15 pm, Alan Fay <alan_...@symantec.com> wrote:
>
> > I'm not sure why browsers are saying this is redirect -- its not.
>
> =A0 =A0It depends on what you're browsing. =A0Google Groups, for
> example, fiddles with hyperlinks, so that what you see is not
> exactly where you're sent. =A0(This allows them to collect info
> on who follows what to where, among other things.) =A0Any decent
> browser should show you what's about to happen before you
> actually click on a link.
>
> =A0 =A0Everything's complicated.


I have been asked "What is the md5sum for this download, I can't find
it and how can I check this on my OpenVMS system?"

Install the md5sum DCL command on your system as shown in section 5 of
the above installation instructions and then you can check the md5sum.

This is a good question, as we cannot include the release md5sum in
the release as it would then change the md5sum (never ending circle).

The md5sum for this release on an OpenVMS (or any other) system is as
follows:

$ md5sum NB_VMS_71_ET2323007.ZIP
a0b2c65413870e68ab7eb36079ed830e  NB_VMS_71_ET2323007.ZIP;1
$

Alan