DEPLOYING SAP HANA DEVELOPMENT EDITION INTO MICROSOFT AZURE THROUGH SAP CAL
Customer needs to migrate SAP HANA DB from AWS to Azure.
– DB Size around 50GB
– Test-bed DB for their in-house applications
– Internal networks only will access the DB
– People logging in are from Denmark
– IT support is in the Philippines
– Presently the DB is on SQL Server 2008
This document explores how a VM with SAP HANA can be deployed directly into the Microsoft Azure cloud.
Thereafter the options for migrating are as follows
1. Manually exporting data tables from SQL into Excel files. Upload the data into HANA
2. Use DATA SERVICES WORKBENCH SAP tool to connect to SQL Server as the source and HANA DB as the destination. Thereafter perform the data export.
This post is dedicated to the deployment of SAP HANA only.
DEPLOYING SAP HANA VM ONTO AZURE:-
Login to SAP CAL (Cloud Appliance Library) account. You can create a free one for purposes of testing.
Click on Step 1 and thereafter proceed to create an account. It will eventually bring you to a place where all the cloud services reside.
Select the SAP service you need, in this case SAP HANA Developer Edition 1.0 SPS 09
For Azure China, select Windows Azure operated by 21VIanet
For Microsoft Azure (non-China), select Microsoft Azure (selected for this demonstration)
Verify the subscription ID in Azure to be entered into the SAP CAL setup
Add yourself as a user/owner
Click Finish, this will bring up another window prompting you to download the Management Certificate.
Accept and click Download
This management certificate needs to be uploaded into Microsoft Azure. Select Management Certificates under Settings.
Click Upload. Browse to the location of recently saved certificate file and then click ok.
Once uploaded, it should show a management certificate installed. Apart from the timestamp, there seems to be no other way to ensure it is indeed a SAP CAL certificate at this time. Be careful that it is the same certificate that you saved earlier.
Go back to the SAP CAL window, click on the SAP HANA Developer Edition
Presently, Azure A7 VM is automatically suggested for this particular version (there is another version of SAP HANA as well which is not available on trial)
Note: If the SAP HANA Developer Edition 1.0 SPS 09 is not shown as active, click on the ACTIVATE and it should show you the below activation
Click Create Instance
Click next to select additional information such as VM size.
Select either VM instance based on the need. VM sizes A7 and A8 have been recently added for SAP HANA. Click Next.
Enter the Master Password for the solution.
Choose the suspension and/or termination options. There is an option to manually activate and suspend as well, if you don’t want to choose automatic suspension or termination.
Verify the summary before final creation and click FINISH.
Click Store to store it within the SAP CAL
Once you click OK, the estimated time to create the system and solution on Azure is about 45 minutes.
In about 25-30 minutes, you should see two items created in the Azure Portal (Storage account and VM)
Wait until the VM is provisioned. Check whether the storage has been provisioned as well. Note that the “CONNECT” option has been greyed out for the Azure VM created.
Confirm that you are able to see the VM on your SAP CAL login as well, with the options to “CONNECT” or “SUSPEND”.
Click Connect to access the VM. Access is through the web browser
If the IP address connectivity does not work, connect to Windows Azure Portal and copy out the fully qualified DNS Name of the server. This will definitely work.
To find the FQDN of the server from Azure Portal
It should show up as if the server is configured properly, without any errors.
Upon scrolling down, more options are visible including information to access the server.
Click on xs-admin to login to the system
Enter user name and password and you should be now able to login into the system.
Click on Database Status for more information.
Click on Memory Overview for more information.
You can also manage roles and users from this console, along with alerting and application lifecycle. Along with this, you should now be able to work on this server now and perform your development activities as per normal.