NBU 7.7.2 NBSL Issue?
I have a fresh Windows 2012 R2 x64 VM with a fresh install of NetBackup 7.7.2. Am I missing something on the connection aspect?
Everytime I try to login via the Java GUI, I get a time out on the "NetBackup Service Layer" which isn't running.
I try to manually run it, and does a start/stop.
All services appear to be running, but I do not see anywhere where I need to configure the initial setup for NetBackup.
have things changed for 7.7.2?
TECH199820
If its the same issue as below, enabling 8dot3 names on the volume is a workaround.
Enabling 137 and 132 logging and debug/ diag 6 would allow messages as shown in the technote to be seen in nbsl to confirm the same issue.
On a Windows 2003/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
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.
Error Message 
When NBSL is unable to start on NetBackup 7.7.2 and you enable NBSL logging on a higher verbosity for oid: 137 (libraries) and oid:132 (nbsl), the NBSL logs under the <installpath>\NetBackup\logs\nbsl displays the following messages
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 you authenticate the current user at the CLI level using ‘bpnbat –login’ and subsequently execute the following ‘nbemmcmd –listhosts’ and ‘bptestnetconn’ commands, you will see 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 <installpath>\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
Cause As seen in the above error message, a directory path has been erroneously truncated. The reference to "D:\Program" should actually be a longer path that begins with "D:\Program Files\Veritas\" .
For Windows 2003/2008, 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.
This behavior changed in Windows 2012: only the system volume has 8.3 naming enabled and it is disabled by default on any newly-created volumes.
Run the following command to check the state of 8dot3 name creation:
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.Solution There are two possible workarounds
Workaround 1: Enable/re-enable 8dot3name and set a short name:
Stop NetBackup services and follow these steps:- Set 8dot3name to enabled for the volume using this syntax:
fsutil 8dot3name set <volume> 0
Example:
C:\>fsutil 8dot3name set D: 0
Successfully enabled 8dot3name generation on D:NOTE: For more information on the fsutil command, see this Microsoft article: http://technet.microsoft.com/en-us/library/ff621566(v=ws.10).aspx
- Once 8dot3name is enabled on the volume, run this command to create the 8.3 folder name:
fsutil file setshortname "<path you want to set the shortname for>" <shortname>
Example:
C:\>fsutil file setshortname "D:\PROGRAM FILES" PROGRA~1NOTE: Run the above commands from a different drive than the drive on which you want to enable the 8dot3name to avoid an "Access Denied" error.
Refer to the article on 'fsutil file setshortname' at: http://technet.microsoft.com/en-us/library/bb490642.aspx
- (Optional) The 8dot3name can again be optionally disabled after confirming that NetBackup is up and running successfully, as:
fsutil 8dot3name set <volume> 1
Example:
C:\>fsutil 8dot3name set D: 1
Successfully disabled 8dot3name generation on D:Workaround 2: Reinstall NetBackup into a 8.3 path:
If you do not want to enable the 8dot3name parameter, just reinstall NetBackup on a 8.3 path.
It is possible to reinstall NetBackup into a directory structure that does not exceed the 8.3 naming conventions, for example C:\veritas\NetBackup\
This article describes how to relocate NetBackup to a different Drive Letter (the process would be the same for simply changing the Install Path).
https://www.veritas.com/support/en_US/article.TECH9558
Note: The workaround 2 applies to:- Windows 2003/2008 when NetBackup is installed on a volume where 8.3 naming is disabled, or
- Any Windows 2012 (and R2) data volume as 8.3 naming is disabled by default.
More details on this can be found at https://technet.microsoft.com/en-us/library/ff621566(v=ws.10).aspx
