Symptom
- Backup and restore scenario where it is necessary to match the number of services for Source and Target systems during system copy
- This also applies to system copy and migration scenarios where there is an error because the number of services/processes is not the same on the target and source systems
- When performing backup and restore from a source system to a target system
- When you have to match the number of services/processes on both source and target systems to enable a smooth backup and restore
- There might be similar error messages in the nameserver and indexserver trace files:
Error message similar to the error below is shown in the indexserver trace file or in the namseserver trace file or in the daemon trace file:
- RECOVERY RECOVER DATA finished with error: Recovery failed in nameserver startup: convert 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
- 3 scriptservers and 1 standby configured in source topology, 0 in destination system, mismatch
- 3 xsengines and 1 standby configured in source topology, 1 in destination system
- 1 indexservers configured in source topology, 2 in destination system
- 0 dpservers configured in source topology, 1 in destination system
Read more...
Environment
SAP Hana Database 1.0
Product
SAP HANA, platform edition all versions
Keywords
Recovery failed in nameserver startup; system copy; migration , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , How To
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.