vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* --total-volume-bandwidth: The amount of bandwidth (in megabits per second) that is allocated exclusively to instance storage volumes. An increase in this value results in a corresponding decrease to total network bandwidth.
* --boot-volume: BOOT_VOLUME_JSON|@BOOT_VOLUME_JSON_FILE, boot volume attachment in JSON or JSON file. For the data schema, see the boot_volume_attachment property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --volume-attach: VOLUME_ATTACH_JSON|@VOLUME_ATTACH_JSON_FILE, volume attachment in JSON or JSON file, list of volumes. For the data schema, see the volume_attachments property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --keys: Comma-separated IDs or names of SSH keys.
* --dedicated-host: ID or name of the host destination where the instance is placed.
* --dedicated-host-group: ID or name of the host group destination where the instance is placed.
* --placement-group: ID or name of the placement group. The placement group restrictions for the virtual server instance.
* --user-data: data|@data-file. User data to transfer to the virtual server instance.
* --sgs: Comma-separated security group IDs or names for primary network interface.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
Creating a stand-alone data volume from a snapshot with Terraform 

To create a volume from a snapshot, use the ibm_is_volume resource. The following example creates a volume from the snapshot bdcdc984-ba4e-4aef-84fb-e8448c3116b1 with the general-purpose performance profile.

resource "ibm_is_volume" "storage" {
name = "restore-data-vol1"
profile = "general-purpose"
zone = "us-south-1"
source_snapshot = "ibm_is_snapshot.example.id"
}

For more information about the arguments and attributes, see [ibm_is_volume](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_volume).







 Next steps 

You can create more snapshots.

[Create](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create) more snapshots or [manage](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage) existing snapshots.
The details of the boot volume that is to be created are displayed on the page. You can edit the boot volume by clicking the pencil icon to change the size, encryption, and add any user tags to identify this resource.
4. To create a data volume and attach it to the instance, in the Data volumes section of the instance provisioning page, click Create. In the side panel, specify the volume details. Table 1 shows the values that need to be defined.



Table 1. Block Storage for VPC volume values to be specified during instance provisioning.

 Field Value 

 Name Specify a unique, meaningful name for your volume. For example, it can be a name that describes your compute or workload function. The volume name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. You can later edit the name if you want. Volume names must be unique the entire VPC infrastructure. 
 Resource group The resource group is inherited from the instance. 
 Location Location inherited from the instance (for example, Dallas 2) 
 Tags Specify user tags to associate with this volume. For more information about organizing resources with user tags, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag&interface=ui). 
 Auto Delete Enable this feature to automatically delete this volume when the attached virtual server instance is deleted. You can change this setting later on the virtual server details page. 
 Size Enter a volume size in GBs. Volume sizes can be 10 - 16,000 GB. 
 Profile Select [Tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) and select the IOPS tier list. If your performance requirements don't fall within a predefined IOPS tier, select [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) and select an IOPS value within the range for that volume size. 
 Encryption Provider-managed encryption with IBM-managed keys is enabled by default on all volumes.
Snapshot Optionally, click Select snapshot to create the volume with data from the selected snapshot. You can create data volumes with Nonbootable snapshots, and boot volumes with Bootable snapshots. For more information, see [Create a stand-alone Block Storage for VPC volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=clicreate-vol-from-snapshot-ui). 
 Profile IOPS tiers are shown by default. Click the tab for Custom IOPS. 
 For [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers), select the tile with the performance level that you require and specify the volume size in GBs. Volume sizes can be 10 - 16,000 GB. 
 For [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) IOPS, specify the size of your volume and IOPS range based on the size of the volume. As you type the IOPS value, the UI shows the acceptable range. You can also click the storage size link to see a table of size and IOPS ranges. For more information, see [Custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom). 
 Encryption Encryption with IBM-managed keys is enabled by default on all volumes. You can also choose Customer Managed and use [your own encryption key](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryption). 



4. When you're finished, click Create volume. You're returned to the Block Storage for VPC volumes page, where a message indicates that the volume is being created (volume status is pending). A second message displays when the volume is created (volume status is available).
5. To see details of the new volume, select the View resource link in the second message to go to the Volume details page.
Snapshot Optionally, click Select snapshot to create the volume with data from the selected snapshot. You can create data volumes with Nonbootable snapshots, and boot volumes with Bootable snapshots. For more information, see [Create a stand-alone Block Storage for VPC volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=uicreate-vol-from-snapshot-ui). 
 Profile IOPS tiers are shown by default. Click the tab for Custom IOPS. 
 For [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers), select the tile with the performance level that you require and specify the volume size in GBs. Volume sizes can be 10 - 16,000 GB. 
 For [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) IOPS, specify the size of your volume and IOPS range based on the size of the volume. As you type the IOPS value, the UI shows the acceptable range. You can also click the storage size link to see a table of size and IOPS ranges. For more information, see [Custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom). 
 Encryption Encryption with IBM-managed keys is enabled by default on all volumes. You can also choose Customer Managed and use [your own encryption key](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryption). 



4. When you're finished, click Create volume. You're returned to the Block Storage for VPC volumes page, where a message indicates that the volume is being created (volume status is pending). A second message displays when the volume is created (volume status is available).
5. To see details of the new volume, select the View resource link in the second message to go to the Volume details page.
User data You can add user data to automatically complete common configuration tasks or run scripts. For more information, see [User data](https://cloud.ibm.com/docs/vpc?topic=vpc-user-data). 
 Boot volume The default boot volume size for all profiles is 100 GB. You can edit the boot volume by clicking the pencil icon. 
 Data volume You can add one or more secondary data volumes when you provision the instance. To add volumes, click New volume. For more information about provisioning the volume, see [Create and attach a block storage volume when you create a new instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi). Attach data volumes to your virtual server depending on your SAP HANA or SAP NetWeaver virtual server profile. 
 Network interfaces Assign networking options to connect into the IBM Cloud VPC. You can create and assign up to five network interfaces to each instance - see below. 







 Adding Network Block Storage for VPC 



1. Log in to the [IBM Cloud console](https://cloud.ibm.com) with your unique credentials.
2. Click Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Block storage volumes > New Volume.
3. Enter a unique Name.
4. Choose a Resource group.

The resource group can't be changed after you create the virtual server.
5. Select the same Location in which you created your Virtual Servers for VPC. The location consists of a region and zone.
6. Select either IOPS tiers or Custom. As described in [Storage design considerations](https://cloud.ibm.com/docs/sap?topic=sap-storage-design-considerations), the IOPS per GB depends on the workload anticipated.
7. Click Create volume.

By default all block storage for VPC volumes use IBM-managed encryption.
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/vde: 536.9 GB, 536870912000 bytes, 1048576000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/vdf: 536.9 GB, 536870912000 bytes, 1048576000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Show more

These three disks must be managed under the Linux® Logical Volume Manager (LVM), and deployed as logical volumes. In order to achieve that, first put the three devices under LVM control. For example, make them physical volumes:

[root@hana256-vsi ] pvcreate /dev/vdd /dev/vde /dev/vdf

Then, create a volume group from the physical volumes. The name of the volume group can be chosen according to your preferences, in our sample it is hana_vg:

[root@hana256-vsi ] vgcreate hana_vg /dev/vdd /dev/vde /dev/vdf

After creating the volume group, three logical volumes need to be defined on top. These logical volumes reflect the file system size requirements for SAP HANA. The following commands are for a 256 GB virtual server:

[root@hana256-vsi ] lvcreate -i 3 -I 64K -L 256GB -n hana_log_lv hana_vg
[root@hana256-vsi ] lvcreate -i 3 -I 64K -L 256GB -n hana_shared_lv hana_vg
region = "eu-de"
}
3. Import the list of available volume profiles as a read-only data source.

data "ibm_is_volume_profiles" "example" {
}

For more information, see [ibm_is_volume_profile](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_volume_profiles).









 Next Steps 

To expand volume capacity, see [expanding block storage volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes).

To [change the IOPS tier or Custom IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops) for an existing volume that is attached to a virtual server instance.

For more information about Balanced, Compute, and Memory profiles for Virtual Servers for VPC, see [Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles).
For each profile, consider the specific volume sizes in table 7 and always make sure that the correct disks are given for the respective commands. The Linux command fdisk -l shows which disk has been mapped to the volume, for example /dev/vde.



 ux2d-8x224 and ux2d-16x448 



1. Create the volume group for LVM.

[root@ux2d-8x224 ] pvcreate /dev/vde
[root@ux2d-8x224 ] vgcreate hana_vg /dev/vde
2. After the volume group is created, three logical volumes are defined on top. These logical volumes reflect the file system size requirements for SAP HANA.

[root@ux2d-8x224 ] lvcreate -L 224G -n hana_shared_lv hana_vg
 or lvcreate -L 448G -n hana_shared_lv hana_vg

[root@ux2d-8x224 ] lvcreate -L 224G -n hana_log_lv hana_vg
 or lvcreate -L 448G -n hana_log_lv hana_vg

[root@ux2d-8x224 ] lvcreate -l 100%VG -n hana_data_lv hana_vg
3. Now proceed with the same instructions that are listed in steps 3 and 4 [profile vx2d-16x224](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-intel-vs-vpcvx2d-16x224).







 ux2d-36x1008 and ux2d-48x1344 



1. Create the volume groups for LVM. /hana/log and /hana/data are assigned to the LVM.

[root@ux2d-36x1008 ] pvcreate /dev/vde /dev/vdf
In this example all of the block storage devices are virtio_blk devices:



* vda is the boot volume.
* vdb and vdc are the 600 GB instance storage disks. Since the lsblk command is displaying “G” units as base-2 gibibytes, the size is displayed as 558.8 GiBs.
* vdd and vde are remote data volumes that are attached to the instance. Since these data volumes are requested in the same units as lsblk is displaying, their size remains as whole GiBs (50).
* Notice that the physical sector size and logical sector size are much larger for the instance storage disks. To identify the disk name for all instance storage, you can run the following command. In this example, the command returns /dev/vdb and /dev/vdc.



lsblk -p -o NAME,TYPE,PHY-SEC,LOG-SEC,MOUNTPOINT | grep disk | grep 4096 | awk 'NR>0{print $1}'



* vdf and vdg are small block volumes that are used for the cloud-init configuration of the instance.







 Partitioning, formatting, and mounting instance storage disks 

The instance storage disks can be partitioned, formatted with a file system, and mounted into the hierarchical file system in the same manner as the remote block volumes.



* For instructions for Linux®, see [Set up your Block Storage for VPC data volume for use (Linux)](https://cloud.ibm.com/docs/vpc?topic=vpc-start-using-your-block-storage-data-volume-lin) or [Configuring a single disk instance storage by using the cloud-config script](https://cloud.ibm.com/docs/vpc?topic=vpc-user-dataconfigure-instance-storage-cloud-config).
* For Windows®, use the Computer Management UI to bring a block volume online, partition, and format it.
* --type: Type of the volume (ssd, standard, tier1, or tier3).
* --size: Size of the volume (GB).
* --shareable: Whether volume can be attached to multiple VMs.
* --json: Format output in JSON.



--------------------







 ibmcloud pi volume-delete 



 Delete a volume 

ibmcloud pi volume-delete VOLUME_ID



* VOLUME_ID: The unique identifier or name of the volume



--------------------







 ibmcloud pi volume-detach 



 Detach a volume from an instance 

ibmcloud pi volume VOLUME_ID --instance INSTANCE [--json]



* VOLUME_ID: The unique identifier or name of the volume.



Options



* --instance: Instance to detach the volume from.
* --json: Format output in JSON.



--------------------







 ibmcloud pi volume-flash-copy-mapping 



 Get a list of flash copy mappings of a volume directly from primary storage host 

ibmcloud pi volume-flash-copy-mapping VOLUME_ID [--json]



* VOLUME_ID: The unique identifier or name of the volume.



Options



* --json: Format output in JSON.



--------------------







 ibmcloud pi volume-group 



 View details of a volume group 

ibmcloud pi volume-group VOLUME_GROUP_ID [--long] [--json]



* VOLUME_GROUP_ID: The unique identifier or name of the volume group.



Options



* --long: Retrieve additional details for the volume group.
* --json: Format output in JSON.



--------------------







 ibmcloud pi volume-group-create
: Filter by type of storage volume, options are: performance,endurance.

-o, --order
: Filter by ID of the order that purchased the block storage.

--sortby
: Column to sort by, default:id, options are: id,username,datacenter,storage_type,capacity_gb,bytes_used,ip_addr,lunId,active_transactions,created_by.

--column
: Column to display. Options are: id,username,datacenter,storage_type,capacity_gb,bytes_used,ip_addr,lunId,created_by,active_transactions,notes. This option can be specified multiple times.

Examples:

ibmcloud sl block volume-list -d dal09 -t endurance --sortby capacity_gb

This command lists all endurance volumes on current account that are located at dal09, and sorts them by capacity.





 ibmcloud sl block volume-modify 

Modify an existing block storage volume:

ibmcloud sl block volume-modify VOLUME_ID [OPTIONS]

Command options:

-c, --new-size
: New Size of block volume in GB. If no size is given, the original size of volume is used. Potential Sizes: [20, 40, 80, 100, 250, 500, 1000, 2000, 4000, 8000, 12000] Minimum: [the original size of the volume]

-i, --new-iops
: Performance Storage IOPS. Range between [100 and 6000], and in multiples of 100 [only for performance volumes] If no IOPS value is specified, the original IOPS value of the volume is used. Requirements: [If original IOPS/GB for the volume is less than 0.3, new IOPS/GB must also be less than 0.3. If original IOPS/GB for the volume is greater than or equal to 0.3, new IOPS/GB for the volume must also be greater than or equal to 0.3.]

-t, --new-tier
Data read from the volume (MiB/s).



Table 10: Volume I/O throughput read metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_io_throughput_read_mib 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation, 1, resource name, disk name of the volume, UUID of storage volume 







 Volume I/O throughput total 

All volume I/O, in MiB/s.



Table 11: Volume I/O throughput total metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_io_throughput_total_mib 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation, 1, resource name, disk name of the volume, UUID of storage volume 







 Volume I/O throughput written 

Data that is written to the volume (MiB/s)



Table 12: Volume I/O throughput written metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_io_throughput_write_mib 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation, 1, resource name, disk name of the volume, UUID of storage volume 







 Volume I/O wait time 

Total I/O wait time (all requests) per second



Table 13: Volume I/O wait time metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_io_wait 
 Metric type gauge 
 Value type none 
 Segment by IBM IS Generation, 1, resource name, disk name of the volume, UUID of storage volume 







 Volume read requests bytes per second 

Read requests in bytes per second.



Table 14: Volume read requests bytes per second metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_read_bps 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation, 1, resource name, disk name of the volume, UUID of storage volume 







 Volume read requests I/O operations per second 

Volume read requests per second.



Table 15: Volume read I/O operations per second metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_read_iops 
 Metric type gauge
Specify a name for your volume, volume profile, and the zone where you are creating the volume. To attach a block storage data volume to an instance, the instance and the block storage data volume must be created in the same zone.

ibmcloud is volume-create my-volume custom us-south-2 --iops 1000

From the output that's returned, save the ID of the volume in a variable so you can use it later:

vol=0738-933c8781-f7f5-4a8f-8a2d-3bfc711788ee

The status of the volume is pending when it first is created. Before you can proceed, the volume needs to move to available status, which takes a few minutes.

To check the status of the volume, run this command:

ibmcloud is volume $vol





 Attach a block storage data volume to an instance 

Use the following command to attach the volume to the virtual server instance, by using the variables that we created:

ibmcloud is instance-volume-attachment-add my-volume-attachment $instance $vol --auto-delete true





 Add rules to the default security group 

You can configure the security group to define the inbound and outbound traffic that is allowed for the instance. For example, you can add a rule to allow SSH traffic.

Find the security group for the VPC:

ibmcloud is vpc-sg $vpc

From the output that's returned, save the ID in a variable so you can use it later:

sg=0738-2d364f0a-a870-42c3-a554-000000981149

Now create a rule to allow SSH traffic:

ibmcloud is sg-rulec $sg inbound tcp --port-min=22 --port-max=22

Optionally, you can also add a rule to allow ping traffic:

ibmcloud is sg-rulec $sg inbound icmp --icmp-type 8 --icmp-code 0
lvhome<SID> /db2/db2<SID> 
 lv<SID>db2dump /db2/<SID>/db2dump 
 lv<SID>logdir /db2/<SID>/log_dir 
 lv<SID>log_archive /db2/<SID>/log_archive 
 lv<SID>saptmp /db2/<SID>/saptemp1 
 lv<SID>db2sw /db2/db2/<DBSID>/db2_sw 
 Db2 database storage II <sid>db2datvg lv<SID>sapdata1 /db2/<SID>/sapdata1 
 ``lv sapdata2` /db2/<SID>/sapdata2 
 ``lv sapdata3` /db2/<SID>/sapdata3 
 ``lv sapdata4` /db2/<SID>/sapdata4 



For more information, see [Required File Systems for IBM Db2 for Linux, UNIX, and Windows](https://help.sap.com/viewer/4fbd902c7c76410bb82c6311dd4dc94b/CURRENT_VERSION/en-US/713eb64f45c6448c8dbe8a51b85680ee.html) and [SAP Note 1707361](https://launchpad.support.sap.com//notes/1707361).





 Sample storage configuration for SAP HANA that use the IBM Power Virtual Server 

The following table shows an example of a storage layout for an SAP HANA system.

SAP HANA Data and SAP HANA Log directory file systems must be striped over 4 or 8 storage volumes.

Striping for other file systems (SAP executable files, HANA Shared, HANA Backup, HANA Export) is not required. See the SAP TDI documents for general storage requirements.



Table 6. Example of a storage layout for an SAP HANA system

 HANA file system Total Space Required Size of Volumes Number of Volumes 

 /hana/data 560 70 8 
 /hana/log 640 80 8
/dev/sdb2 /hana/data remaining capacity 









 BI.S4.H2.3000 Appliance 

Link to Profile: [BI.S4.H2.3000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1109&presetId=1103)



 Physical Disk and RAID Configuration 



 RAID Components Drives Array Total Capacity 

 RAID 1 2x 960 GB SSD SED hdd0, hdd1 RAID1-A 960 GB 
 RAID 10 4x 3.8 TB SSD SED hdd2, hdd3, hdd4, hdd5 RAID1-B 7.6 TB 
 Global hot spare 1x 3.8 TB SSD SED hdd6 







 Disk mount points and Partitions 



 Array Partition Name Size (GB) 

 RAID1-A /dev/sda 
 /dev/sda1 /boot 50 
 /dev/sda2 / 150 
 /dev/sda3 /usr/sap 150 
 /dev/sda4 /hana/log remaining capacity 
 RAID1-B /dev/sdb 
 /dev/sdb1 /hana/shared 1024 
 /dev/sdb2 /hana/data remaining capacity 









 BI.S4.H4.3000 Appliance 

Link to Profile: [BI.S4.H4.3000 Appliance](https://cloud.ibm.com/gen1/infrastructure/provision/bm?imageItemId=13467&packageId=1117&presetId=1117)



 Physical Disk and RAID Configuration 



 RAID Components Drives Array Total Capacity 

 RAID 1 2x 960 GB SSD SED hdd0, hdd1 RAID1-A 960 GB 
 RAID 10 4x 3.8 TB SSD SED hdd2, hdd3, hdd4, hdd5 RAID1-B 7.6 TB 
 Global hot spare 1x 3.8 TB SSD SED hdd6 







 Disk mount points and Partitions 



 Array Partition Name Size (GB) 

 RAID1-A /dev/sda 
 /dev/sda1 /boot 50