Understanding Your SAP HANA One Deployment

Now that you deployed your SAP HANA One instance, attached an elastic IP Address, adjusted your security groups, and connected your SAP HANA Studio installation lets take a closer look at the solution as well as some basic operations. Network Topology If you deployed your SAP HANA One instance using the 1-Click deployment option, your instance is deployed into AWS Cloud and secured via a security group.

Figure 1 - HANA One Deployment in EC2 Classic network topology

The network topology for an AWS VPC deployment is also included for reference but is beyond the scope of this quick start guide.

Figure 2 - VPC Deployment with Access via Internet Gateway

Figure 3 - VPC Deployment with Access via Corporate Network

AWS Instance Type SAP HANA One instances are currently based on the AWS cc2.8xlarge instance type. This instance type has the following characteristics: 60.5 GB of memory 88 EC2 Compute Units (2 x Intel Xeon E5-2670, eight-core "Sandy Bridge" architecture) 64-bit platform I/O Performance: Very High (10 Gigabit Ethernet)

Storage Configuration & Volume Layout The SAP HANA One storage configuration as delivered uses a combination of standard Elastic Block Store (EBS) Volumes and Provisioned IOPS volumes. As depicted by the diagram below, the AWS instance is EBS backed. For the SAP HANA One installation, EBS P-IOPS volumes are used for the log device to ensure consistent performance. The data and backup volumes leverage EBS standard volumes. However, for Rev 48, EBS P-IOPS, volumes are optional.

Figure 4 - global.ini configuration

Mdadm arrays are used for the SAP HANA One Log and Data volumes, as well as the backup volumes. This is done primarily for performance reasons. For configuration details please see the file /etc/mdadm.conf on your system. Figure 5 - EBS Volume configuration

Backup and Recovery Simple Backup and restore functions can be managed entirely from the SAP HANA Studio. Simply select your SAP HANA One instance within the studio and right-click for the context menu. Select Backup and follow the onscreen instructions. Note the location of the backup as specified, and then complete the backup. Please make sure database user has necessary roles for backup operation as described in SAP HANA Backup and Recovery Guide.

Once you have created a backup onto an EBS volume, you need to copy the backup data to Amazon S3 to protect the data against EBS volume failure. Copying Files direct to Amazon S3 To copy to or retrieve data from Amazon S3 you can use various command line interfaces exist that you can incorporate into a script. S3cmd is an open source project available under GNU Public License v2 (GPLv2) and is free for both commercial and private use Creating a Snapshot of a backup EBS Volume Instead of copying and retrieving single files to Amazon S3, you can also create a snapshot of the complete EBS Volume. The snapshot is automatically stored in Amazon S3 and can subsequently be used to create new EBS Volumes that contain the same data as stored in the snapshot. The Backup and Recovery of SAP systems on Amazon Web Services guide provides an overview of how to backup SAP systems running on Amazon Web Services. This guide focuses on the essential differences in backing up SAP systems on AWS as compared to traditional infrastructure.

Upgrading to SAP HANA One Revision 48 When upgrading to Revision 48, you can have two scenarios: 1. Upgrade an existing revision to a new release. For example, how does a Rev 38 customer upgrade a Rev 38 SAP HANA One system to a newer release, like Rev 48? 2. Migrate an existing system to a new release. For example, how can content of an existing Rev 38 SAP HANA One system be migrated to a new Rev 48 SAP HANA One system? For release SAP HANA One Rev 48, scenario 1 is not directly supported. However, in scenario 2, any existing SAP HANA One customer can migrate content from a lower Revision (for example, Rev 38) to a higher Revision (for example, Rev 48) and can achieve the feature requirement in 1. This method applies to upgrading only from SAP HANA One 38. However, migrating between any releases not available in HANA One is not supported in HANA One (for example, Rev 38 to Rev 46). To perform these steps, you should be familiar with SAP HANA backup, recovery, import, export processes, and AWS EBS volume, snapshot management or S3 functionality. To migrate an existing SAP HANA One system to a new release: 1. Make a backup of all data from your existing SAP HANA One system and keep it safe. 2. Use Export Utility in SAP HANA to export content from an existing SAP HANA One system. 3. Use Import utility in SAP HANA to import content from an existing to a new SAP HANA One system. Details 1. Always create and keep a backup of your data from an existing system. Data backup can be performed with HANA Studio with backup wizard and only choosing Data option. Once you successfully performed data back, please make sure you keep your data backup files safe and secured. There are several ways, the data backup files can be saved securely including: a. Create a tar file from the backup directory in Linux level. For SAP HANA One, it is /backup/HDB/data. b. Using tools like winscp to download the tar file to your desktop or local server. Data stays locally under your control. Attach a new EBS volume to your HANA One instance and then mount the new volume. Backup data to this newly mounted volume (note down volume ID for future reference). After you complete the data backup the file, you can detach the new volume. You can keep this volume and attach directly to the same HANA One instance or attach to a newer HANA One instance. You also can create a snapshot from this volume. In either way (either as a volume or a snapshot), you can securely keep backup data within your AWS account. You also can save back up data into AWS S3.

2. If your backup data file in a safe location, export data from your existing HANA One system. For the exact SQL syntax for export/import, see http://help.sap.com/hana/html/_gdata_import_export_statements.html. 3. Launch the new SAP HANA One system from AWS Marketplace or start an existing and already subscribed system to which you want to migrate your existing data. 4. Following steps 1a and 1b, transfer exported files from your original or source system to new or target system. 5. Following SQL syntax in step 2, import your content as described in step 4. Following these guidelines, you can save data as backup files and then use import/export utility of SAP HANA to migrate data from an older version of SAP HANA One instance to a newer instance of SAP HANA One instance.