NetBackup 7.5 - NB client will not start because of Private Branch Exchange Service
I have a system which the NetBackup Client 7.5.0.3 and will not start because of the following error from the Event Viewer: > A timeout was reached (30000 milliseconds) while waiting for the Symantec Private Branch Exchange service to connect. > The Symantec Private Branch Exchange service failed to start due to the following error: >The service did not respond to the start or control request in a timely fashion. > A timeout was reached (30000 milliseconds) while waiting for the Symantec Private Branch Exchange service to connect. I have tried setting the time out to 60000, but it didn't work. Any ideas?Ready; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks
BE 2012 - After migration, storage pools but no storage devices
Migrated our BE 2012 server using the steps in the article below. We moved from a Win2K8 R2 Enterprise OS to Win2K8 R2Standard OS for licensing reasons. Everything seemed to migrate successfully except for the storage devices which are simply network drives/shares. In the BE console on the new BE server, the storage pools, that were on the old BE server, are there and the properties of the storage pools show the related storage devices. The problem is that the storage devices do not show up as individual devices on the storage tab of the BE console, so I cannot edit the properties or even use them with the migrated backup jobs. I tried renaming the old BE server and taking it offline, then renaming the new BE server to the old BE server name, but I could not log into BE using the old or new name after that. I put the new name back into place so now I'm back at square one again. I thought about just configuring new storage devices with new names but I'm concerned about how that will affect my ability to restore existing backed up data that is on these drives. Ideally, I would like to get some help on how I can get this migrated BE server to recognize the storage devices again. https://support.symantec.com/en_US/article.TECH129826.html Thank You, RAoprd returned abnormal status (96)
Hi, I am not able to get media manager daemons after bouncing Netbackup Daemons. And i got this error #./vmoprcmd -d oprd returned abnormal status (96) IPC Error: Daemon may not be running Logs of daemon & reqlib & ltid as below:- Ltid:- 01:21:23.746 [23332] <4> CheckShutdownWhileInit: Pid=1, Data.Pid=25157, Type=100, Param1=0, Param2=-5056, LongParam=-23490544 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-01 is ACTIVE 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-02 is ACTIVE 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-03 is ACTIVE 01:21:24.281 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-06 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-07 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-08 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-10 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive DLT8000-12 is ACTIVE 01:21:24.282 [23332] <16> InitLtidDeviceInfo: Drive IBM_ULTRIUM2_Drv07 is ACTIVE reqlib:- 01:00:01.207 [23580] <2> EndpointSelector::select_endpoint: performing call with the only endpt available!(Endpoint_Selector.cpp:431) 01:00:01.220 [23580] <2> EndpointSelector::select_endpoint: performing call with the only endpt available!(Endpoint_Selector.cpp:431) 01:01:40.430 [23805] <4> vmoprcmd: INITIATING 01:01:40.488 [23805] <2> vmoprcmd: argv[0] = vmoprcmd 01:01:40.488 [23805] <2> vmoprcmd: argv[1] = -d 01:01:40.488 [23805] <2> vmdb_start_oprd: received request to start oprd, nosig = yes 01:01:40.527 [23805] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2046: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006 01:01:40.527 [23805] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2060: service: vmd 01:01:40.623 [23805] <2> getrequestack: server response to request: REQUEST ACKNOWLEDGED 650 01:01:40.649 [23805] <2> getrequeststatus: server response: EXIT_STATUS 0 01:01:40.649 [23805] <4> vmdb_start_oprd: vmdb_start_oprd request status: successful (0) 01:02:57.220 [23805] <2> wait_oprd_ready: oprd response: EXIT_STATUS 278 01:02:57.221 [23805] <2> put_string: cannot write data to network: Broken pipe (32) 01:02:57.221 [23805] <16> send_string: unable to send data to socket: Broken pipe (32), stat=-5 Deamon:- 01:07:42.537 [24144] <4> rdevmi: INITIATING 01:07:42.537 [24144] <2> mm_getnodename: cached_hostname tcppapp001, cached_method 3 01:07:42.583 [24144] <2> mm_ncbp_gethostname: GetNBUName <tcppapp001-bip> 01:07:42.583 [24144] <2> mm_getnodename: (5) hostname tcppapp001-bip (from mm_ncbp_gethostname) 01:07:42.584 [24144] <2> rdevmi: got CONTINUE, connecting to ltid 01:08:02.755 [24098] <16> oprd: device management error: IPC Error: Daemon may not be running 01:08:03.241 [23355] <2> vmd: TCP_NODELAY 01:08:03.242 [23355] <4> peer_hostname: Connection from host tcppvmg265-bip, 172.16.6.7, port 6735 01:08:03.335 [23355] <4> process_request: client requested command=43, version=4 01:08:03.335 [23355] <4> process_request: START_OPRD requested 01:08:03.369 [23355] <4> start_oprd: /usr/openv/volmgr/bin/oprd, pid=24164 01:08:03.638 [23355] <2> vmd: TCP_NODELAY 01:08:03.638 [23355] <4> peer_hostname: Connection from host tcppvmg265-bip, 172.16.6.7, port 18394 01:08:03.685 [23355] <4> process_request: client requested command=43, version=4 01:08:03.685 [23355] <4> process_request: START_OPRD requested Please help me out how toget rid of this issue and what is this issue about.