vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Storage class reference 

The available storage classes correspond to the predefined File Storage for VPC profiles. For more information about the profiles and IOPs tiers, see [File Storage for VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles).

By default, all File Storage for VPC devices are provisioned with an hourly billing type and endurance storage. If you choose a monthly billing type, when you remove the persistent storage, you still pay the monthly charge for it, even if you used it only for a short amount of time. If you want to keep your data, then choose a retain storage class. When you delete the PVC, only the PVC is deleted. The PV, the physical storage device in your IBM Cloud infrastructure account, and your data still exist. To reclaim the storage and use it in your cluster again, you must remove the PV and follow the steps for [using existing File Storage for VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-file-vpc-apps). If you want the PV, the data, and your physical File Storage for VPC device to be deleted when you delete the PVC, choose a storage class without retain

Storage classes that have retain in the title have a reclaim policy of Retain. Example: ibmc-file-retain-bronze. Storage classes that don't have retain in the title have a reclaim policy of Delete. Example: ibmc-file-bronze.

3 IOPS

5 IOPS

10 IOPS



3 IOPS

 Characteristics          Setting                                                                           

 Name                     ibmc-vpc-file-3iops-tier  <br>ibmc-vpc-file-retain-3iops-tier                     
 Type                     Endurance storage                                                                 
 File system              NFS                                                                               
 IOPS per gigabyte        3                                                                                 
 Size range in gigabytes  20-12000 Gi                                                                       
 Hard disk                SSD                                                                               
 Reclaim policy           ibmc-vpc-file-3iops-tier: Delete  <br>ibmc-vpc-file-retain-3iops-tier: Retain     
 Billing                  Hourly                                                                            
 Pricing                  [Pricing information](https://cloud.ibm.com/cloud-storage/file/order)
* 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.



4. Choose the size and IOPS for your block storage. 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 block storage 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 gigabytes within the allowed size range. The size that you choose determines the IOPS range that is available to you. You can choose an IOPS that is a multiple of 100 within the specified range. The IOPS that you choose is static and does not scale with the size of the storage. For example, if you choose 40Gi with 100 IOPS, your total IOPS remains 100. The IOPS to gigabyte ratio also determines the type of hard disk that is provisioned for you. For example, if you are using 500Gi at 100 IOPS, your IOPS to gigabyte ratio is 0.2.
-h, --help Show this message and exit.

If you're using the replication feature, be sure that the schedule that you're deleting isn't the schedule that is used by replication. For more information about deleting a replication schedule, see [here](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-replication).





 Deleting a snapshot in the UI 

Snapshots that are no longer needed can be manually removed to free up space for future snapshots. Deletion is done through Storage > File Storage for Classic.



1. Click your storage volume and click Snapshot to see the list of existing snapshots.
2. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg) next to a particular snapshot and click Delete to delete the snapshot. This deletion doesn't affect any future or past snapshots on the same schedule as snapshots don't depend on each other.



Manual snapshots that aren't deleted in the portal manually, are automatically deleted when you reach space limitations. The oldest snapshot is deleted first.





 Deleting a snapshot from the SLCLI 

Snapshots that are no longer needed can be manually removed to free up space for future snapshots. You can delete a snapshot from the SLCLI by using the following command.

 slcli file snapshot-delete --help
Usage: slcli file snapshot-delete [OPTIONS] SNAPSHOT_ID

Options:
-h, --help Show this message and exit.

Manual snapshots that aren't deleted in the portal manually, are automatically deleted when you reach space limitations. The oldest snapshot is deleted first.





 Restoring storage volume to a specific point in time by using a snapshot in the UI
[Enabling the IBM Cloud File Storage for VPC add-on](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-installstorage-file-vpc-install)



* [Prerequisites](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-installprereqs-store-file-vpc)



[Adding File Storage for VPC to apps](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-appsstorage-file-vpc-apps)



* [Deploying an app that uses File Storage for VPC with dynamic provisioning](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-appsvpc_add_file_dynamic)
* [Deploying an app that uses File Storage for VPC with static provisioning](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-appsvpc_add_file_static)



[Managing IBM Cloud File Storage for VPC](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingstorage-file-vpc-managing)



* [Creating a custom storage class](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingstorage-file-vpc-custom-sc)
* [Updating the File Storage for VPC add-on](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingstorage-file-vpc-update)
* [Understanding your storage removal options](https://cloud.ibm.com/docs/containers?topic=containers-storage-file-vpc-managingvpc_storage_delete_options_file)
* Anniversary date: Choose this option to cancel your storage on the next anniversary date. Your storage instances remain active until the next anniversary date and you can continue to use them until this date, such as to give your team time to make backups of your data.



* When you dynamically provisioned the storage with a storage class that sets reclaimPolicy: Delete and you choose to remove the PVC, the PV and the storage instance are immediately removed. For hourly billed storage, billing stops immediately. For monthly billed storage, you are still charged for the remainder of the month. After your storage is removed and billing stops, you might still see your storage instance in the console or the CLI for up to 72 hours.



What do I need to be aware of before I delete persistent storage?
: When you clean up persistent storage, you delete all the data that is stored in it. If you need a copy of the data, make a backup for [file storage](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_backup_restore) or [block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_backup_restore).

I deleted my storage instance. Why can I still see my instance?
: After you remove persistent storage, it can take up to 72 hours for the removal to be fully processed and for the storage to disappear from your IBM Cloud console or CLI.

I deleted my cluster. How do I remove the remaining storage volumes?
: See the steps in [Why am I still seeing charges for block storage devices after deleting my cluster](https://cloud.ibm.com/docs/containers?topic=containers-ts_storage_clean_volume).





 Cleaning up persistent storage 

Remove the PVC, PV, and the storage instance from your IBM Cloud account to avoid further charges for your persistent storage.

Before you begin:



* Make sure that you backed up any data that you want to keep.
Note that you must delete your storage assignments before you can successfully delete your storage configuration.



1. From the Satellite storage dashboard, select the storage configuration you want to delete.
2. Select Actions > Delete
3. Enter the name of your storage configuration.
4. Select Delete.







 Removing the AWS EBS storage configuration from the CLI 

Use the CLI to remove the AWS EBS storage configuration.

Note that you must delete your storage assignments before you can successfully delete your storage configuration.



1. List your storage assignments and find the one that you used for your cluster.

ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)
2. Remove the assignment. After the assignment is removed, the AWS EBS driver pods and storage classes are removed from all clusters that were part of the storage assignment.

ibmcloud sat storage assignment rm --assignment <assignment_ID>
3. Verify that the AWS EBS driver is removed from your cluster.



1. List of the storage classes in your cluster and verify that the AWS EBS storage classes are removed.

oc get sc
2. List the pods in the kube-system namespace and verify that the AWS EBS storage driver pods are removed.

oc get pods -n kube-system | grep ebs
3. List the secrets in the kube-system namespace and verify that the AWS secret that stored your AWS credentials is removed.

oc get secrets -n kube-system | grep aws



4. Optional: Remove the storage configuration.



1. List the storage configurations.

ibmcloud sat storage config ls
2. Remove the storage configuration.

ibmcloud sat storage config rm --config <config_name>











 Parameter reference 



 1.1.0 parameter reference 



Table 1. 1.1.0 parameter reference

 Display name CLI option Type Description Required? Default value
If the data is very skewed across Db2 partitions, meaning that one or more Db2 partitions is almost full while other Db2 partitions still have significant capacity remaining, then see [Choosing a hash distribution key for a table in an MPP database](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.doc/learn_how/choosing_dist_key_mpp.html){: external}.
2. If one or more table spaces have reclaimable space, complete the following steps to reclaim that space:

Do not reclaim space during an online backup. The reclaim operation can also impact the performance of ongoing workloads, so it is best to run the following steps during off-peak hours.

a. Verify that an online backup is not running:

db2 "SELECT MEMBER,SUBSTR(UTILITY_DETAIL, 1, 150) AS CMD FROM TABLE(MON_GET_UTILITY(-2)) AS T"
 b. For every table space in the list generated by the previous step, reclaim the unused space by running the following command:
 {: codeblock}
db2 alter tablespace <tablespace_name> reduce max
3. If there is no disk space that can be reclaimed, you must either purge unwanted data or scale up the storage on your Db2 Warehouse on Cloud instance to ensure database stability.







 Additional information 

[Reclaimable storage](https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html)

[Reclaiming unused storage in DMS table spaces](https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.dbobj.doc/doc/t0055397.html)
* You will need to pick a region where Object Lock is supported, refer to [Integrated Services](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-service-availability) for details.
* A maximum default retention period of 100 years (or 36500 days) is supported.
* When using the console, it is also possible to set a Retain Until Date in months, in addition to days or years.



The retention period for an object cannot be decreased. If you are using default retention for validation testing please use a lower duration (such as 1 day) as the default retention, increasing it to your desired setting as needed.



 Creating and setting up your new bucket for use with Object Lock 



1. Navigate to your desired Object Storage instance and use Create Bucket with Customize your bucket option
2. Enter the required bucket configuration details as per your use case requirements
3. Navigate to the Object Versioning section and set it to Enabled
4. Look for Immutability, and under Object Lock click Add
5. Set Object Lock to Enabled
6. Optionally, set a default retention period.
7. Click on Save
8. Proceed with rest of the configuration settings and click Create bucket







 Enabling Object Lock on an existing bucket: 

A bucket can be set for Object Lock use as follows:



1. Navigate to your bucket Configuration section
2. Click on Object Versioning
3. At the Object Versioning section click on Edit, set the configuration option to Enabled and Save
4. Navigate to Object Lock section, click on Add
5. Set Object Lock to Enabled
6. Optionally, set a default retention period.
7. Click on Save







 Adding a Retain Until Date or Legal Hold to an object 



1. Navigate to the bucket with the target object
2. Toggle Display Versions
3. Go to the details of the target version
4. Add a retention period and/or toggle on a legal hold.









 Using Object Lock for business continuity and disaster recovery
* You cannot expand a volume that is at its maximum capacity for its [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers-beta) or [Custom](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) volume range.
* Data volumes can expand to 16,000 GB, with the following limitations:



* If the volume was created by using an [IOPS tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers-beta) that limits capacity to less than 16,000 GB, it can expand only to the allowed capacity for that tier.
* If the volume is a [custom volume](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom) that is created in a lower range that doesn't allow expanding to 16,000 GB, it can expand only to its maximum capacity for that custom range.
* Volumes can expand multiple times until maximum capacity is reached.



* IOPS can increase to the maximum that is allowed by the IOPS tier profile. While volume resizing does not incur downtime (that is, you don't need to restart the instance and reattach the volume), for the increased IOPS to take effect, you must restart the virtual server instance, or detach and reattach the volume from the instance.
* After you create a volume, can't change a volume's IOPS tier profile.
* You can't independently modify IOPS for a volume that is created from an IOPS tier profile. IOPS is adjusted when you expand a volume's capacity and then restart the instance, or attach and detach the volume from the instance.
* When you expand a volume that was created from a custom profile, the capacity is increased but the IOPS remains the same. You can't independently increase the IOPS.
Command options 

--config CONFIG
: Required. The name of the storage configuration that you want to remove. To list Satellite storage configurations, run ibmcloud sat storage config ls.

-f
: Optional. Force the command to run with no user prompts.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat storage config rm --config ocs-config







 ibmcloud sat storage config upgrade 

Upgrade a Satellite storage configuration to the latest template revision. Template revisions, if available, include the latest storage driver patch updates.

ibmcloud sat storage config upgrade --config CONFIG [-f] [--include-assignments] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Configuration resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--config CONFIG
: Required. The name of the storage configuration that you want to upgrade. To list Satellite storage configurations, run ibmcloud sat storage config ls.

-f
: Optional. Force the command to run with no user prompts.

--include-assignments
: Optional. Include this option to also update the assignments of the storage configuration to the latest configuration version.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat storage config upgrade --config ocs-config







 ibmcloud sat storage config sc add 

Add a custom storage class to a Satellite storage configuration.

ibmcloud sat storage config sc add --config-name CONFIG --name NAME [--param PARAM ...] [-q]



 Minimum required permissions
* UI
* CLI
* API







 Managing instance storage 

Instance storage provides fast, affordable, temporary storage that can improve the performance of some cloud native workloads (or apps or services). For more information, see [About instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage).

To provision an instance storage disk with your virtual server instance, select a profile that includes instance storage. The instance storage disk devices cannot be live attached or detached, as they are purchased as part of the instance profile itself. The general-purpose profile families (Balanced, Compute, and Memory) and some specialty profile families (Very High Memory and Storage Optimized) all have profile options with instance storage. The amount of instance storage is proportionally allocated based on the number of vCPUs assigned to the profile. For more information about profiles, see [Instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles).



 Provisioning a Virtual Server Instance with instance storage in the UI 

Before you can create a virtual server instance with instance storage, you need to create an IBM Cloud VPC.

To provision a with instance storage, complete the following steps:



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Virtual server instances.
2. On the Virtual server instances for VPC page, click Create and enter the required information. For more information about specific fields, see [Creating virtual servers](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).
3. To choose your instance storage profile, click View all profiles. All ox2 profiles and profiles with the letter "d" in the fourth position of the Profile name include instance storage.
Auto-scaling 

When you enable autoscaling, the storage on your Db2 on Cloud instance will automatically be scaled up if your storage use exceeds the threshold you specify. For example, you can choose to scale up your storage by 20GB if more than 90% of your storage is in use for a period of 15 minutes.

To monitor your storage usage, use the IBM Cloud® Monitoring integration, which provides metrics for disk space.



  General Autoscaling Parameters 



*  When to scale, based on usage over time.
*  A hard limit on scaling, your deployment stops autoscaling at the limit.



![paras.png](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/autoscaling_UI.png)

Zoom

![autoscaling_step1.png](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/autoscaling_step1.png)
* You can delete a Block Storage for VPC volume and all its snapshots. All snapshots must be in a stable or pending state. No snapshot can be actively restoring a volume.







 Create and work with snapshots 

You can create and manage your snapshots. For more information about creating a snapshot, viewing a list of snapshots, and restoring a volume from a snapshot, see the following items.



* To use the UI, log in to the [IBM Cloud console](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create&interface=ui).
* To use the [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create&interface=cli), download and install the following CLI plug-ins. For more information, see the [CLI reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).
* To use the [API](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create&interface=api), set up the [VPC API](https://cloud.ibm.com/apidocs/vpc).
* To use [Terraform](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create&interface=terraform), download the Terraform CLI and configure the IBM Cloud Provider plug-in. For more information, see [Getting started with Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).
* [Create](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-createsnapshots-vpc-create) your snapshots.
* Storage performance: 0.25, 2, or 4 IOPS/GB



For planning and sizing information, see [IBM Spectrum Protect Plus Blueprints and Sizing Spreadsheet](https://www.ibm.com/support/pages/node/1119489).





 Storage for management 

One 1000 GB, 2 IOPS/GB endurance file storage that hosts the IBM Spectrum Protect Plus virtual machine and running on the same subnet as the backup storage.





 Networking 

Two portable private IP addresses.





 Licenses and fees 



* IBM Spectrum Protect Plus (10 to a maximum of 1000 VM licenses in increments of 10)
* IBM Spectrum Protect Plus license offered through the IBM Cloud for VMware Solutions console (number of VMs in packages of 10) or as BYOL









 Considerations when you delete IBM Spectrum Protect Plus 

Review the following considerations before you delete the IBM Spectrum Protect Plus service:



* Before you delete the service, you must remove any personal VMs from storage that are deployed with this service.
* Ensure that all the backup job configurations are removed along with active backup or restore operations.
* When you delete the service, the storage for the backup repository is deleted from the IBM Spectrum Protect Plus VM and the storage order is canceled, which deletes the backup repository data permanently.
* When you delete the service, the backup storage that is ordered for the service is deleted too. All the backups become inaccessible during service deletion.







 Related links 



* [IBM Spectrum Protect Plus Preventive Service Planning](https://www-01.ibm.com/support/docview.wss?uid=swg22012650)
* [Managing IBM Spectrum Protect Plus](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingspp)
* [IBM Spectrum Protect Plus documentation](https://www.ibm.com/docs/en/spp/10.1.5)
* [Opening a case for IBM Spectrum Protect Plus](https://www.ibm.com/mysupport/s/article/How-to-Open-a-Case)