SAP Knowledge Base Article - Preview

3378174 - SAP HANA restore fails with peer is not allowed

Symptom

Getting an peer not allowed error when restoring the TenantDB restore on then same appliance.

Restore failed error: 
Backint SAP HANA restore fails with peer is not allowed to request restore to client...

BACKUP.log
2023-04-12T14:37:16-04:00  P3611198      18776c1f809 INFO    RECOVERY INQUIRE started [1681324636169]
2023-04-12T14:37:16-04:00  P3611198      18776c1f809 INFO    RECOVERY command: BACKUP LIST DATA FOR XY1 UNTIL TIMESTAMP '2023-04-12 18:35:41' USING CATALOG PATH ('/tempbackup/AAA/archive/DB_XY1') LIMIT 10
2023-04-12T14:37:16-04:00  P3611198      18776c1f809 INFO    RECOVERY using backup catalog 1681323912526 from /tempbackup/AAA/archive/DB_XY1/log_backup_0_0_0_0.1681323912526
2023-04-12T14:37:16-04:00  P3611198      18776c1f809 INFO    RECOVERY INQUIRE finished successfully
2023-04-12T14:37:34-04:00  P3611455      18776c23e14 INFO    RECOVERY INQUIRE started [1681324654100]
2023-04-12T14:37:34-04:00  P3611455      18776c23e14 INFO    RECOVERY command: BACKUP CHECK ACCESS FOR XY1 BACKUP_ID 1680633345676 USING CATALOG PATH ('/tempbackup/AAA/archive/DB_XY1')
2023-04-12T14:37:34-04:00  P3611455      18776c23e14 INFO    RECOVERY using backup catalog 1681323912526 from /tempbackup/AAA/archive/DB_XY1/log_backup_0_0_0_0.1681323912526
2023-04-12T14:37:35-04:00  P3611455      18776c23e14 INFO    RECOVERY INQUIRE finished successfully
2023-04-12T14:38:02-04:00  P3611987      18776c2adce INFO    RECOVERY INQUIRE started [1681324682702]
2023-04-12T14:38:02-04:00  P3611987      18776c2adce INFO    RECOVERY command: BACKUP CHECK ACCESS FOR XY1 BACKUP_ID 1681322910284 USING CATALOG PATH ('/tempbackup/AAA/archive/DB_XY1')
2023-04-12T14:38:02-04:00  P3611987      18776c2adce INFO    RECOVERY using backup catalog 1681323912526 from /tempbackup/AAA/archive/DB_XY1/log_backup_0_0_0_0.1681323912526
2023-04-12T14:38:03-04:00  P3611987      18776c2adce INFO    RECOVERY INQUIRE finished successfully
2023-04-12T14:38:16-04:00  P3612153      18776c2e5a1 INFO    RECOVERY INQUIRE started [1681324696993]
2023-04-12T14:38:16-04:00  P3612153      18776c2e5a1 INFO    RECOVERY command: BACKUP LIST DATA FOR XY1 UNTIL TIMESTAMP '2023-04-12 18:35:41' USING CATALOG PATH ('/tempbackup/AAA/archive/DB_XY1') LIMIT 10
2023-04-12T14:38:17-04:00  P3612153      18776c2e5a1 INFO    RECOVERY using backup catalog 1681323912526 from /tempbackup/AAA/archive/DB_XY1/log_backup_0_0_0_0.1681323912526
2023-04-12T14:38:17-04:00  P3612153      18776c2e5a1 INFO    RECOVERY INQUIRE finished successfully
2023-04-12T14:38:25-04:00  P3612539      18776c3073b INFO    RECOVERY INQUIRE started [1681324705595]
2023-04-12T14:38:25-04:00  P3612539      18776c3073b INFO    RECOVERY command: BACKUP CHECK ACCESS FOR XY1 BACKUP_ID 1681322910284 USING CATALOG PATH ('/tempbackup/AAA/archive/DB_XY1')
2023-04-12T14:38:25-04:00  P3612539      18776c3073b INFO    RECOVERY using backup catalog 1681323912526 from /tempbackup/AAA/archive/DB_XY1/log_backup_0_0_0_0.1681323912526
2023-04-12T14:38:26-04:00  P3612539      18776c3073b INFO    RECOVERY INQUIRE finished successfully
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY RECOVER DATA started [1681325160513]
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY command: RECOVER DATABASE FOR XY1 UNTIL TIMESTAMP '2023-04-12 18:35:41' CLEAR LOG USING CATALOG PATH ('/tempbackup/AAA/archive/DB_XY1') USING LOG PATH ('/tempbackup/AAA/archive/DB_XY1') USING DATA PATH ('/usr/sap/AAA/SYS/global/hdb/backint/DB_XY1/') USING BACKUP_ID 1681322910284 CHECK ACCESS USING FILE
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY using backup catalog 1681323912526 from /tempbackup/AAA/archive/DB_XY1/log_backup_0_0_0_0.1681323912526
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY The following strategy is used:
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY from backint: 2023-04-12_14-08_XY1_databackup_0_1 in /usr/sap/AAA/SYS/global/hdb/backint/DB_XY1 ebid VXP11681322911_------------------
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY from backint: 2023-04-12_14-08_XY1_databackup_2_1 in /usr/sap/AAA/SYS/global/hdb/backint/DB_XY1 ebid VXP11681322921_------------------
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY from file: log_backup_2_0_58114752_58189632.1681323012498 in /tempbackup/AAA/archive/DB_XY1
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY from file: log_backup_2_0_58189632_58248256.1681323912500 in /tempbackup/AAA/archive/DB_XY1
2023-04-12T14:46:00-04:00  P3615481      18776c9f841 INFO    RECOVERY state of service: indexserver, finhd1-rr-001:33549, volume: 0, RecoveryExecuteTopologyRecoveryInProgress
2023-04-12T15:46:07-04:00  P3615481      18776c9f841 INFO    RECOVERY state of service: indexserver, finhd1-rr-001:33549, volume: 0, RecoveryError
2023-04-12T15:46:07-04:00  P3615481      18776c9f841 ERROR   RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, [110088] Error reading backup from 'BACKINT' '/usr/sap/AAA/SYS/global/hdb/backint/DB_XY1/2023-04-12_14-08_XY1_databackup_0_1', [110203]
Not all data could be written: Expected 4096 but transferred 0


BACKINT.log
2023-04-12 14:46:00.567 backint started:
  command: /usr/sap/AAA/SYS/global/hdb/opt/hdbbackint -f restore -p /usr/openv/netbackup/ext/db_ext/sap/scripts/sap_oracle/initSAPMTHLY.utl -i /var/tmp/hdbbackint_AAA.FZs08T -o /var/tmp/hdbbackint_AAA.uFJAGT -u AAA
  pid: 3615705
  input:
  #SOFTWAREID "backint 1.04" "HANA HDB server 2.00.059.06.1666783180"
  #EBID VXP11681322911_------------------ "/usr/sap/AAA/SYS/global/hdb/backint/DB_XY1/2023-04-12_14-08_XY1_databackup_0_1" "/usr/sap/AAA/SYS/global/hdb/backint/DB_XY1/2023-04-12_14-08_XY1_databackup_0_1"

2023-04-12 15:46:06.958 backint terminated:
  pid: 3615705
  exit code: 0
  output:
  #SOFTWAREID "backint 1.04" "Veritas NetBackup backint 0.1"


AAAadm.xxx.log
14:26:47.836 [4174744] <4> get_Policy_Methodtype: Start get_Policy_Methodtype.
14:26:47.836 [4174744] <4> init_VxBSA_env: Enter!
14:26:47.836 [4174744] <4> init_VxBSA_env: BSA_API_VERSION=1.1.0
14:26:47.836 [4174744] <4> init_VxBSA_env: BSA_SERVICE_HOST=------------------
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_CLIENT_HOST=------------------
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_POLICY=BKPDB_SAP-NA-NA-NA-HANA_24H7D_NA_DEFAULT
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_SCHEDULE=SAP_MTHLY
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_DB_TYPE=SAP
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_LOG_DIRECTORY=backint
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_FEATURE_ID=40
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_NUM_STREAMS=1
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_RETRY_COUNT=0
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_SORT_TYPE=size
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_KEYWORD=sap_hana_AAA
14:26:47.836 [4174744] <4> init_VxBSA_env: NBBSA_USE_OBJECT_GROUP=1
14:26:47.836 [4174744] <4> init_VxBSA_env: Exit!

14:26:47.903 [4174744] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_CLIENT_HOST
14:26:47.903 [4174744] <4> VxBSAGetEnv: INF - returning - ------------------

14:26:48.025 [4174744] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_CLIENT_HOST
14:26:48.025 [4174744] <4> VxBSAGetEnv: INF - returning - ------------------

14:26:48.173 [4174750] <4> get_Policy_Methodtype: Start get_Policy_Methodtype.
14:26:48.173 [4174750] <4> init_VxBSA_env: Enter!
14:26:48.173 [4174750] <4> init_VxBSA_env: BSA_API_VERSION=1.1.0
14:26:48.173 [4174750] <4> init_VxBSA_env: BSA_SERVICE_HOST=------------------
14:26:48.173 [4174750] <4> init_VxBSA_env: NBBSA_CLIENT_HOST=#SOFTWAREID
14:26:48.279 [4174750] <2> bprd_connect_need_auth: Ignoring local_name #SOFTWAREID.
14:26:48.279 [4174750] <2> bprd_connect_need_auth: Ignoring owner_name AAAadm.
14:26:48.279 [4174750] <2> vnet_same_host_and_update: [vnet_addrinfo.c:3255] Comparing name1:[------------------] name2:[localhost]
14:26:48.280 [4174750] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5588] targaddr=1xx.xxx.xxx.xx prefnet=ANY
14:26:48.280 [4174750] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5602] prefnet =  ANY
14:26:48.280 [4174750] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5588] targaddr=1xx.xxx.xxx.xx prefnet=ANY
14:26:48.280 [4174750] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:5602] prefnet =  ANY
14:26:48.280 [4174750] <2> async_connect: [vnet_connect.c:2887] connect in progress 1 0x1
14:26:48.281 [4174750] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded


Read more...

Environment

SAP HANA DB Version 2.0

Keywords

KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.