AWS sap documentation change
Summary
Complete restructuring of storage configuration guide for SAP HANA. Changes include: consolidated instructions for Nitro/non-Nitro systems, added volume identification steps with lsblk examples, emphasized label-based mounting in /etc/fstab, removed redundant LVM examples, and added structured planning tables.
Security assessment
The changes focus on operational reliability and clarity rather than addressing security vulnerabilities. The emphasis on label-based mounting prevents potential mount failures during instance restarts (a stability improvement), but there's no evidence of patching vulnerabilities or addressing security incidents.
Diff
diff --git a/sap/latest/sap-hana/configure-storage-for-sap-hana.md b/sap/latest/sap-hana/configure-storage-for-sap-hana.md index 855de3328..9e2741452 100644 --- a//sap/latest/sap-hana/configure-storage-for-sap-hana.md +++ b//sap/latest/sap-hana/configure-storage-for-sap-hana.md @@ -5 +5 @@ -# Configure Amazon EBS storage for SAP HANA +OverviewIdentify VolumesCreate FilesystemsCreate Mount PointsMount and Verify @@ -7 +7 @@ -This topic explains how to configure scale-up and scale-out workloads with Amazon EBS. +# Configure SAP HANA Filesystems @@ -9 +9 @@ This topic explains how to configure scale-up and scale-out workloads with Amazo -In SAP HANA benchmark testing, the best performance is achieved using a 256 KB stripe size for data volumes and a 64 KB stripe size for log volumes. +## Overview @@ -11 +11 @@ In SAP HANA benchmark testing, the best performance is achieved using a 256 KB s - 1. Amazon EBS volumes should have been created and attached when you launched the Amazon EC2 instance. Confirm that all the required volumes are attached to the instance by running the `lsblk` command, which returns a list of the storage devices that are attached to the instance. +This guide explains how to configure Amazon EBS storage for SAP HANA on Amazon EC2. It covers volume identification, filesystem creation, and LVM configuration where required. @@ -15,34 +15 @@ In SAP HANA benchmark testing, the best performance is achieved using a 256 KB s -On [Nitro-based instances](https://docs.aws.amazon.com-AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances), Amazon EBS volumes are presented as [NVME block devices](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html). You need to perform additional mapping when configuring these volumes. - -Depending on the instance and storage volume types, your block device mapping will look similar to the following examples. - -**Example from a non-Nitro instance** - - lsblk - NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - xvda 202:0 0 50G 0 disk - ├─xvda1 202:1 0 1M 0 part - └─xvda2 202:2 0 50G 0 part / - xvdb 202:16 0 800G 0 disk - xvdc 202:32 0 800G 0 disk - xvdd 202:48 0 800G 0 disk - xvde 202:64 0 1T 0 disk - xvdf 202:80 0 4T 0 disk - xvdh 202:112 0 525G 0 disk - xvdr 202:4352 0 50G 0 disk - -**Example from a Nitro instance** - - lsblk - NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT - nvme0n1 259:0 0 50G 0 disk - └─nvme0n1p1 259:1 0 50G 0 part / - nvme1n1 259:2 0 4T 0 disk - nvme2n1 259:3 0 800G 0 disk - nvme3n1 259:4 0 800G 0 disk - nvme4n1 259:5 0 800G 0 disk - nvme5n1 259:6 0 525G 0 disk - nvme6n1 259:7 0 1T 0 disk - nvme7n1 259:8 0 50G 0 disk - - 2. Initialize the volumes of SAP HANA data, log, and backup to use with Linux Logical Volume Manager (LVM). +This guide uses NVMe device names (e.g., /dev/nvme1n1) which are standard on Nitro-based instances. On non-Nitro instances, devices will use different naming (e.g., /dev/sdb). Adjust commands according to your device names. @@ -50 +17 @@ Depending on the instance and storage volume types, your block device mapping wi -###### Note +Before beginning configuration, verify that you have the following: @@ -52 +19 @@ Depending on the instance and storage volume types, your block device mapping wi -Ensure you are choosing the devices that are associated with the SAP HANA data, log, and backup volumes. The device names might be different in your environment. + * An EC2 instance with appropriate EBS volumes attached @@ -54 +21 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, -**Example from a non-Nitro instance** + * Root or administrative access to the instance @@ -56,6 +22,0 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, - pvcreate /dev/xvdb /dev/xvdc /dev/xvdd /dev/xvdf /dev/xvdh - Physical volume "/dev/xvdb" successfully created. - Physical volume "/dev/xvdc" successfully created. - Physical volume "/dev/xvdd" successfully created. - Physical volume "/dev/xvdf" successfully created. - Physical volume "/dev/xvdh" successfully created. @@ -63 +23,0 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, -**Example from a Nitro instance** @@ -65,6 +24,0 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, - pvcreate /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 /dev/nvme5n1 /dev/nvme1n1 - Physical volume "/dev/nvme2n1" successfully created. - Physical volume "/dev/nvme3n1" successfully created. - Physical volume "/dev/nvme4n1" successfully created. - Physical volume "/dev/nvme5n1" successfully created. - Physical volume "/dev/nvme1n1" successfully created. @@ -72 +26 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, - 3. Create volume groups for SAP HANA data, log, and backup. Ensure that device IDs are associated correctly with the appropriate volume group. +## Identify Volumes @@ -74 +28 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, -**Example from a non-Nitro instance** +Identify block devices, their sizes, and associated volume IDs in order to assign them to the appropriate filesystems. @@ -76,6 +30 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, - vgcreate vghanadata /dev/xvdb /dev/xvdc /dev/xvdd - Volume group "vghanadata" successfully created - vgcreate vghanalog /dev/xvdh - Volume group "vghanalog" successfully created - vgcreate vghanaback /dev/xvdf - Volume group "vghanaback" successfully created + 1. **Run lsblk to view the associations** @@ -83 +32 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, -**Example from a Nitro instance** +As root, on the host, run the following: @@ -85,6 +34 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, - vgcreate vghanadata /dev/nvme2n1 /dev/nvme3n1 /dev/nvme4n1 - Volume group "vghanadata" successfully created - vgcreate vghanalog /dev/nvme5n1 - Volume group "vghanalog" successfully created - vgcreate vghanaback /dev/nvme1n1 - Volume group "vghanaback" successfully created + # lsblk -o NAME,SIZE,TYPE,FSTYPE,LABEL,PATH,SERIAL | sed 's/vol0/vol-0/g' @@ -92 +36 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, - 4. Create a logical volume for SAP HANA data. +_Example_ @@ -94 +38,9 @@ Ensure you are choosing the devices that are associated with the SAP HANA data, -In the following command, `-i 3` represents stripes based on the number of volumes that are used for a HANA data volume group. Adjust the number depending on the number of volumes that are allocated to the HANA data volume group, based on instance and storage type. + NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE LABEL PATH SERIAL + nvme1n1 259:0 0 2.2T 0 disk /dev/nvme1n1 vol-0abc123def456789a + nvme0n1 259:1 0 50G 0 disk /dev/nvme0n1 vol-0xyz987uvw654321b + ├─nvme0n1p1 259:5 0 2M 0 part /dev/nvme0n1p1 + ├─nvme0n1p2 259:6 0 20M 0 part /boot/efi vfat EFI /dev/nvme0n1p2 + └─nvme0n1p3 259:7 0 50G 0 part / xfs ROOT /dev/nvme0n1p3 + nvme4n1 259:2 0 1T 0 disk /dev/nvme4n1 vol-0pqr456mno789123c + nvme2n1 259:3 0 2.2T 0 disk /dev/nvme2n1 vol-0jkl789ghi123456d + nvme3n1 259:4 0 500G 0 disk /dev/nvme3n1 vol-0def456abc789123e @@ -96,3 +48 @@ In the following command, `-i 3` represents stripes based on the number of volum - lvcreate -n lvhanadata -i 3 -I 256 -L 2350G vghanadata - Rounding size 2.29 TiB (601600 extents) up to stripe boundary size 2.29 TiB (601602 extents). - Logical volume "lvhanadata" created. + 2. **Record the Volume Associations** @@ -100 +50 @@ In the following command, `-i 3` represents stripes based on the number of volum - 5. Create a logical volume for SAP HANA log. +Document the volume requirements and assignments in a structured format. This table will help ensure the correct commands for setting up the volumes. @@ -102 +52,6 @@ In the following command, `-i 3` represents stripes based on the number of volum -In the following command, `-i 1` represents stripes based on the number of volumes that are used for a HANA log volume group. Adjust the number depending on the number of volumes that are allocated to the HANA log volume group, based on instance and storage type. +Purpose | Volume Size | Volume Count | Striping Required | Devices(s) | Volume(s) +---|---|---|---|---|--- +HANA Data | | | | | +HANA Log | | | | | +HANA Shared | | | | | +Other | | | | | @@ -104,3 +59 @@ In the following command, `-i 1` represents stripes based on the number of volum - lvcreate -n lvhanalog -i 1 -I 64 -L 512G vghanalog - Ignoring stripesize argument with single stripe. - Logical volume "lvhanalog" created. + 3. **Review or Assign Tags (optional)** @@ -108 +61 @@ In the following command, `-i 1` represents stripes based on the number of volum - 6. Create a logical volume for SAP HANA backup. +Tags help identify volumes in the AWS console and API commands, particularly useful during maintenance, volume extensions, or backup/restore operations. Review existing, or add new tags using the following command or the AWS Console. @@ -110,3 +63 @@ In the following command, `-i 1` represents stripes based on the number of volum - lvcreate -n lvhanaback -i 1 -I 256 -L 4095G vghanaback - Ignoring stripesize argument with single stripe. - Logical volume "lvhanaback" created. +_Example_ @@ -114 +65 @@ In the following command, `-i 1` represents stripes based on the number of volum - 7. Construct XFS file systems with the newly created logical volumes for HANA data, log, and backup by using the following commands: + $ aws ec2 create-tags --resources vol-0abc123def456789a --tags Key=Name,Value="PRD - Hana Data Volume 1 of 2" @@ -116,3 +67 @@ In the following command, `-i 1` represents stripes based on the number of volum - mkfs.xfs -f /dev/mapper/vghanadata-lvhanadata - mkfs.xfs -f /dev/mapper/vghanalog-lvhanalog - mkfs.xfs -f /dev/mapper/vghanaback-lvhanaback +Repeat for all volumes. @@ -120 +68,0 @@ In the following command, `-i 1` represents stripes based on the number of volum - 8. Construct XFS file systems for HANA shared and HANA binaries. @@ -122,2 +69,0 @@ In the following command, `-i 1` represents stripes based on the number of volum - mkfs.xfs -f /dev/xvde -L HANA_SHARE - mkfs.xfs -f /dev/xvdr -L USR_SAP @@ -125 +70,0 @@ In the following command, `-i 1` represents stripes based on the number of volum -###### Note @@ -127 +72,70 @@ In the following command, `-i 1` represents stripes based on the number of volum -On Nitro-based instance types, device names can change during instance restarts. To prevent file system mount issues, it is important to create labels for devices that aren’t part of logical volumes so that the devices can be mounted by using labels instead of the actual device names. +## Create Filesystems + +Create Filesystems according to whether or not striping has been identifed as a requirement + + 1. **Configure Single Volumes** + +When performance requirements can be met using a single volume (including capacity for growth), create XFS filesystems directly on the device. + +_Example_ + + # Create XFS filesystem with label for HANA Shared + mkfs.xfs -f /dev/nvme4n1 -L HANA_SHARED + + # Create XFS filesystem with label for HANA Log + mkfs.xfs -f /dev/nvme3n1 -L HANA_LOG + +###### Tip + +Labels provide consistent device identification across instance restarts. You can add or change a label on an existing XFS filesystem using `xfs_admin -L LABEL_NAME /dev/device_name`. Always use labels in /etc/fstab by referencing `/dev/disk/by-label/LABEL_NAME`. + + 2. **Configure Striped Volumes** + +Logical Volume Management (LVM) manages storage in three layers: Physical Volumes (created with pvcreate) are the actual disks, Volume Groups (created with vgcreate) combine these disks into storage pools, and Logical Volumes (created with lvcreate) are virtual partitions that can span multiple disks for features like striping. + +_Example_ + + # Create physical volumes + pvcreate /dev/nvme1n1 /dev/nvme2n1 + + # Create volume group + vgcreate vg_hana_data /dev/nvme1n1 /dev/nvme2n1 + + # Create striped logical volume + lvcreate -i 2 -I 256 -l 100%VG -n lv_hana_data vg_hana_data + + # Create XFS filesystem with label for HANA data + mkfs.xfs -L HANA_DATA /dev/vg_hana_data/lv_hana_data +