NetWorker: HP OpenVMS - File System Backup Troubleshooting Guide

Step 1: Problem Overview:

Identify the following:

• What action is being performed? (backup, restore.)
• What is the scope of the problem? (single client, many clients)
  • For many clients identify what is similar between the problem clients, and what is different from the functioning clients.
• When did the problem first appear? Were there any changes in the environment around the time that this problem appeared?
• Is this a consistent or intermittent problem?
  • For intermittent issues, is there anything specific about when the problem appears? For example, runtime, the number of other jobs running when the issue appears? Or is it random?
• Is this a new client or configuration?
  • For new configurations or issues that appeared after upgrades, see the NetWorker compatibility matrix to ensure system supportability: E-Lab Interoperability Navigator 2.0-HOME (Requires Dell Support Account Sign-In)

Step 2: Basic environment gathering:

• From the NetWorker backup server:
  • Hostname
  • OS type, platform, and version
  • NetWorker version, and build number
  • The above details can be collected from the following: NetWorker: Methods for Identifying NetWorker Software version
  • When engaging NetWorker support, collect an NSRGET bundle: NetWorker: How to Use the NSRGet NetWorker Data Collection Tool
  • For backup issues, collect the policy logs folder from the NetWorker server:
    • Linux: /nsr/logs/policy/POLICY_NAME/WORKFLOW_NAME
    • Windows (Default): C:\Program Files\EMC NeTWorker\nsr\logs\policy\POLICY_NAME\WORKFLOW_NAME\
• From the OpenVMS client:
  • Hostname
  • OS type, platform, and version 
    The commands:
    product show product *
product show history
  • NetWorker version, and build number
    The commands:
    product show history/producer=lgto
@nsr$system:nsr$versions
  • Gather any additional environment information: Example, this is a standalone, or clustered environment?
  • Optionally run EMCreports for OpenVMS (attached to this Knowledge Article).
  • Collect log files from NSR$LOGS: On the OpenVMS host

Step 3: Initial Troubleshooting:

The following things are unique to OpenVMS:

• To define a NetWorker command: <command> :== $nsr$system:<command>
• Any token on a command line that is upper case has to be quoted with the double-quotes [ " ]
• OpenVMS has unique file specification names device:[path.path...]filename.type;version may or may not be case-dependent.
  Example:

save :== $nsr$system:save
save "-D3" -s myserver -g "MyGroup Name" "DISK$ALPHA:[000000]foo.txt;1" 
logs are in nsr$logs on the OpenVMS client
$ sho log  nsr$*

(LNM$PROCESS_TABLE)

(LNM$JOB_81E9FD80)

(LNM$GROUP_000001)

(LNM$SYSTEM_TABLE)

  "NSR$BITMAPS" = "NSR$SYSROOT:[NSR.BITMAPS]"
  "NSR$COMMON" = "SPIRAL$DKA0:[SYS0.SYSCOMMON.NSR$SPIRAL.NSRCOMMON.]"
  "NSR$LOGS" = "NSR$SYSROOT:[NSR.LOGS]"
  "NSR$RES" = "NSR$SYSROOT:[NSR.RES]"
  "NSR$SPECIFIC" = "SPIRAL$DKA0:[SYS0.SYSCOMMON.NSR$SPIRAL.]"
  "NSR$SYSROOT" = "NSR$SPECIFIC:"
        = "NSR$COMMON:"
  "NSR$SYSTEM" = "NSR$SYSROOT:[NSR]"
  "NSR$TMP" = "NSR$SYSROOT:[NSR.TMP]"

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)
$

Step 4: Run a sample save from the client until you re-create the problem.

1. Define the save command: save :== $nsr$system:save
2. Run the save command using the following syntax: save -s <NetWorker_server_name> -b <Pool_name> "DISK$xxxx"  where xxxx will be noted in the failed backup.
3. Run the backup policy from the NetWorker server.
4. Results:
   1. Review the output and search the knowledgebase for articles that may relate to the errors found.
   2. If the results are not conclusive. Collect the information from steps 1 and 2 along with the results of the testing performed. Provide this information to NetWorker support.