Starting the Target System

On the management console, shut down the five servers of the target system.
Change the physical IP addresses of the primary and extended NICs of the five servers in the target system from the transition IP addresses to the production IP addresses of the source system. Bind the virtual IP addresses of the ASCS/ERS servers in the source system to the primary NICs of the ASCS/ERS servers in the target system.
On the management console, power on the five servers of the target system.
Check the /etc/hosts files on the five servers in the target system and ensure that the IP addresses match the domain names or host names. Ensure that the target HANA host name is different from the source host name. Change the HANA host name if the target system uses the source one.
Mount the SFS shared directory.

Mount the shared file system for database backup in the source system to the /etc/fstab file on the target database server.

Mount the shared file system for mounting /sapmnt/ and /usr/sap/trans on the source application servers to the /etc/fstab file on the target application servers.
Log in to the database server as a database user and run the HDB start command to start the database. After the database is started, log in to the database using HANA Studio and check whether the database is normal.
Log in to each application server and run the following command as an application user to check the database connection. If 00 is displayed in the command output, the database connection is normal.
```
hdbuserstore list
R3trans –d
```
Change the SBD device ID in /etc/sysconfig/sbd on the active and standby ASCS/ERS nodes to the actual device ID and rebuild the SBD disk.
```
sbd –d  /dev/disk/by-id/scsixxxxx   -4 30 -1 15 create
```
Start the ASCS and ERS.

Start the two-node cluster and set it to the maintenance status.
```
service pacemaker start
crm configure property maintenance-mode=true
```
Run the crm configure edit command to access the two-node cluster configuration page and change the ASCS/ERS shared disk ID to the actual disk ID of the target system.

Stop the maintenance status of the cluster.
```
crm configure property maintenance-mode=false
```
Check the cluster resources. Ensure that the ASCS/ERS resources are in the started status.
```
crm status
```
Log in to the PAS/AAS servers as an application user, start the PAS and AAS, check their process, and check the application status on SAP.
```
sapcontrol -nr [Instance ID] -function Start
sapcontrol -nr [Instance ID] –function GetProcessList
```