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?oprd 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 to get rid of this issue and what is this issue about.
Exchange GRT Restore send notification to user
Looking for suggestions on how to turn off notifications on mailbox restores when using the Exchange GRT with a Netbackup 7 environment. While this feature is useful when the user requests a restore, it's not so good when the restore is requested by Security. Any thoughts? Below is the message that shows up: Subject: Symantec NetBackup initialization message for mailbox restore. Symantec Backup Exec for Windows Servers has restored one or more items to your mailbox. After verifying that all requested items have been restored, you can delete this message. For more information, contact your system administrator and refer to the job history for job Currently running NBU 7 on Windows 2K8. Is this an Exchange setting or Netbackup? It gets sent from the service account that was created.
Netbackup AIR - restricting REPLICATION jobs
I have a situuation whereby the link between two NBU sites / domains has been inactive for some time, and the link has now been upgraded and is available again. I suspended secondary operations on the SLP's in the primary site during this period, and as a result now have a couple of thousand images awaiting replication to the secondary site. Before I re-enable the secondary operations on the SLP's I want to ensure that I don't have hundreds of replicaton jobs starting at once, as I have seen this in the past and the system becomes unresponsive. How can I limit the amount of replication jobs that will be submitted as I want to limit this to a manageable number (say 20 concurrent). I know I can limit the amount of streams on the Storage Server / Disk Pool, but I am afraid that the replications will all kick in and the backups will not have any available streams to work with. Bottom line - I want to continue to allow my backups to run but also have a limited number of replication jobs running concurrently allongside them. Any input appreciated. AJ