- Migrate older versions of HANA One to the latest HANA One Rev 52.1 (HANA Upgradable)
- Migrate HANA contents from HANA Dev Edition to HANA One Rev 52.1 (HANA Upgradable)
SAP released HANA One Rev 38, HANA One Rev 48 and HANA Rev 52 prior to the releasing HANA One Rev 52.1. HANA One Rev 52.1 has self-service upgrade capability via Addon Manager [blog]. Customers using HANA One Rev 52.1 can continuously upgrade to the latest HANA version as a self-service option and can also extend 1 year license key at its expiry or install a valid license key, if needed. However, customers using HANA One prior to HANA One Re 52.1, cannot upgrade HANA nor can extend license key. This blog provides a step by step procedure to migrate older releases of HANA One to the latest HANA One to take advantage of new Addon feature in HANA One Rev 52.1.
With the availability of HANA License Key 1.0 in HANA One Rev 52.1 from September 23 2013, customers can use database backup and recovery (system copy) to migrate their HANA contents from HANA One Rev 48 or HANA One Rev 52 to HANA One Rev 52.1. However, this feature is not applicable to HANA One Rev 38 (1 year license expires in early October 2013). The only option to migrate HANA contents from HANA One Rev 38 to HANA One Rev 52.1 is using HANA export and import utility. Even though the focus here is HANA One migration, the same procedure can be followed, if anyone wants to migrate HANA contents to HANA Dev Edition to HANA One.
In HANA One at AWS (an example of a public cloud), a database copy is possible as it uses file-based backups only. To simplify the migration in the cloud, only the data backup files are considered here. This restores the content exactly as of the point in time at which the data backup was created.
However, few prerequisites must be met:
- A database backup of the source system is available.
- The version of the target system is the same or higher than the source system. Except HANA One Rev 38, all HANA One versions met this criterion.
- The target system has sufficient disk space and memory. Once a new HANA One Rev 52.1 instance is launched, it meets this criterion.
- The target system configuration is usable for the recovery of the source system. The type and number of services (for example, indexserver) must be identical in both systems. HANA One is not expected to change any internal configuration and hence, it meets this criterion too.
- A license key file is available for the target database. The license key of the source system will not work in the target system. HANA One Rev 52.1 includes HANA One License Version 1.0 since September 23, 2013.
- Stop the source HANA instance.
- Take data backup. You can use HANA Studio to take data backup or use HANA One management console (Rev 52 and onward).
- Launch a new HANA One Rev 52.1 instance as your new target system (Start an Instance on AWS).
- Transfer backup files from your source system to your target system.
- Use HANA Studio (Rev 52) to recover the data only.
- Use Addon feature in HANA One Rev 52.1 to install HANA Rev 52.1 License Key 1.0, Once recovery is successful,.
- Verify the license at your Rev 52.1 instance and content.
Example – Migrate HANA One Rev 48 to HANA One Rev 52.1
Step -1: Check Studio and Server version of the source system as shown here. Stop Source HANA System Using HANA Studio Rev 48.
Step 2: Take Rev 48 backup using HANA Studio Backup Wizard as shown below
Choose the location of backup files
After clicking Next and then click Finish; backup starts and completes as shown:
Step 3: Launch a new HANA One Rev 52.1 instance as your new target system
Step 4: Transfer backup files from the source system to the transfer system
Transfer backup data files /backup/HDB/REV48_* from the source system to the target system as shown below using the target instance *.pem file placed at /root/Demo.pem of the source system. Here, the same key-pairs is used in the source and target system.
Then using scp, files from the source system are copied to the target system’s /backup/HDB/data
After files are transferred 100% successfully, change the ownership of the files at the target system to <sid>adm (hdbadm here).
File transfer is complete and necessary permission to the <sid>adm user is added to the target system. Now these files are ready for recovery at the target system.
Step 5: Use HANA Studio (Rev 52) to recover the data only (no logs) Rev 52 Studio
Agree to shutdown the system and then select only a specific data backup option.
Specify the backup files as shown below
Check all the parameter and click on Finish button to start recovery. Ignore new license key install.
Wait till recovery is complete and after successful recovery, you will see the following message.
After recovery, license became invalid as shown in the Studio.
Step 6: Install License Key using Addon Manager
In the Addons tab, find HANA License 1.0 package and click on Download & Install button.
Enter SYSTEM DB password and hit on Submit button.
After license key is installed, under installed tab, you will see the package installed successfully.
Step 7: Verify license key and HANA content
You can verify the license key both at HANA One Management Console Admin page and at HANA Studio.
License key confirmation at HANA Studio
License key information at HANA One management Console Admin tab
Congratulations! You have successfully migrated to HANA One Rev 52.1. You can further upgrade your instance from HANA Rev 52 to the latest SP (HANA Rev 66 at the time of this blog). Even though the blog is created to migrate HANA contents from older releases to the latest HANA One release, similar steps (with minor changes in the file locations) can be followed when a wiling HANA Dev Edition customer is ready to move to HANA One as long as the source version of HANA is greater than Rev 45.
VN:F [1.9.22_1171]SAP HANA One Migration via Data Backup and Recovery,