Unable to recover stg system with prd backup and even stg backup

[Former Member]

Hi,

I am trying to recover new staging system with  Data backup file.

first:  I did try with production system backup file it failed with

error:

recovery failed in name server startup: check services against topology

failed: mismatch: 2 Xsengines configured in source topology, 0 standby

in source topology, 1in destination system.

then I did try with stag system backup(we just tack this backup before

start recovery process).

but again recovery process failed with error:

RECOVER DATA finished with error:

Recovery failed in nameserver startup: check services against topology

failed: mismatch: 1 statisticsservers configured in source topology, 0

standby in source topology, 2 in destination system, mismatch: 1

xsengines configured in source topology, 0 standby in source topology,

2 in destination system

1. both the system are similar configuration( but stg system is new dont have data)

2. why i am unable to perform recovery with stg backup also?

3. is there ant way we can bring the server without recovery?

please let me know is there any way we can bring the server?.

Thanks

Ravindar

[Former Member · Accepted solution]

Hi All,

I was just able to solve the problem.

Solution Found:

Found active reservations to the LUNs that are showing issues(Master node volumes 😞

lun 32 (Partition 1 – Data)

ResKey  : AF2ABE064EAC49B9

ResWWN  :  20000????????F:200000??????????  (Node 5)

lun 34 (Partition 1 – Log)

ResKey  : AF2ABE064EAC49B9

ResWWN  :  200000???????:2000000?????  (Node 4)

On those nodes I can mount those particular LUNs, but when I umount it won’t release the lock.

I used the following commands to remove the reservation locks:

sg_persist /dev/dm-7

sg_persist --out --register --param-sark=1 /dev/dm-7

sg_persist /dev/dm-7

sg_persist --out -C -K 1 /dev/dm-7

I was able to mount the Log LUN but the Data LUN mounted with errors.  I umounted and ran xfs_repair –L and now everything is working!  We still need EMC and SUSE to help determine root cause.  The How and why we got into this state.

Thanks & Regards,

Ravindar Nalla                                         

[Former Member]

Hi ravinder wait for  Swapan Saha  reply many times swapan solved the smiler issues .

thank you

[Former Member]

Hi all,

how is possible two statisticsservers in one SAP HANA system?.

error message: mismatch: 1 statisticsservers configured in source topology,

0 standby in source topology,

2 in destination system,

mismatch: 1 xsengines configured in source topology,

0 standby in source topology,

2 in destination system

[Former Member]

Hi ravindar , if you check the daemon.ini file for different nodes on HANA server, you'll see there're 2 nodes having the same content in their daemon.ini

  can help you

[Former Member]

Hi Poorna,

this is new system.

and i did check the daemon.ini files in all nodes.

even i did delete and try the recovery process but still same error message.

and even I did try its Owen data backup still same error.

deamon.ini:

[indexserver]

name=HDB Indexserver

executable=hdbindexserver

arguments=

startdir=${SAP_RETRIEVAL_PATH}

runlevel=3

instances=1

stdout=${SAP_RETRIEVAL_PATH}/trace/indexserver1.out

stderr=

flags=COMPRESSBACKUP

[indexserver.c]

name=HDB Tenant Indexserver on Port 3$(SAPSYSTEM)$(INSTANCE:2)

executable=hdbindexserver

arguments=-port 3$(SAPSYSTEM)$(INSTANCE:2)

startdir=${SAP_RETRIEVAL_PATH}

runlevel=3

instanceids=

stdout=${SAP_RETRIEVAL_PATH}/trace/indexserver2.out

stderr=

flags=COMPRESSBACKUP

[preprocessor]

name=HDB Preprocessor

executable=hdbpreprocessor

arguments=

startdir=${SAP_RETRIEVAL_PATH}

runlevel=2

instances=1

stdout=${SAP_RETRIEVAL_PATH}/trace/preprocessor1.out

stderr=

flags=COMPRESSBACKUP

[nameserver]

name=HDB Nameserver

executable=hdbnameserver

arguments=

startdir=${SAP_RETRIEVAL_PATH}

runlevel=1

instances=1

stdout=${SAP_RETRIEVAL_PATH}/trace/nameserver.out

stderr=

flags=COMPRESSBACKUP

[scriptserver]

name=HDB Scriptserver

executable=hdbscriptserver

arguments=

startdir=${SAP_RETRIEVAL_PATH}

runlevel=3

instances=0

stdout=${SAP_RETRIEVAL_PATH}/trace/scriptserver.out

stderr=

flags=COMPRESSBACKUP

[statisticsserver]

name=HDB Statisticsserver

executable=hdbstatisticsserver

arguments=

startdir=${SAP_RETRIEVAL_PATH}

runlevel=3

instances=0

stdout=${SAP_RETRIEVAL_PATH}/trace/statisticsserver.out

stderr=

flags=COMPRESSBACKUP

[xsengine]

name=HDB XSEngine

executable=hdbxsengine

arguments=

startdir=${SAP_RETRIEVAL_PATH}

runlevel=3

instances=0

stdout=${SAP_RETRIEVAL_PATH}/trace/xsengine1.out

stderr=

flags=COMPRESSBACKUP

[sapwebdisp]

name=SAP WebDispatcher

executable=sapwebdisp_hdb

arguments=pf=${SAP_RETRIEVAL_PATH}/wdisp/sapwebdisp.pfl -f ${SAP_RETRIEVAL_PATH}/trace/dev_webdisp

startdir=${DIR_INSTANCE}

starttime=5000

environment=

runlevel=4

instances=0

stdout=${SAP_RETRIEVAL_PATH}/trace/sapwebdisp.out

stderr=

flags=COMPRESSBACKUP

[compileserver]

name=HDB Compileserver

executable=hdbcompileserver

arguments=

startdir=${SAP_RETRIEVAL_PATH}

runlevel=2

instances=1

stdout=${SAP_RETRIEVAL_PATH}/trace/compileserver.out

stderr=

flags=COMPRESSBACKUP

followed by this sap note: 1905462 - HANA scale-out landscape : topology mismatch leads to recovery failure

note: is there any way can we bring the server without recovery process??

Thanks

Ravindar