vania-janet/multiturn-rag-retrieval-data huggingface dataset:
1. Remove operating system ISCSI sessions and, if applicable, unmount the device.
2. Revoke access for the host from the storage device in the [IBM Cloud® console](https://cloud.ibm.com/login).
3. Remove automatic discovery, and if applicable, remove connect database entries from the operating system for ISCSI connections.



* How do endurance and performance storage differ?

Endurance and Performance are provisioning options that you can select for storage devices. In short, Endurance IOPS tiers offer predefined performance levels whereas you can fine-tune those levels with the Performance tier. The same devices are used but delivered with different options. For more information, see [IBM Cloud Block Storage: Details](https://www.ibm.com/cloud/block-storage/details).
* I am unable to upgrade storage. What can affect the ability to upgrade or expand storage?

The following situations can affect the ability to upgrade or expand storage:



* If the original volume is the Endurance 0.25 tier, then the IOPS tier can't be updated.
* Older storage types can't be upgraded. For more information, see [expanding Block Storage for Classic Capacity](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-expandingcapacity).
* The permissions that you have in the [IBM Cloud® console](https://cloud.ibm.com/login) can be a factor. For more information, see the topics within [User roles and permissions](https://cloud.ibm.com/docs/account?topic=account-userroles).



* Are ISCSI LUNs thin or thick provisioned?

All File and Block Storage for Classic services are thin-provisioned. This method is not modifiable.
* My billing ID changed, what does this mean?

You might notice that your Storage volumes are now billed as "Endurance Storage Service” or "Performance Storage Service" instead of "Enterprise Storage". You may also have new options in the console, such as the ability to adjust IOPS or increase capacity.
* If you want to delete the data in your persistent storage, review the delete options for the type of storage that you use.



* [File storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storagestorage_delete_options_file)
* [Block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storagecleanup_block) for classic clusters
* [Block storage](https://cloud.ibm.com/docs/containers?topic=containers-storage-block-vpc-remove) for VPC clusters
* [Object storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-deleting-multiple-objects-patterns)
* [Portworx](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_removing)





To remove a cluster:



1. Optional: From the CLI, save a copy of all data in your cluster to a local YAML file.

kubectl get all --all-namespaces -o yaml
2. Remove the cluster.



* From the IBM Cloud console



1. Select your cluster and click Delete from the More actions menu.



* From the IBM Cloud CLI



1. List the available clusters.

ibmcloud ks cluster ls
2. Delete the cluster.

ibmcloud ks cluster rm --cluster <cluster_name_or_ID>





3. Follow the prompts and choose whether to delete cluster resources, which include containers, pods, bound services, persistent storage, and secrets.



* Persistent storage: If you [dynamically provisioned](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptsdynamic_provisioning) storage with a storage class that sets reclaimPolicy: Delete, your persistent volume claim (PVC), persistent volume (PV), and the storage instance are automatically deleted when you delete the cluster.
About increasing volume capacity 

For Block Storage for VPC boot and data volumes, you can increase volume capacity from its initial setting, within limits.



 Expandable volume concepts 

You can increase capacity for boot and data volumes that are attached to a virtual server instance.



 Data volumes 

After you provisioned and attached a data volume to a virtual server instance, you can increase its volume size in GB increments up to 16,000 GB capacity, depending on your volume profile. This process doesn't require you to perform manual steps. For example, you don't need to migrate your data to a larger volume. The resizing operation causes no outage or lack of access to the storage.

Billing for the volume is automatically updated to add the pro-rated difference of the new price to the current billing cycle. The new full amount is then billed in the next billing cycle.

To expand a volume, it must be in an available state and the instance must be running. Your user authorization is verified before the volume is expanded. You can use the UI, CLI, API, or Terraform to expand volume capacity. You can expand the volume multiple times, up to its [maximum capacity limit](https://cloud.ibm.com/docs/vpc?topic=vpc-about-increasing-volume-capacityexp-vols-capacity-IOPs-limitations). After the volume is expanded, you can't reduce the volume capacity.

Expanded capacity is determined by the maximum that is allowed by the volume's profile.

Volumes that were created by using an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers-beta) can be expanded to the maximum size for its IOPS tier:



* A general-purpose, 3 IOPS/GB profile can be expanded up to 16,000 GB.
* A 5 IOPS/GB profile can be expanded up to 9,600 GB.
* A 10 IOPS/GB profile can be expanded up to 4,800 GB.



IOPS values are automatically adjusted for tiered profiles, based on the size of the volume.
Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

How do I delete the storage when I want to keep my cluster?
: When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete, you can remove the PVC to start the deletion process of your persistent storage. Your PVC, PV, and storage instance are automatically removed.
: For storage that was [statically provisioned](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptsstatic_provisioning), VPC Block Storage, or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, you must manually remove the PVC, PV, and the storage instance to avoid further charges.

How does the billing stop after I delete my storage?
: Depending on what storage components you delete and when, the billing cycle might not stop immediately. If you delete the PVC and PV, but not the storage instance in your IBM Cloud account, that instance still exists and you are charged for it.

If you delete the PVC, PV, and the storage instance, the billing cycle stops depending on the billingType that you chose when you provisioned your storage and how you chose to delete the storage.



* When you manually cancel the persistent storage instance from the IBM Cloud console or the ibmcloud sl CLI, billing stops as follows:



* Hourly storage: Billing stops immediately. After your storage is canceled, you might still see your storage instance in the console for up to 72 hours.
* Monthly storage: You can choose between immediate cancellation or cancellation on the anniversary date. In both cases, you are billed until the end of the current billing cycle, and billing stops for the next billing cycle. After your storage is canceled, you might still see your storage instance in the console or the CLI for up to 72 hours.



* Immediate cancellation: Choose this option to immediately remove your storage. Neither you nor your users can use the storage anymore or recover the data.



* Anniversary date: Choose this option to cancel your storage on the next anniversary date.
Why are no spaces associated with my current org? 

You can't create an app if no space is associated with your current organization.

  What’s happening 

When you try to create an app the following error message is displayed:

> BXNUI0097E: Before you can add an app, at least one space must be associated with your organization and region. On the Dashboard, click Create a Space. When the space is created, try again.

  Why it’s happening 

Apps must be created in a space under your organization.

  How to fix it 

To create a space, use one of the following methods:



*  From the console menu bar, click Manage > Account. Expand Account resources and click Cloud Foundry orgs. Then, select the organization in which you want to create the space, and click Add a space.
*  From the IBM Cloud CLI, enter ibmcloud account space-create <space_name> -o <organization_name>.
The RAM provisioned to your deployment remains for your future needs, or until you scale down your deployment manually. The disk provisioned to your deployment remains because disk cannot be scaled down.
* If you need to add resources to your deployment occasionally or rarely, you can [manually scale](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-resources-scaling) your deployment.







 Configuring Autoscaling in the UI 

The Autoscaling pane is on the Resources tab of your deployment's Manage page. To enable scaling, enter your parameters. Then, check the boxes to enable the parameters you are using. Be sure to click Save Changes for your configuration to be saved and your changes to take effect.

To disable autoscaling, clear the boxes for the parameters that you no longer want to use. If you clear all the boxes, autoscaling is unavailable. Click Save Changes to save the configuration.





 Configuring Autoscaling in the CLI 

You can get the autoscaling parameters for your deployment through the CLI by using the [cdb deployment-autoscaling](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-) command.

ibmcloud cdb deployment-autoscaling <deployment name or CRN> member

To enable and set autoscaling parameters through the CLI, use a JSON object or file with the [cdb deployment-autoscaling-set](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-set-) command.
: The increased capacity in GiB, for example 250.
5. Log in to your app pod.

oc exec <pod-name> -it bash
6. Get the file system details and make a note of the Filesystem path that you want to update. You can also grep for the mount path as specified in your application pod. df -h | grep <mount-path>.

df -h

Example output

Filesystem Size Used Avail Use% Mounted on
overlay 98G 64G 29G 70% /
tmpfs 64M 0 64M 0% /dev
tmpfs 32G 0 32G 0% /sys/fs/cgroup
shm 64M 0 64M 0% /dev/shm
/dev/vda2 98G 64G 29G 70% /etc/hosts
/dev/vdg 9.8G 37M 9.8G 1% /mount-path Note the Filesystem path that corresponds to the mountPath that you specified in your app.
tmpfs 32G 40K 32G 1% /run/secrets/kubernetes.io/serviceaccount
tmpfs 32G 0 32G 0% /proc/acpi
tmpfs 32G 0 32G 0% /proc/scsi
tmpfs 32G 0 32G 0% /sys/firmware
7. Resize the file system.

sudo resize2fs <filesystem-path>

Example command

sudo resize2fs /dev/vdg
8. Verify the file system is resized.

df -h









 Backing up and restoring data 

Data on Block Storage for VPC is secured across redundant fault zones in your region. To manually back up your data, use the Kubernetes oc cp command.

You can use the oc cp[command](https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commandscp) to copy files and directories to and from pods or specific containers in your cluster
* Number of shares - When want to use the same configuration setting for each file share, specify the number of file shares for the NFS shared storage that you want to add.
* Size (GB) - Select the capacity that meets your shared storage needs.
* Performance - Select the IOPS (input/output operations per second) per GB based on your workload requirements.
* Add shared storage - Select to add individual file shares with different configuration settings.



The following table indicates the performance level details.



Table 4. NFS performance level options

 Option Details 

 0.25 IOPS/GB This option is designed for workloads that are not used often. Example applications include vaulted data, hosting large databases with legacy data, or virtual disk images of virtual memory system as backup. 
 2 IOPS/GB This option is designed for most general-purpose workloads. Example applications include hosting small databases, backing up web applications, or VM disk images for a hypervisor. 
 4 IOPS/GB This option is designed for higher-intensity workloads that have a high percentage of active data at a time. Example applications include transactional databases. 
 10 IOPS/GB This option is designed for the most demanding workload types, such as analytics. Example applications include high-transaction databases and other performance-sensitive databases. This performance level is limited to a maximum capacity of 4 TB per file share. 







 vSAN storage 

Specify the following vSAN options.



 Size for vSAN capacity disks 

Select an option for the capacity disks that you need.





 Number of vSAN capacity disks 

Specify the number of capacity disks that you want to add.

If you want to add more capacity disks, select the High performance with Intel Optane checkbox. This option provides two extra capacity disk bays, which are useful for workloads that require less latency and higher IOPS throughput.

The High performance with Intel Optane option is available only for vSphere 6 instances.





 Size for vSAN cache disks 

Review the Size for vSAN cache disks value. The value depends on whether you checked the High performance with Intel Optane box.





 Number of vSAN cache disks 

Review Number of vSAN cache disks.
}





 Expand block storage volumes with Terraform 

To increase the capacity of a volume, use the ibm_is_volume resource. When applied, the following example updates the capacity to 8,000 GB.

resource "ibm_is_volume" "storage" {
name = "demo-volume-update"
size = 8000
profile = "general-purpose"
zone = "us-south-2"
}

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 

Create more volumes or manage your existing block storage volumes.



* [Creating block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage).
* [Managing block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage).



Optionally, [increase the capacity of boot volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes).
* UI
* CLI
* API
* Terraform







 Increasing block storage volume capacity 

After you provisioned a Block Storage for VPC data volume and attached it to a virtual server instance, you can increase its volume size in the UI, from the CLI, with the API or Terraform.

You can't change the volume to a smaller size after you expand its capacity. However, if your requirements change, you can expand the same volume again up to the maximum capacity that's available for its profile.



 Expand block storage volumes in the UI 

Follow these steps to expand volume capacity:



1. Go to the list of block storage volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes. By default, block storage volumes display for all resource groups in your region.
2. In the list of all Block storage for VPC volumes, click the name of the volume you want to expand to see the volume details.

The volume that you select must be attached to a virtual server instance. In the list of volumes, its attachment type is data.
3. Alternatively, go to a virtual server instance with an attached volume that you want to expand and select it from the list of attached volumes.
4. On the volume details page, locate Size. The current IOPS profile and volume size are displayed.
5. Click the pencil icon. Alternatively, click the Actions menu and select Expand block storage volume.
6. In the panel, increase the volume size in GB up to 16,000 GB.

The maximum size that you can expand to is based on the selected IOPS profile or custom volume settings. The UI indicates the maximum capacity for the selected profile.
For more information about each storage class, see the [storage class reference](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_reference). If you want to change any of the pre-set values, create your own customized storage class.
5. Decide on a name for your bucket. The name of a bucket must be unique in IBM Cloud Object Storage. You can also choose to automatically create a name for your bucket by the IBM Cloud Object Storage plug-in. To organize data in a bucket, you can create subdirectories.

The storage class that you chose earlier determines the pricing for the entire bucket. You can't define different storage classes for subdirectories. If you want to store data with different access requirements, consider creating multiple buckets by using multiple PVCs.
6. Choose if you want to keep your data and the bucket after the cluster or the persistent volume claim (PVC) is deleted. When you delete the PVC, the PV is always deleted. You can choose if you want to also automatically delete the data and the bucket when you delete the PVC. Your IBM Cloud Object Storage service instance is independent from the retention policy that you select for your data and is never removed when you delete a PVC.



Now that you decided on the configuration that you want, you are ready to [create a PVC](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_apps) to provision IBM Cloud Object Storage.





 Verifying your installation 

Review the pod details to verify that the plug-in installation succeeded.



1. Verify the installation succeeded by listing the driver pods.

kubectl get pod --all-namespaces -o wide | grep object

Example output

ibmcloud-object-storage-driver-9n8g8 1/1 Running 0 2m
ibmcloud-object-storage-plugin-7c774d484b-pcnnx 1/1 Running 0 2m
From a virtual disk, you can create one or more volumes, where you can configure the size, drive letter or folder, file system (NTFS file system or Resilient File System (ReFS), allocation unit size, and optionally a volume label.

For more information, see [Storage Spaces](https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/overview).





 About MS SQL Server 2019 editions 

A summary of SQL Server editions are as follows:



* Evaluation - Functionally the same as the Enterprise edition, and free for a 180 day trial but it isn’t supported. Can be upgraded to any edition but Express.
* Express LocalDB - A lightweight version of Express that has all of its programmability features, runs in user mode and has a fast, zero-configuration installation and a short list of prerequisites.
* Express - Appropriate only for environments in which data size is small, is not expected to grow. This edition has no SQL Server Agent to automate backups. This edition is limited to a maximum of 1 socket or 4 cores or 1,410 MB available buffer pool memory or 10 GB individual database size.
* Express with Advanced Services - Similar to Express edition in limitations, but includes some additional features including R integration, full-text search, and distributed replay.
* Web - Appropriate for production environments but limited to low-cost server environments for web applications.
* Standard - Appropriate for production environments but limited to a maximum of 4 sockets or 24 cores or 128 GB of buffer pool memory.
* Developer - Appropriate for all pre-production environments, and supports the same features and capacity as the Enterprise edition and is free.



For a full reference of SQL Server editions, refer to [Editions and supported features of SQL Server 2019 (15.x)](https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15).





 About Microsoft licensing 

IBM Cloud virtual servers can include Microsoft Windows operating system licenses.
Choose the [type of File Storage for Classic](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-getting-startedprereqs) that you want to provision.

Bronze, silver, and gold storage classes
: These storage classes provision Endurance storage. Endurance storage lets you choose the size of the storage in gigabytes at predefined IOPS tiers.

Custom storage class
: This storage class provisions Performance storage. With performance storage, you have more control over the size of the storage and the IOPS.





 IOPS 

Choose the size and IOPS for your File Storage for Classic. The size and the number of IOPS define the total number of IOPS (input/ output operations per second) that serves as an indicator for how fast your storage is. The more total IOPS your storage has, the faster it processes read and write operations.

Bronze, silver, and gold storage classes
: These storage classes come with a fixed number of IOPS per gigabyte and are provisioned on SSD hard disks. The total number of IOPS depends on the size of the storage that you choose. You can select any whole number of gigabyte within the allowed size range, such as 20 Gi, 256 Gi, or 11854 Gi. To determine the total number of IOPS, you must multiply the IOPS with the selected size. For example, if you select a 1000Gi File Storage for Classic size in the silver storage class that comes with 4 IOPS per GB, your storage has a total of 4000 IOPS.



Table of storage class size ranges and IOPS per gigabyte

 Storage class IOPS per gigabyte Size range in gigabytes 

 Bronze 2 IOPS/GB 20-12000 Gi 
 Silver 4 IOPS/GB 20-12000 Gi 
 Gold 10 IOPS/GB 20-4000 Gi 



Custom storage class
: When you choose this storage class, you have more control over the size and IOPS that you want. For the size, you can select any whole number of gigabyte within the allowed size range. The size that you choose determines the IOPS range that is available to you.
ibmcloud account space-delete SPACE [-o ORG] [-f]



For more information on managing accounts, users in an account by using the CLI, and the org, space, and roles of public Cloud Foundry environments, visit [Managing accounts, users, and Cloud Foundry orgs](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_account).







 Updating orgs and spaces by using the Cloud Foundry API 



 Updating organizations 

You can update organizations by calling the Cloud Foundry API. For detailed information about how to use it, see [Update an Organization](http://v3-apidocs.cloudfoundry.org/version/3.97.0/index.htmlupdate-an-organization). Check the following sample request:

curl "https://api.example.org/v3/organizations/[guid]" -X PATCH -H "Authorization: bearer [token]" -H "Content-Type: application/json" -d '{ "name": "my-organization" }'





 Deleting spaces 

You can delete spaces by calling the Cloud Foundry API. For detailed information about how to use it, see [Delete a space](http://v3-apidocs.cloudfoundry.org/version/3.97.0/index.htmldelete-a-space). Check the following sample request:

curl "https://api.example.org/v3/spaces/[guid]" -X DELETE -H "Authorization: bearer [token]"