Copy the Snapshot to a New Volume
Using the FlashArray Web GUI navigate to the Storage view, and under Volumes identify the SAP HANA data volume(s). The volume in the image below is the SAP-HANA-Data volume for a Scale Up instance. Focus on the Volume Snapshots Section and identify the point in time for the recovery, this is done using the "Created" field. Note also that Snapshot names in this scenario are shown with "SAP-HANA-Data-SAPHANA-BackupID". In a normal recovery using the SAP HANA backup catalog, the backup ID can be used to match the recovery point to a volume snapshot.
In the Volume Snapshots view select the 3 ellipses in the upper right hand corner to expose the options. In this scenario, the volume snapshot is going to be copied to a new volume. It is also possible to overwrite the existing volume with the snapshot.
Give the new volume a name. If a volume exists with the same name, then it may be necessary to overwrite it by setting the overwrite option.
Once completed , the volume should not show up in the list of volumes on the FlashArray, this can be seen in Storage, under the Volumes section:
Disconnect the old volume (if the volume has been copied)
Once the volume has been copied, then the original SAP HANA Data volume needs to be disconnected from the host and the new volume for recovery connected to the host. This can be done in Storage, under hosts - find the relevant SAP HANA Host. To disconnect the original volume either select the 3 ellipses in the upper right hand corner and select disconnect volume of "Connect Volumes" or use the "x" next to the volume.
Prompt when selecting the "x":
Selecting the 3 ellipses and using "Disconnect".
Once the original SAP HANA Data volume has been disconnected, the operating system must be informed that the SAP HANA Data volume has been removed. To do so - execute the following to check for and remove missing volumes:
rescan-scsi-bus.sh -rIf the volumes have been removed properly, then at the end of the command executing it will show output similar to this:
16 device(s) removed.
[2:0:0:1]
[2:0:2:1]
[2:0:5:1]
[2:0:7:1]
[4:0:1:1]
[4:0:2:1]
[4:0:5:1]
[4:0:8:1]
[7:0:2:1]
[7:0:3:1]
[7:0:6:1]
[7:0:7:1]
[8:0:1:1]
[8:0:3:1]
[8:0:8:1]
[8:0:9:1]
Connect the New Volume (if the Volume has been Copied)
In Storage, under the Hosts view find the host to connect the new SAP HANA Data volume to. Find the section for "Connected Volumes" In the Host properties and select the 3 ellipses in the top right hand corner.
In the option which appears, select "Connect..."
Select the new SAP HANA Data Volume and then select "Connect".
The volume should now be connected. At this point the operating system needs to scan for the new volume. use the following command to scan for any new volumes:
rescan-scsi-bus.sh -aIf the new volume has been found then the output should contain something similar to the below:
16 new or changed device(s) found.
[2:0:0:1]
[2:0:2:1]
[2:0:5:1]
[2:0:7:1]
[4:0:1:1]
[4:0:2:1]
[4:0:5:1]
[4:0:8:1]
[7:0:2:1]
[7:0:3:1]
[7:0:6:1]
[7:0:7:1]
[8:0:1:1]
[8:0:3:1]
[8:0:8:1]
[8:0:9:1]
Mount the Data Volume(s)
Scale Up
If the volume has been copied or overwritten during recovery, these steps are all the same for a Scale Up environment.
Identify the SAP HANA Data volume using the following command:
multipath -llThe output will show a number of devices, but the first line of the device information contains the device serial number (this is the text starting with 3624a9730).
3624a93701b16eddfb96a4c3800011c36 dm-5 PURE,FlashArray
size=5.0T features='0' hwhandler='1 alua' wp=rw
`-+- policy='queue-length 0' prio=50 status=active
|- 2:0:7:1 sds 65:32 active ready running
|- 2:0:5:1 sdq 65:0 active ready running
|- 2:0:2:1 sdo 8:224 active ready running
|- 2:0:0:1 sdm 8:192 active ready running
|- 4:0:5:1 sdy 65:128 active ready running
|- 4:0:2:1 sdw 65:96 active ready running
|- 4:0:1:1 sdu 65:64 active ready running
|- 4:0:8:1 sdaa 65:160 active ready running
|- 7:0:7:1 sdai 66:32 active ready running
|- 7:0:6:1 sdag 66:0 active ready running
|- 7:0:3:1 sdae 65:224 active ready running
|- 7:0:2:1 sdac 65:192 active ready running
|- 8:0:1:1 sdak 66:64 active ready running
|- 8:0:9:1 sdaq 66:160 active ready running
|- 8:0:8:1 sdao 66:128 active ready running
`- 8:0:3:1 sdam 66:96 active ready running
Viewing the volume information the serial number can be matched up to the device.
Once the device has been identified, it needs to be mounted to the SAP HANA data volume location identified in Step 1.
mount /dev/mapper/3624a93701b16eddfb96a4c3800011c36 /hana/dataIf the device has mounted successfully then when executing "df" in the command line it should be displayed:
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 2377876496 0 2377876496 0% /dev
tmpfs 3568402432 32 3568402400 1% /dev/shm
tmpfs 2377886844 20568 2377866276 1% /run
tmpfs 2377886844 0 2377886844 0% /sys/fs/cgroup
/dev/mapper/3624a9370c49a4cb0e2944f440002d735-part2 62883840 18672736 44211104 30% /
/dev/mapper/3624a9370c49a4cb0e2944f440002dc76 536608768 44161756 492447012 9% /hana/shared
tmpfs 475577368 24 475577344 1% /run/user/469
tmpfs 475577368 0 475577368 0% /run/user/468
tmpfs 475577368 0 475577368 0% /run/user/0
/dev/mapper/3624a93701b16eddfb96a4c3800011c31 1073217536 550628920 522588616 52% /hana/log
fileserver.puredoes.local:/mnt/nfs/HANA_Backup 524032000 154021888 370010112 30% /hana/backup
/dev/mapper/3624a93701b16eddfb96a4c3800011c36 5366622188 583412144 4783210044 11% /hana/data
Once the recovery is completed it is recommended that the device is set to permanently mount at startup by editing the /etc/fstab entry.
Scale Out
In a scale out scenario, if the volumes have been overwritten no further action is needed.
If the volumes have been copied to new volumes, additional steps are required to inform SAP HANA of the world wide identifiers(WWIDs) have changed.
To update the WWID's for SAP HANA open the following file in a text editor : /hana/shared/<SID>/global/hdb/custom/config/global.ini.
Identify the [storage] section, this contains the WWID'ss, the sections containing "partition_N_data_wwid" need to be updated with the new volume values.
[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
To get the new volume values execute the following:
mutliapth -llThe WWID for each volume is the first identifier for each device-mapper device. These values need to be taken to update the global.ini file.
3624a9370884890ea83bd488200011c61 dm-3 PURE,FlashArray
size=512G features='0' hwhandler='1 alua' wp=rw
`-+- policy='queue-length 0' prio=50 status=active
|- 0:0:0:252 sdd 8:48 active ready running
|- 0:0:1:252 sdj 8:144 active ready running
|- 0:0:4:252 sdp 8:240 active ready running
|- 0:0:7:252 sdv 65:80 active ready running
|- 1:0:4:252 sdaf 65:240 active ready running
|- 1:0:5:252 sdal 66:80 active ready running
|- 1:0:6:252 sdar 66:176 active ready running
`- 1:0:7:252 sdax 67:16 active ready running
3624a9370884890ea83bd488200011c60 dm-4 PURE,FlashArray
size=512G features='0' hwhandler='1 alua' wp=rw
`-+- policy='queue-length 0' prio=50 status=active
|- 0:0:0:253 sde 8:64 active ready running
|- 0:0:1:253 sdk 8:160 active ready running
|- 0:0:4:253 sdq 65:0 active ready running
|- 0:0:7:253 sdw 65:96 active ready running
|- 1:0:4:253 sdag 66:0 active ready running
|- 1:0:5:253 sdam 66:96 active ready running
|- 1:0:6:253 sdas 66:192 active ready running
`- 1:0:7:253 sday 67:32 active ready running
3624a9370884890ea83bd488200011c5f dm-5 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:1:254 sdl 8:176 active ready running
|- 0:0:4:254 sdr 65:16 active ready running
|- 0:0:7:254 sdx 65:112 active ready running
|- 1:0:4:254 sdah 66:16 active ready running
|- 1:0:5:254 sdan 66:112 active ready running
|- 1:0:6:254 sdat 66:208 active ready running
`- 1:0:7:254 sdaz 67:48 active ready running
Once the global.ini file has been updated it should have the new WWID values:
[storage]
ha_provider = hdb_ha.fcClient
partition_*_*__prtype = 5
partition_1_data__wwid = 3624a9370884890ea83bd488200011c61
partition_1_log__wwid = 3624a9370884890ea83bd488200011c4a
partition_2_data__wwid = 3624a9370884890ea83bd488200011c60
partition_2_log__wwid = 3624a9370884890ea83bd488200011c4b
partition_3_data__wwid = 3624a9370884890ea83bd488200011c5f
partition_3_log__wwid = 3624a9370884890ea83bd488200011c4c
Once the global.ini file has been updated, if the volumes have been copied, then the master nameserver needs to be identified and the SAP HANA instance on it started.
View the text of the following file: /hana/shared/<SID>/global/hdb/custom/config/nameserver.ini. Identify the [landscape] section and find the "active_master" property. the value in this section is the node that the instance gets started on.
[landscape]
id = d65820d1-16fd-014d-a076-140d78db92ca
master = shn1:30001 shn2:30001 shn4:30001
worker = shn1 shn2 shn3
active_master = shn1:30001
standby = shn4
roles_shn4 = standby
roles_shn2 = worker
roles_shn3 = worker
roles_shn1 = worker
workergroups_shn4 = default
failovergroup_shn4 = default
workergroups_shn2 = default
failovergroup_shn2 = default
workergroups_shn3 = default
failovergroup_shn3 = default
workergroups_shn1 = default
failovergroup_shn1 = default
Further recovery must take place on the active_master nameserver. All commands executed for the Scale Out environment needs to be done from the master_nameserver.