On a Windows 2008/2012 Server, the following NetBackup services may fail to start:

• NetBackup Service Layer
• NetBackup Vault Manager
• NetBackup Event Manager
• NetBackup Remote Manager and Monitor Service
• NetBackup Policy Execution Manager
• NetBackup Storage Lifecycle Manager
• NetBackup Agent Request Server
• NetBackup Service Monitor
• NetBackup Indexing Manager

On a clustered (VCS or MSCS) NetBackup system where the cluster has not been frozen or taken offline, this problem can lead to the cluster failing over to a passive node because the NetBackup Service Layer is a monitored service.

The problem occurs on:

• A NetBackup 7.7.2 Windows server
• Prior NetBackup versions on a Windows server where:
• NBAC is enabled and USE_VXSS is set to AUTOMATIC or REQUIRED.
• Enhanced Auditing is enabled.

When nbsl is unable to start on NetBackup 7.7.2 and  nbsl logging is enabled with a higher verbosity on oid:137 (libraries) and oid:132 (nbsl), the nbsl logs under <install_path>\NetBackup\logs\nbsl contain messages similar to the following:

2/5/2016 20:44:51.826 [Debug] NB 51216 libraries 137 PID:1120 TID:3876 File ID:132 [No context] 1 [add_protocols] eat_home_dir :E:\Program Files\Veritas\NetBackup\sec\at(Orb.cpp:212)

2/5/2016 20:44:51.826 [Debug] NB 51216 libraries 137 PID:1120 TID:3876 File ID:132 [No context] 1 [add_protocols] eat_data_dir : E:\Program Files\Veritas\NetBackup\var\vxss\at(Orb.cpp:213)

2/5/2016 20:44:51.826 [Application] NB 51216 libraries 137 PID:1120 TID:3876 File ID:132 [No context] [Error] V-137-124 Cannot initialize ORB as the NetBackup install path contains a space and an equivalent short path name was not available. This failure can happen if 8dot3 name creation is disabled for the volume.

2/5/2016 20:44:51.826 [Diagnostic] NB 51216 libraries 137 PID:1120 TID:3876 File ID:132 [No context] 6 V-137-102 [Orb::init] CORBA exception: system exception, ID 'IDL:omg.org/CORBA/BAD_PARAM:1.0'

TAO exception, minor code = 0 (unknown location; unspecified errno), completed = NO during orb initialization

For NetBackup versions prior to 7.7.2, where NBAC is enabled and the current user is authenticated at the CLI level using bpnbat –login, subsequent execution of the nbemmcmd –listhosts and bptestnetconn commands will return the following errors:

D:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listhosts

NBEMMCMD, Version:7.1 Failed to initialize EMM connection. Verify that network access to the EMM server is available and that the services nbemm and pbx_exchange are running on theEMM server. (195) Command did not complete successfully.

D:\Program Files\Veritas\NetBackup\bin>bptestnetconn -c EMM/EMMServer -H MASTERSERVER -v adding hostname = MASTERSERVER

------------------------------------------------------------------------

Connecting to 'EMM/EMMServer'

CN: MASTERSERVER :    30 sec [TRANSIENT] PBX: Yes VNETD: Yes BPCD: Yes

------------------------------------------------------------------------

Total elapsed time: 30 sec

Review the admin log found at <install_path>\NetBackup\logs\admin:

******ERROR SECTION******

14:06:25.683 [3864.4936] <2> TAO: VxSSIOP (3864|4936) VxSSIOP_ORBInitializer::VxSSIOP_ORBInitializer - Setting EAT_HOME_DIR to D:\Program and EAT_DATA_DIR to D:\Program for AT initialization.

******ERROR SECTION******

14:06:25.714 [3864.4936] <2> TAO: VxSSIOP (3864|4936) VxSSIOP_ORBInitializer::VxSSIOP_ORBInitializer Failed to load AT v6.0 (err=24598) - reverting to v4.2

14:06:25.761 [3864.4936] <2> TAO: PBXVxSS (3864|4936) PBXVxSS_Singleton::set_init_handle: Failed to load AT v6.0 (err=24598) - reverting to v4.2

As highlighted in the error message above, a directory path has been truncated. The reference to D:\Program should actually be the longer path that begins with D:\Program Files\Veritas\.

For Windows versions prior to Windows 2012, all non 8.3 paths and file names are created with an associated 8.3 name on all volumes by default. However, if NetBackup is installed on a volume with 8.3 naming disabled, the associated 8.3 names will not be generated.

In Windows 2012, this behavior changed: only the system volume has 8.3 naming enabled and 8.3 naming is disabled by default on any newly-created volumes.

This fsutil command syntax will display the state of 8dot3 name creation for a given volume:

fsutil 8dot3name query <volume> 

For example:

C:\>fsutil 8dot3name query D:

The volume state is: 1 (8dot3 name creation is disabled).

The registry state is: 2 (Per volume setting - the default).

Based on the above two settings, the 8dot3 name creation is disabled on the D: drive.