vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Table 4. Storage configuration of the default bare metal server deployment (boot volume)

 File system Partition Storage type Size 

 sda1 Pre-configured BIOS volume 1 MB 
 /boot/efi sda2 Pre-configured boot volume 100 MB 
 / sda3 Pre-configured root volume 9.9 GB 





 Internal Storage 

Your bare metal server on VPC comes with a number of internal NVMEs, depending on its size. For SAP NetWeaver based deployment, you can use the NVMEs that are listed as block devices to the operating system. The NVMEs are under “/dev/nvmeXn1” (X from 0 to the number of NVMEs in total, minus 1). Use the NVMEs according to your requirements and needs. However, to increase failure resilience, you might have to install Linux Logical Volume Manager (LVM) to add RAID configuration, like RAID1 or RAID5. Since NVMEs are provisioned, performance considerations are mostly not an issue.





 External Storage 

If more storage needs are to be added to your Bare metal server on VPC, for example, for backup purposes, NFS-based file shares can be created and mounted. Learn more details in the corresponding chapter [Creating file shares and mount targets](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create).
[GPU](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=uigpu) GPU enabled profiles provide on-demand access to NVIDIA V100 and A100 GPUs to accelerate AI, high-performance computing, data science, and graphics workloads. 
 [Storage Optimized](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=uistorageopt) Storage Optimized profiles offer temporary SSD instance storagedisks at a ratio of 1 vCPU to 300 GB instance storage with a lower price point per GB. These profiles are designed for storage-dense workloads and offer virtio interface type for attached disks. 



Profiles with instance storage and profiles with 64 or more vCPUs are deployed exclusively on the Intel®'s second-generation quad processor Xeon® Platinum 8260 Cascade Lake with 96 cores that are running at a base speed of 2.4 GHz and an all-core turbo frequency of 3.1 GHz or Intel®'s quad processor Xeon® Gold 6248 Cascade Lake with 80 cores that are running at a base speed of 2.5 GHz and an all-core turbo frequency of 3.1 GHz.

Profiles with AMD manufactured processors are available in the Toronto region.



 Balanced 

Balanced profiles provide a mix of performance and scalability for more common workloads with a ratio of 4 GiB of memory for every 1 vCPU of compute. The Balanced profile family includes profiles with and without [instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage). The following table shows all Balanced profiles available for Intel® x86-64, and AMD x86-64 processors.

Balanced profiles with the bx2d prefix are available in the US South (Dallas), US East (Washington DC), Canada (Toronto), United Kingdom (London), EU Germany (Frankfurt), Japan (Tokyo), Japan (Osaka), and Australia (Sydney) regions.

Intel x86-64

AMD x86-64



Table 3. Balance profiles options for Intel x86-64 instances
Balanced profiles options for Intel x86-64 virtual server instances.
name: ibmc-vpc-block-retain-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
profile: custom
region: ""
resourceGroup: ""
sizeIOPSRange: |-
[10-39]GiB:[100-1000]
[40-79]GiB:[100-2000]
[80-99]GiB:[100-4000]
[100-499]GiB:[100-6000]
[500-999]GiB:[100-10000]
[1000-1999]GiB:[100-20000]
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-general-purpose
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: general-purpose
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
kind: List
metadata:
annotations:
version: 2.0.3_354
* UI
* CLI
* API







 File Storage for VPC profiles 

When you provision File Storage for VPC file shares by using the IBM Cloud console, CLI, or API, you specify a file share profile. The profile defines the performance level that you require based on the file share size.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.



 File storage profiles overview 

When you [create a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-create) in your availability zone, you select share size and IOPS performance based on a file storage profile. New file shares are created based on the high performance, [dp2](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uidp2-profile) profile.

Earlier file shares that were created by using either the [IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uifs-tiers) profiles or [custom IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uifs-custom) profile can continue to operate based on these profiles. You can also update these file shares to use the dp2 profile or switch back to a previous profile. However, you cannot use the previous profiles when you create a new file share.

Table 1 shows the dp2 profile performance levels compared to the earlier profiles. [Table 2](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uidp2-profile) presents the IOPS and capacity ranges for the dp2 profile.
If your backup storage utilization is greater than 60 GB for the month (in this scenario), you are charged an overage of $0.03/month per gigabyte.

By default, Cloud Databases provides a daily backup that is stored for 30 days. These backups, and any on-demand backups you make, all count toward the above allocation.

In the above example, if your database contains 2 GB of data and you have not taken any on-demand backups, then your total backup size is 2 GB x 30 = 60 GB. Your backup costs are nil.

If your database contains 15 GB of data and you have not taken any on-demand backups, then your total backup size is 15 GB x 30 = 450 GB. In this scenario, your backup costs are (450 GB - 60 GB) * 0.03 = $11.7 per month.

Most deployments will not ever go over the allotted credit.





 Dedicated Cores Pricing 

You have the option of selecting the CPU allocation for your deployment. With dedicated cores, your resource group is given a single-tenant host with a guaranteed minimum reserve of cpu shares. Your deployments are then allocated the number of CPUs you specify. The cost of dedicated cores is $30 per core per month, and each member gets the selected number of cores. For example, if you provision a deployment with three dedicated cores per member that is a total of six cores and billed at $180 per month.

Dedicated cores are an optional feature. The default Shared CPU setting provisions your deployment on hosts with shared compute resources and incurs no additional charge.





 Scaling per Member 

Databases for PostgreSQL deployments have minimum and maximum allocation for disk and RAM as shown. Scaling deployments through the API/CLI provides more granularity and also allows a user to scale a database instance up to 4 TB of disk per member.



Table 1. Per Member Scaling Limits

 Resource Minimum Maximum Scaling Granularity (API/CLI) 

 Disk 5 GB per member 4 TB per member 1024 MB per member 
 RAM 1 GB per member 112 GB per member 128 MB per member 
 CPU (if enabled) 3 CPUs per member 28 CPUs per member 1 CPU per member
[Compute](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profilescompute-dh-pr) Best for workloads with intensive CPU demands, such as medium to high web traffic workloads, production batch processing, and front-end web servers. Compute profiles offer vCPU to memory ratios with 1 vCPU to 2 GiB of RAM. Compute profiles are offered with and without instance storage. 
 [Memory](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profilesmemory-dh-pr) Best for memory intensive processes, such as memory caching, intensive database applications, or in-memory analytics workloads. Memory profiles offer vCPU to memory ratios with 1 vCPU to 8 GiB of RAM. Memory profiles are offered with and without instance storage. 
 [Very High Memory with instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profilesvhm-is-dh-pr) Best for OLAP workloads and SAP-related services, such as SAP NetWeaver. The Very High Memory profile offers 1 vCPU to 14 GiB of RAM memory ratio, is hosted exclusively on the Intel® Xeon® Platinum Cascade Lake server, and includes instance storage for temporary swap space or cache. 
 [Ultra High Memory with instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-dh-profilesuhm-is-dh-pr) Best for in-memory OLTP databases, such as SAP. The Ultra High Memory profile offers the highest vCPU to memory ratios with 1 vCPU to 28 GiB of RAM, is hosted exclusively on the Intel® Xeon® Platinum Cascade Lake server, and includes instance storage for temporary swap space or cache 



Profiles with AMD manufactured processors are available in the Toronto region.



 Balanced 

The Balanced profile provides a good mix of performance and scalability for more common workloads.

The Balanced with instance storage profile provides a good mix of performance and scalability for more common workloads.
After you set storage bandwidth, network bandwidth is automatically adjusted so the total bandwidth of the instance equals the displayed Total bandwidth value. The value for Network bandwidth or Storage bandwidth cannot be set less than 500 Mbps.

To view the new bandwidth allocation, you must either stop and start the instance, or detach and reattach secondary volumes.





 Adjusting bandwidth allocation using the CLI 

You can adjust the allocation of your instance's total bandwidth between network bandwidth and storage bandwidth using the CLI.

To reallocate instance bandwidth by using the CLI, run the instance-update command and specify the total storage bandwidth in megabits per second (Mbps) for the total-volume-bandwidth parameter. Here, INSTANCE can be ID or Name of the instance. Use this syntax:

ibmcloud is instance-update INSTANCE --total-volume-bandwidth VALUE





 Adjusting total storage bandwidth allocation from the API 

You can adjust total storage bandwidth for an existing instance. Make a PATCH /instances call and specify total_volume_ bandwidth. Total storage bandwidth (in megabits per second) is the total bandwidth allocated for primary boot and secondary attached data volumes. Increasing total storage bandwidth results in a corresponding decrease in network bandwidth. The minimum network bandwidth you can have is 500 mbps, so adjust total storage bandwidth accordingly. For example,

curl -X PATCH "$vpc_api_endpoint/v1/instances/$instance_id?version=2021-06-22&generation=2" -H "Authorization: $iam_token" -d '{
"total_volume_bandwidth": 500
}'

Bandwidth allocation is also realized when you add a secondary volume using POST / volume_attachments or delete a volume using DELETE volume_attachments.





 Retrieving the virtual server instance identifier 

When a virtual server instance is created, that instance is automatically assigned an instance identifier (ID), which includes the SMBIOS system-uuid as a portion of the ID. The ID can be up to 64 bytes in length and it consists of digits, lower-case letters, underscores, and dashes.
Flex storage class pricing 

Regional

Cross Region

Single Data Center



Table 1. Storage Capacity (GB/month)

 Storage used US South US East EU United Kingdom EU Germany AP Australia AP Japan São Paulo, Brazil Toronto, Canada 

 0 - 499.99 TB $0.009 $0.009 $0.0096 $0.0099 $0.0108 $0.0102 $0.0108 $0.0093 
 500+ TB $0.009 $0.009 $0.0096 $0.0099 $0.0108 $0.0102 $0.0108 $0.0093 



Regional

Cross Region

Single Data Center



Table 2. Public outbound bandwidth (GB/month)

 Bandwidth used US South US East EU United Kingdom EU Germany AP Australia AP Japan São Paulo, Brazil Toronto, Canada 

 0 - 50 TB $0.09 $0.09 $0.09 $0.09 $0.14 $0.14 $0.18 $0.09 
 Next 100 TB $0.07 $0.07 $0.07 $0.07 $0.11 $0.11 $0.14 $0.07 
 Next 350 TB $0.05 $0.05 $0.05 $0.05 $0.08 $0.08 $0.10 $0.05 
 Greater than 500 TB Contact us Contact us Contact us Contact us Contact us Contact us Contact us Contact us 



Regional

Cross Region

Single Data Center



Table 3. Operational Requests

 Request type US South US East EU United Kingdom EU Germany AP Australia AP Japan São Paulo, Brazil Toronto, Canada 

 Class A: PUT, COPY, POST and LIST (per 1,000) $0.01 $0.01 $0.01 $0.01 $0.01 $0.01 $0.01 $0.01 
 Class B: GET and all others (per 10,000) $0.01 $0.01 $0.01 $0.01 $0.01 $0.01 $0.01 $0.01 
 Delete requests No charge No charge No charge No charge No charge No charge No charge No charge
Pricing 

A Databases for MySQL Standard plan deploys as one highly available MySQL cluster with three data members. Your data is replicated on all members. The Standard plan is priced based on the total amount of disk storage, RAM, dedicated cores, and backup storage that is allocated to deployments, prorated hourly. Databases for MySQL deployments have a minimum of 10 GB of disk and 1 GB of RAM per data member.



 Using the Pricing Calculator 

Templates are provided for ease of use and provide balanced resource allocations appropriate for general-purpose workloads. The Custom tab can be used to configure Disk, RAM, and vCPU, as wanted.

For pricing estimation, use the Add to Estimate button on the [Databases for MySQL catalog page](https://cloud.ibm.com/catalog/databases-for-mysql). Input your total consumption across three data members into the calculator. This is roughly double the size of your data because your data is replicated to all members. For example, 20 GB of disk and 1 GB of RAM across three data members would be priced at 60 GB of disk and 3 GB of RAM respectively.





 Backups Pricing 

You receive your total disk space purchased, per database, in free backup storage. For example, in a given month, if you have a Databases for MySQL deployment that has 20 GB of disk per member, and has three data members, you receive 60 GB of backup storage free for that month. If your backup storage utilization is greater than 60 GB for the month (in this scenario), you are charged an overage of $0.03/month per gigabyte.

By default, Cloud Databases provides a daily backup that is stored for 30 days. These backups, and any on-demand backups you make, all count toward the above allocation.

In the above example, if your database contains 2 GB of data and you have not taken any on-demand backups, then your total backup size is 2 GB x 30 = 60 GB. Your backup costs are nil.
If your backup storage utilization is greater than 60 GB for the month (in this scenario), you are charged an overage of $0.03/month per gigabyte.

By default, Cloud Databases provides a daily backup that is stored for 30 days. These backups, and any on-demand backups you make, all count toward the above allocation.

In the above example, if your database contains 2 GB of data and you have not taken any on-demand backups, then your total backup size is 2 GB x 30 = 60 GB. Your backup costs are nil.

If your database contains 15 GB of data and you have not taken any on-demand backups, then your total backup size is 15 GB x 30 = 450 GB. In this scenario, your backup costs are (450 GB - 60 GB) * 0.03 = $11.7 per month.

Most deployments will not ever go over the allotted credit.





 Dedicated Cores Pricing 

You have the option of selecting the CPU allocation for your deployment. With dedicated cores, your resource group is given a single-tenant host with a guaranteed minimum reserve of cpu shares. Your deployments are then allocated the number of CPUs you specify. The cost of dedicated cores is $30 per core per month, and each member gets the selected number of cores. For example, if you provision a deployment with 3 dedicated cores per member, that is a total of 9 cores, and billed at $270 per month.

Dedicated cores are an optional feature. The default Shared CPU setting provisions your deployment on hosts with shared compute resources and incurs no additional charge.





 Scaling per Member 

Databases for etcd deployments have minimum and maximum allocation for disk and RAM as shown. Scaling deployments through the API/CLI provides more granularity and also allows a user to scale a database instance up to 4 TB of disk per member.



Table 1. Per Member Scaling Limits

 Resource Minimum Maximum Scaling Granularity (API/CLI) 

 Disk 5 GB per member 4 TB per member 1024 MB per member 
 RAM 1 GB per member 112 GB per member 128 MB per member 
 CPU (if enabled) 3 CPUs per member 28 CPUs per member 1 CPU per member
In addition, their health checks ensure that workloads only travel through healthy VNF devices. For more information about this service, see [Creating a network load balancer with routing mode for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vnf).





 14 September 2021 

Terraform available for Placement Groups
: You can now create and manage placement groups in your IBM Cloud VPC by using Terraform. See [Managing placement groups](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-placement-group&interface=terraform).





 07 September 2021 

New Very High Memory instance profile family (LA)
: Very High Memory profiles are available in the US South (Dallas), US East (Washington DC), Canada (Toronto), EU Germany (Frankfurt), and Japan (Tokyo) regions. Very High Memory profiles offer a core to RAM ratio of 1 vCPU to 14 GiB of RAM. This family is optimized for running high-compute-intensity in-memory workloads like SAP BW/4 HANA. For more information, see [Very High Memory profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=uivhmemory).

Instance Bandwidth (LA)
: Instance bandwidth is now available in the US South (Dallas), US East (Washington DC), Canada (Toronto), EU Germany (Frankfurt), Japan (Osaka), Brazil (Sao Paulo) regions. When you provision a virtual server instance, you can now allocate bandwidth between attached volumes and networking by using the API and CLI. You can adjust bandwidth after you provision a virtual server instance by using the UI, API, and CLI. The maximum bandwidth capacity is determined by the instance profile that you select during instance provisioning. For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles).





 01 September 2021 

New GPU Instance Profile family (Beta)
FAQs: Reserved capacity and instances 



  Which virtual server instance types can be reserved? 

Only SAN-backed balanced, memory, and compute family sizes can be reserved.





  Can I combine different CPUxRAM sizes or change the sizes later? 

You cannot combine different CPUxRAM sizes or change the sizes later. The set of virtual server instances that you provision to your reserved capacity must be the same size as your reservation.





  Is my payment upfront or monthly? 

Reserved capacity and instances are purchased for a 1 or 3-year term. After that point, you're committed to a monthly payment.





  What happens at the end of my contract? 

Depending on whether you choose hourly or monthly billing, the billing price for the CPU and RAM converts to the current list price, with any account discounts applied. Contact your sales representative, who in turn works with your global sales manager to determine end-of-contract options such as renewal or restructuring of your contract provisions. For more information about pricing, see [Build your virtual server](https://www.ibm.com/cloud/virtual-servers).





  What happens if I don't need my reserved virtual server instances anymore? 

You can reclaim reserved virtual server instances, but you cannot cancel reserved capacity.





  Does the reservation include everything that I configured into my virtual server instance? 

Only CPU and RAM are included in your reservation. Primary disk and no-additional charge network or storage products are not included in your reservation. More network bandwidth, storage capacity, OS, and third-party software are charged on an hourly or monthly basis, which depends on the instance type.





  Why do I need to choose hourly or monthly billing on the virtual server instance? 

Your additional software, storage, and network selections need to be billed either hourly or monthly.
Other volumes contain archived information that doesn't change much, so you'd prefer to back them up weekly. You can create four backup plans per policy. Your solution might look like this:

Create a backup policy with an hourly backup plan for the time-critical volumes:



* When you create the policy, create a tag for the target volumes (for example, hourly-finance). Provide a policy name that reflects the interval and type of data. It can help organize policies in the list and the volumes that are associated with them.
* Add the new tags to your volumes - Specify tags in Apply tags to target resources in the UI or specify them in the CLI or API. It ensures that all volumes that you want to back up hourly are included by the hourly backup policy.
* If your volume already contains tags: verify that another backup policy isn't already backing up the volume. If that's the case, remove the extra tag from the volume so that it is not backed up twice, and incurring extra costs.
* Set a retention period that does not exceed the total backup limitation of 10 TB. For hourly backups, you might need a shorter retention period than daily or weekly backups. You are also allowed up to 100 backups of the volume. Don't exceed that quota.



Create a weekly backup plan for archived data:



* Create another plan and define the retention period as 7 days. Assess the length of time that you can afford not to back up archived data, the amount of data that is in the volume, and anticipated changes. The limit is 10 TB for all backups of the volume.
* Set a longer retention period to have multiple copies of your archive volume. For weekly backups, you might want to retain the backups for a month.







 Next steps 

[Plan a strategy](https://cloud.ibm.com/docs/vpc?topic=vpc-backups-vpc-planning) for backing up your Block Storage for VPC volumes. [Create a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create).