SAP HANA tenant restore is failed (HANA 2.0 SP1)

[former_member450836]

I have a SAP HANA 2.0 SP1 backup and restore setup. I am using backint (Veritas Netbackup 8.0) interface to perform backup and restore.

I am able to perform SYSTEMDB backup and restore using backint inerface without any issues. The moment I fire the restore for the Tenant database, the SAP HANA Studio fails with "Restoration is failed" with no log information. But I could see the restore opeartion is in progress and completed in the NetBackup "Activity Monitor".

I found couple of error's in the "nameserver_alert_xxx.trc" file which shows the following..

[123525]{100128}[-1/-1] 2017-07-28 21:29:12.776039 e EmbeddedAPI Connection.cc(00360) : exception 1: no.70012019 (TrexNet/BufferedIO.cpp:1180) timeout occured; $TYPE$=ReadTimeout; $MESSAGE$=a timeout occured while reading from the channel; $INFO$=timeout occured; $PARAM$=active channel (since 30007722mues) 128 from 41450 to 127.0.0.1:31003 with method core/flushtrace with id 8726005753007075886 on host xxxxx on port 31001 from process hdbnameserver with service port 31001, pid 123297 and tid 123525 exception throw location: [123429]{-1}[-1/-1] 2017-07-28 21:29:29.218060 e TNS_Timing LocalWatchDog.cpp(00254) : LocalWatchDog takes 36 seconds for 'indexserver@xxxx:31003'. Communication problem or interval (10 seconds) too short?

I have SAP HANA Studio which is installed on Windows server. There is no time mismatch between the Linux host and the Windows server.

Please suggest if you have come across this error.

Regards,

Vasu

[lsueiras]

Hi,

I have the same problem with Netbackup and hana 2.0 SP1. I tried to put the listening interfaces in global, etc, but always have the same Hana Studio error.

Any ideas?

Regards.

[former_member209962]

Hi Vasu,

Did you check Veritas Netbackup 8.0 supports tenant db backup and restore? also before starting the restore what all prerequisites you are doing?

Thanks

Tabrayz

[former_member183326]

Can you upload a full system dump to this location?

https://mdocs.sap.com/mcm/public/v1/open?shr=bOm06vYpsQMWInF-hQpk2M5il2sgLc7-IqQgAjfMK4s

The problem may be with your vendor.