In the protection group snapshot select "Copy Snapshot" for each volume being attached to the new system. All of the log and data volumes for the SAP HANA Scale Out deployment must be copied.
Give each new volume an appropriate name.
Connect the volumes to the SAP HANA Scale Out deployment(s) host group.
On all SAP HANA nodes in the Scale Out deployment, scan for the volumes.
rescan-scsi-bus-aIf the volumes have been found then the output should be as follows:
48 new or changed device(s) found.
[0:0:0:249]
[0:0:0:250]
[0:0:0:251]
[0:0:0:252]
[0:0:0:253]
[0:0:0:254]
[0:0:1:249]
[0:0:1:250]
[0:0:1:251]
[0:0:1:252]
[0:0:1:253]
[0:0:1:254]
[0:0:4:249]
[0:0:4:250]
Executing "multipath -ll" will show the devices in the below form. Take particular note of the first line of the device, noting the text starting with "3624a370". this will be needed for each of the new volumes at a later point.
3624a9370884890ea83bd488200011c82 dm-3 PURE,FlashArray
size=512G features='0' hwhandler='1 alua' wp=rw
`-+- policy='queue-length 0' prio=50 status=active
|- 0:0:0:254 sdf 8:80 active ready running
|- 0:0:7:254 sdx 65:112 active ready running
|- 0:0:4:254 sdr 65:16 active ready running
|- 0:0:2:254 sdl 8:176 active ready running
|- 1:0:4:254 sdah 66:16 active ready running
|- 1:0:9:254 sdaz 67:48 active ready running
|- 1:0:6:254 sdat 66:208 active ready running
`- 1:0:5:254 sdan 66:112 active ready running
The SAP HANA Storage API connector is going to use the world wide identifiers (WWID's) to ensure the correct volumes are attached to the appropriate hosts. The record of the WWIDs is found in the /hana/shared/<SID>/global/hdb/custom/config/global.ini configuration file.
It may be necessary to compare the source systems global.ini configuration file as the volumes will need to match the partition number given to the disk type.
Source System global.ini:
[storage]
ha_provider = hdb_ha.fcClient
partition_*_*__prtype = 5
partition_1_data__wwid = 3624a9370884890ea83bd488200011c47
partition_1_log__wwid = 3624a9370884890ea83bd488200011c4a
partition_2_data__wwid = 3624a9370884890ea83bd488200011c48
partition_2_log__wwid = 3624a9370884890ea83bd488200011c4b
partition_3_data__wwid = 3624a9370884890ea83bd488200011c49
partition_3_log__wwid = 3624a9370884890ea83bd488200011c4c
Source system volumes (using purevol list) and serial numbers:
Name Size Source Created Serial
SHN-HANA-Data01 512G - 2020-07-07 08:20:41 PDT 884890EA83BD488200011C49
SHN-HANA-Data02 512G - 2020-07-07 08:20:41 PDT 884890EA83BD488200011C48
SHN-HANA-Data03 512G - 2020-07-07 08:20:40 PDT 884890EA83BD488200011C47
SHN-HANA-Log01 384G - 2020-07-07 04:28:37 PDT 884890EA83BD488200011C4C
SHN-HANA-Log02 384G - 2020-07-07 04:28:37 PDT 884890EA83BD488200011C4B
SHN-HANA-Log03 384G - 2020-07-07 04:28:37 PDT 884890EA83BD488200011C4ATarget systems global.ini:
[storage]
ha_provider = hdb_ha.fcClient
partition_*_*__prtype = 5
partition_1_data__wwid = 3624a9370884890ea83bd488200011c82
partition_1_log__wwid = 3624a9370884890ea83bd488200011c85
partition_2_data__wwid = 3624a9370884890ea83bd488200011c87
partition_2_log__wwid = 3624a9370884890ea83bd488200011c84
partition_3_data__wwid = 3624a9370884890ea83bd488200011c86
partition_3_log__wwid = 3624a9370884890ea83bd488200011c83
Target system volumes (using purevol list) and serial numbers:
Name Size Source Created Serial
SAP-HANA-Data01-Copy 512G SHN-HANA-Data01 2020-07-08 06:11:16 PDT 884890EA83BD488200011C86
SHN-HANA-Data02-Copy 512G SHN-HANA-Data02 2020-07-08 06:11:16 PDT 884890EA83BD488200011C87
SHN-HANA-Data03-Copy 512G SHN-HANA-Data03 2020-07-08 06:11:16 PDT 884890EA83BD488200011C82
SHN-HANA-Log01-Copy 384G SHN-HANA-Log01 2020-07-08 06:11:16 PDT 884890EA83BD488200011C83
SHN-HANA-Log02-Copy 384G SHN-HANA-Log02 2020-07-08 06:11:16 PDT 884890EA83BD488200011C84
SHN-HANA-Log03-Copy 384G SHN-HANA-Log03 2020-07-08 06:11:16 PDT 884890EA83BD488200011C85
Note that the topology matching of the source and target Scale Out system follows the below logic:
SHN1 -> SHN5
SHN2 -> SHN6
SHN3 -> SHN7
SHN4 -> SHN8Once the global.ini file has been updated, login as the <sid>adm user and use the hdbnsutil utility to check for the system name changes and update the topology.
hdbnsutil -convertTopologyIf all of the prerequisites are in place, in the event of a successful topology conversion the output will look like the below:
sh1adm@SHN5:/usr/sap/SH1/HDB00> hdbnsutil -convertTopology
nameserver shn5:30001 not responding.
checking 1 master lock file(s) ........................................ ok
load(/usr/sap/SH1/HDB00/exe/python_support/hdb_ha/fcClient.py)=1
attached device '/dev/mapper/3624a9370884890ea83bd488200011c82' to path '/hana/data/SH1/mnt00001'
attached device '/dev/mapper/3624a9370884890ea83bd488200011c85' to path '/hana/log/SH1/mnt00001'
Opening persistence ...
sh1adm: no process found
run as transaction master
converting topology from cloned instance...
- keeping instance 00
- changing host shn1 to shn5
- changing host shn2 to shn6
- changing host shn3 to shn7
- changing host shn4 to shn8
detached device '/dev/mapper/3624a9370884890ea83bd488200011c82' from path '/hana/data/SH1/mnt00001'
detached device '/dev/mapper/3624a9370884890ea83bd488200011c85' from path '/hana/log/SH1/mnt00001'
done.At this point the Scale Out system can be started. This is done using the sapcontrol utility.
/usr/sap/hostctrl/exe/sapcontrol -nr <instance number>-function StartSystem HDBTo check what the status of the system is use the sapcontrol utility with the GetSystemInstanceList function.
/usr/sap/hostctrl/exe/sapcontrol -nr 00 -function GetSystemInstanceListWhen the system has been successfully started all of the nodes should be shown to be "Green".
hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus
shn5, 0, 50013, 50014, 0.3, HDB|HDB_WORKER, GREEN
shn8, 0, 50013, 50014, 0.3, HDB|HDB_STANDBY, GREEN
shn6, 0, 50013, 50014, 0.3, HDB|HDB_WORKER, GREEN
shn7, 0, 50013, 50014, 0.3, HDB|HDB_WORKER, GREEN