Problem

DOCUMENTATION: Veritas NetBackup (tm) 5.0 general install, configuration and support for VMS clients

Solution
Manual: Veritas NetBackup (tm) 5.0 User's Guide for OpenVMS Modification Type:Supplement Modification: NetBackup Reference Information for VMS Clients. This document is divided into the following sections. System Information Networking Installation Configuration Policy Information Logging Backup and Restore Common VMS Commands In-house Test System References Review the NetBackup for VMS User's guide first on the ftp site: ftp://ftp.emea.veritas.com/pub/support/Products/NetBackup_OpenVMS/nbu_v5_0_vms_pdf.zip System Information To view details about the client, use the show command:
$ $ $ $ help show sh status sh system sh network

The 4.5 and 5.0 CD-ROM are available only by special order from the Americas Customer Care center which can be found at: http://symantec.custhelp.com/ For additonal information see section "Media and Licenses" in the user guide.

Run these commands to check that the install, startup of NetBackup, setup of the network, and bp.conf went well:
$ set def sys$sysdevice:[bpcd] $ @bpcd_startup $ set def sys$sysdevice:[openv.netbackup] $ run bpcd_axp (if the client is an alpha) $ run bpcd_vax (if the client is a VAX) NBU> sh ver NBU> sh server

If the "sh server" fails, putting in the IP address of the master server in the local bp.conf file is suggested. There may be problems reading NBU$CONFIG, so rerun @bpcd_startup.com.
NBU> sh client

This will first show the NetBackup version, then will connect to the current host client out through port 13782 in on source port where the client IP address is in parenthesis. All messages displayed are then from that client. A successful "sh client" request shows that the specified VMS client can respond to a TCP/IP connection request. Please note this will take a while to complete. For the latest OpenVMS VAX support, please reference the OpenVMS NetBackup User's guide "Supported OpenVMS Versions." ODS-5 file system support in NetBackup 5.0 MP1 supports the use of special characters.

Networking Networking on VMS may be provided via a number of different software packages, so it is important to clarify which one is being used. Examples include: UCX - DEC TCP/IP Multinet from Process Software TCPware Pathway from AttachMate

The following batch file defines bpcd parameters like port number: [openv.netbackup]bpcd_set_service.com Systems most commonly use multinet or UCX for networking. If using multinet, display and set values:
$ mu show/all $ mu config/serv server-config> show bpcd/full

For example, the following may help: set keepalive. This may help in preventing a socket from being treated as a broken link/pipe due to inactivity when a job is queued waiting for a tape drive.
server-config> server-config> server-config> server-config> select BPCD set keepalive 1800 write exit

From the client, see if bpcd is listening:

To re-initialize bpcd:
server-config> dis bpcd server-config> ena bpcd server-config> exit $ @multinet:start_server

If using UCX: To see if UCX/TCPIP is running, type:

Setting host file entries in UCX:

Is the NetBackup client software running on the VMS client?

To re-initialize bpcd:
$ ucx disable serv bpcd $ ucx enable serv bpcd

To test the communication to the master server from the client:

To test the communication from the master server to the OpenVMS client:
% telnet <client> 13782 % telnet <client ip_adr> 13782

Like other NetBackup client agents, the OpenVMS agent needs reverse name lookup to work. BPCD: This is the VMS Client service that responds to NetBackup Server requests. It is enabled as a TCP/IP service on the client VAX or Alpha. Backup and restore command line qualifiers, accepted by the above NetBackup utility are also accepted by this service; most client side

NetBackup qualifiers may also be specified from the server. VNETD is supported on the client starting with NetBackup 5.0 M1. Installation Keep in mind the latest bug fixes are in the latest release of the OpenVMS NetBackup agent. The OpenVMS 4.5 CD-ROM plus the latest downloadable OpenVMS MP6/MP7 will work correctly with 5.0 master and media servers. The initial installation of NetBackup 4.5 onto the VMS client requires a specially formatted CDROM for VMS: NetBackup 4.5 OpenVMS client CD or NetBackup 5.0 OpenVMS client CD. The chapter "CD ROM INSTALLATION" in the user guide should be followed for proper installation. Failure to do so will cause startup problems. This CD-ROM is in OpenVMS ODS-2 format which can only be mounted on OpenVMS systems. An upgrade of the NetBackup for VMS client binaries can be done by going to ftp://ftp.emea.veritas.com/pub/support/Products/NetBackup_OpenVMS/ and downloading nbu_v4_5_*.zip or nbu_v5_0_*.zip. For upgrades, follow exactly the "Maintenance Packs" chapter in the user guide. The file nbu_v4_5_vms_pdf.zip and nbu_v5_0_vms_pdf.zip are the user guide.

Configuration Setup: Verify that you have the following files: sys$sysdevice:[openv.netbackup]bpcd_set_service.com #sets bpcd tcp port, etc. sys$sysdevice:[bpcd]bpcd_startup.com #Its location is defined by bpcd_set_service.com. This starts bpcd listening. When a connection is made to the bpcd service, the first thing run is [BPCD]BPCD_STARTUP.COM which then runs the particular BPCD client (VAX or Alpha). Make sure that at boot time, the proper startup files are executed to create the NetBackup logicals. You can put them in SYSTARTUP_VMS.COM or just run them:
$ @bpcd_set_service $ @bpcd_startup $ set def sys$sysdevice:[openv.netbackup] $ type bp.conf $ edit bp.conf SERVER=<master server>

CLIENT_NAME=<client name> BUSY_FILE_DIRECTORY=[openv.netbackup] used BUSY_FILE_ACTION=[openv.netbackup] BUSY_FILE_PROCESSING=YES Exclude=CLASS:loki_backup Exclude=SCHED:full VERBOSE=5

# normal bp.conf directives can be

Press <Ctrl+Z> to save. If there are multiple NICs on the master, then put them all in the bp.conf file and put in all media servers. Example of an exclude list:
RA3SA1> show log nbu$exclude "NBU$EXCLUDE" = "NBU$DIR:RA3SA_EXCLUDE.LIS;" (LNM$SYSTEM_TABLE) RA3SA1>type nbu$exclude DSA334:[000000...]*.*;* DSA350:[000000...]*.*;* DSA366:[000000...]*.*;*

Example of email usage:

nbu$start and nbu$end "notify scripts" are explained in the user guide.

Policy Information Policy setup on the master: For the file list enter: # good for root disks # backup logs directory client name = <clientname>, Hardware = <doesn't matter>, OS = <doesn't matter> Make sure the NetBackup server's /etc/hosts file has entries for the VMS client. Reference the user guide if using the directive ALL_LOCAL_DRIVES to be a list of the local device names to back up. Usage of this requires the customer to set up a logical name search list on the client system.
DKB0:[000000...]/IGNORE=INTERLOCK DKB0:[openv.netbackup.logs]/IGNORE=INTERLOCK

Logging Logfiles:
[OPENV.NETBACKUP.LOGS]log.*

shows interaction with master server, shows restores

and backup params

Backup and Restore NBU: This is the VMS Client Side Utility, which provides a command line interface to the NetBackup server from the client. Backups and restores can be initiated from the client with this

utility, and backups on the server can be browsed with native VMS file specifications. Incremental backups explained, use of /RECORD and /MODIFIED --- See TechNote http://support.veritas.com/docs/265529 . This makes use of two policies, full uses the /RECORD directive, incr uses the /RECORD/MODIFIED directive. After a backup, the <dir /full> filename should get updated. Command line client-initiated disk-specific backup and restore logicals can be defined in a batch file like sylogin.com:
$ nbusrv :== "tcpip show serv bpcd" $ nbu :== "mcr nbu$bpcd" $ NBU BACKUP DSA500:[000000...]/IGNORE=INTERLOCK/CASE_SENSITIVE/POLICY=MT_VMS_TEST $ NBU RESTORE/ID=ARION_1098744085 [srcirtl.*.v400..]/exclude=(*.exe,*.obj;,*.map,*.lis,*.ana,*.sca,*.olb) /TO=$1$DGA31:[SCRIRTL...]

How to restore the log directory, list backed up files, show backup IDs, etc.: NBU> restore/log * # verbosely restore NBU> dir/last # lists files backed up NBU> dir/images # master server should be running, shows backupid in GMT
NBU> dir/INDENTIFIER=<xyz>/total NBU> dir filename # shows backed up file NBU> backup/log [000000] # verbosely backup directory

Incremental backups explained, use of /RECORD and /MODIFIED: http://support.veritas.com/docs/265529 For server initiated restores, use a trailing "/" for the destination directory. When doing a restore, set policy type as "standard" from /dkb0/abc/ to /dkb0/test/ or dkb0:\test\ Examples on how to wildcard restores from the client:
$ run [openv.netbackup]bpcd_axp NBU> restore dkb0:[openv.netbackup.logs]log.2004102*

Similar command run from the master server

It is best practice for a Windows GUI restore to do the following: 1. Should have an altpath folder: C:\Program Files\VERITAS\NetBackup\logs\AltPath 2. Use the File pulldown menu to select Client Properties and set the client to be the master server 3. Open up a window (restore or backup) 4. Use the File pulldown menu to specify NetBackup machines * If you cannot find a Client Destination tab, then select the system you are on or the client you are trying to restore in step 2.

Make current the source server, client, and destination client selections. 5. Select files to restore and restore using any of the three radio buttons: Use "/" directory (folder) delineator and make sure there is a trailing "/". For example, specify the path to restore as /DKB0/. For system disk backups and restores, the "System Disk Backups" chapter in the user guide describes the necessary steps for using writeboot.exe.

Common VMS commands: VMS Command Standard UNIX Command Equivalent or Definition cd (cd to root directory)

$ set def [000000] $ set def [openv.netbackup] $ dir /full/owner/sec $ dir nbu$config $ type bp.conf $ set prot/default | show prot $ create dir dsa900:[restore] $ show def $ sh logical nbu$dir $ sh logical nbu$config $ sh proc/all; sh system; sh users $ sh cluster $ analyze/image/interactive nbu$bpcd

cd to Netbackup install directory ls -l ls bp.conf cat bp.conf chmod mkdir restore pwd alias alias top; w show if cluster file bpcd_axp.exe; ldd bpcd_axp.exe, checks for errors, shows symbols

$ show device d $ sh sys $ define/log nbu$x xyz $ sh network $ sh dev/full dkb0: $ analyze/disk dkb0: $ sh memory/files

see if its a cluster, if so setup per TN#245341 uname alias ifconfig details of file system/disk show quotas show pagefiles (swap) should be marked as NOBACKUP see if bpcd is listening

$ telnet TELNET> connect clientname 13782 <cr> $ ucx sh com $ ucx sh interface $ tcpip TCPIP> sh serv ; exit TCPIP> disable service bpcd TCPIP> enable service bpcd $ logout $ @shutdown >>> boot $ mount/over=id dqa0: $ init/struct=5 dva0: _Label: test $ mount dva0: _Label: test

domainname netstat -ian (see if ftp service is running) Enable bpcd logout halt from prom mode, startup system mount floppy format a disk volume ODS-5 Disable bpcd

mount disk volume

_Log name: test

In-house Test System hostname: loki.min.veritas.com Alpha OpenVMS 7.2-1 References User Guide: ftp://ftp.emea.veritas.com/pub/support/Products/NetBackup_OpenVMS/ nbu_v5_0_vms_pdf.zip and nbu_v4_5_vms_pdf.zip

TechNote 268572: The sys$sysdevice:[sys0.syscommon.sysmgr] directory is part of the vms$common directory on the same disk. When checking the backup for the sys$sysdevice:[sys0.syscommon.sysmgr] directory, the backup stops at the sys$sysdevice:[sys0.syscommon] directory and does not go any deeper. http://library.veritas.com/docs/268572

TechNote 263497: Does VERITAS NetBackup (tm) have a client for OpenVMS? http://support.veritas.com/docs/263497 TechNote 265529: How to use the OpenVMS client incremental backup directives /RECORD and /MODIFIED http://support.veritas.com/docs/265529