In the protection group snapshot select "Copy Snapshot" for each volume being attached to the new system. Both the Log and Data volumes must be copied.
Give each new volume to be copied from a snapshot a name.
Once the volume(s) have been copied they will show up in the Storage View under Volumes.
Connect the new volumes to a host.
When the volumes have been connected, scan for them using the rescan-0scsi-bus.sh utility.
rescan-scsi-bus.sh -aIf the devices have been found then the utility will show output similar to the following image:
32 new or changed device(s) found.
[6:0:2:1]
[6:0:2:2]
[6:0:5:1]
[6:0:5:2]
[6:0:7:1]
[6:0:7:2]
[6:0:9:1]
[6:0:9:2]
[7:0:2:1]
[7:0:2:2]
[7:0:4:1]
[7:0:4:2]
[7:0:5:1]
[7:0:5:2]
[7:0:7:1]
[7:0:7:2]
[10:0:2:1]
[10:0:2:2]
[10:0:6:1]
[10:0:6:2]
[10:0:7:1]
[10:0:7:2]
[10:0:9:1]
[10:0:9:2]
[11:0:0:1]
[11:0:0:2]
[11:0:3:1]
[11:0:3:2]
[11:0:5:1]
[11:0:5:2]
[11:0:7:1]
[11:0:7:2]
If the "multipath -ll" command is used then the new volumes should show up in device-mapper-multipath.
Mount the new volumes to the relevant location.
mount /dev/mapper/3624a93701b16eddfb96a4c3800011c3c /hana/log
mount /dev/mapper/3624a93701b16eddfb96a4c3800011c3c /hana/log
Once mounted the volumes will show up at the relevant locations for SAP HANA.
Filesystem Size Used Avail Use% Mounted on
devtmpfs 1.5T 0 1.5T 0% /dev
tmpfs 2.2T 32K 2.2T 1% /dev/shm
tmpfs 1.5T 13M 1.5T 1% /run
tmpfs 1.5T 0 1.5T 0% /sys/fs/cgroup
/dev/mapper/3624a9370c49a4cb0e2944f4400038775-part2 60G 17G 44G 28% /
/dev/mapper/3624a9370c49a4cb0e2944f4400031d31 512G 43G 470G 9% /hana/shared
fileserver.puredoes.local:/mnt/nfs/HANA_Backup 1.0T 153G 872G 15% /hana/backup
tmpfs 290G 20K 290G 1% /run/user/469
tmpfs 290G 0 290G 0% /run/user/468
tmpfs 290G 0 290G 0% /run/user/1001
tmpfs 290G 0 290G 0% /run/user/0
/dev/mapper/3624a93701b16eddfb96a4c3800011c3b 5.0T 98G 5.0T 2% /hana/data
/dev/mapper/3624a93701b16eddfb96a4c3800011c3c 1.0T 73G 952G 8% /hana/log
Once the volumes have been mounted, SAP HANA needs to be informed that the system name has changed. Using the hdbnsutil utility as the <sid>adm user while the instance is completely shutdown will accomplish this.
hdbnsutil -convertTopology
If everything is as expected the output will be similar to the below, showing that the system name has been changed from the source to the target.
nameserver sarah:30001 not responding.
Opening persistence ...
sh1adm: no process found
hdbrsutil: no process found
run as transaction master
converting topology from cloned instance...
- keeping instance 00
- changing host hannah to sarah
done.
The instance can be started at this point. Any new or additional tenants will be automatically picked up from the data volume.
/usr/sap/hostctrl/exe/sapcontrol -nr <instance number> -function Start
To view if the Scale Up SAP HANA system has been brought up as expected, use the sapcontrol utility.
/usr/sap/hostctrl/exe/sapcontrol -nr <instance number> -function GetProcessList
If the instance has been started correctly then all of the processes should show the state "Green".
08.07.2020 05:39:38
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
hdbdaemon, HDB Daemon, GREEN, Running, 2020 07 08 05:38:58, 0:00:40, 33859
hdbcompileserver, HDB Compileserver, GREEN, Running, 2020 07 08 05:39:05, 0:00:33, 34158
hdbindexserver, HDB Indexserver-SH1, GREEN, Running, 2020 07 08 05:39:05, 0:00:33, 34212
hdbnameserver, HDB Nameserver, GREEN, Running, 2020 07 08 05:38:58, 0:00:40, 33877
hdbpreprocessor, HDB Preprocessor, GREEN, Running, 2020 07 08 05:39:05, 0:00:33, 34161
hdbwebdispatcher, HDB Web Dispatcher, GREEN, Running, 2020 07 08 05:39:17, 0:00:21, 41740
hdbindexserver, HDB Indexserver-SH2, GREEN, Running, 2020 07 08 05:39:05, 0:00:33, 34215
hdbindexserver, HDB Indexserver-SH3, GREEN, Running, 2020 07 08 05:39:05, 0:00:33, 34218
hdbindexserver, HDB Indexserver-SH4, GREEN, Running, 2020 07 08 05:39:05, 0:00:33, 34221