Backup of SAP HANA with multitenant database container with netbackup.
Hi, I have one query? We have netbackup 7.7.2 and SAP HANA with multitenant database container. For one instance we have to do following configurations on SAP HANA studio: Create hdbbackint soft link from /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint to /usr/openv/NetBackup/bin/hdbbackint_script for every database instance. The parameter file (initSAP.utl) must be specified for data in the SAP HANA database instance configuration. To specify the parameter file, go to Instance->Configuration-> global.ini > data_backup_parameter_file. The parameter file (initSAP.utl) must be specified for logs in the SAP HANA database instance configuration. To specify backup using the parameter file, go to Instance->Configuration->global.ini-> log_backup_parameter_file. To specify backup using the backint file, go to Instance->Configuration->global.ini-> log_backup_using_backint->SYSTEM = true. My problem is that how to configure backup for multitenant database container (For multiple Instance ) We have cluster "Dev" with multitenant database container having 3 instance "Dev" "Quality" and "SystemDB" The problem is that DBA is telling that create hdbbackint soft link from /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint to /usr/openv/NetBackup/bin/hdbbackint_script . DBA inform us that,It is not possible due to Database instances in SAP HANA database will be in hidden mode. So we cannot create the links. Requesting you to help me in this. Server Details: Master Server. Client/Master = Master NetBackup Client Platform = PC-x64, WindowsXP NetBackup Client Protocol Level = 7.7.2 Product = NetBackup Version Name = 7.7 Version Number = 770000 NetBackup Installation Path = D:\Program Files\Veritas\NetBackup\bin Client OS/Release = Windows2008 6 SAP HANA Client . Client/Master = Client of IRBIDCQCSER001.irb.local NetBackup Client Platform = Linux, SuSE3.0.76 NetBackup Client Protocol Level = 7.7.2 Product = NetBackup Version Name = 7.7 Version Number = 770000 NetBackup Installation Path = /usr/openv/netbackup/bin Client OS/Release = Linux 3.0.101-0.47.67-default
Backup exec remote agent service stuck in stopping state.
I have face the below issue many times. Operating systame - Windows 2008 or Windows 2008 R2. Backup Exec 2012 having SP 3 installed. Most of the time when we restart the backup exec services, that time "Backup exec remote agent service" get stuck in stopping state. And in this stage we fail to stop and then start the service. Even taskkill command also desen't work to kill the beremote.exe process. And in this situation every time we require to reboot the server and then we found all backup exec services in running state properly. Does any one have solution on this? Regards, Santosh Pawar.
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.
