vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* If you select NFS storage and want to add and configure file shares individually, toggle the Configure shares individually switch on, then click Add shared storage and select the Size (GB) and Performance for each file share. You must select at least one file share.
* If you select vSAN storage, specify the following values:



* Size for the vSAN capacity disks
* Number of vSAN capacity disks
* Size for vSAN cache disks
* Number of vSAN cache disks
* vSAN license edition





If you want more storage, check the High performance with Intel Optane box.

By default, the Enable vSAN deduplication and compression box is selected. If you do not want to enable vSAN deduplication and compression, clear the checkbox.



6. For gateway clusters, complete the following configuration.



1. For data center location, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) and select the geography, data center, and pod to host the cluster.
2. Specify the cluster name.
3. Select the CPU model, RAM size, and the number of bare metal servers.



7. For network interface settings, enter the hostname prefix, and then select the uplink speed and network type.
8. On the Summary pane, verify the cluster configuration before you add the cluster.



1. Review the settings for the cluster.
2. Review the estimated price of the cluster. Click Pricing details to generate a PDF summary. To save or print your order summary, click Print or Download on the upper right of the PDF window.
3. Click the link or links of the terms that apply to your order, and confirm that you agree with these terms before you add the cluster.
4. Click Create.









 Results after you add clusters to Cyber Recovery instances 



1.
Automate the creation of PVC, PV, and storage device: You want to automatically provision and deprovision storage without manual intervention from a cluster admin.
3. Create and delete storage often: You have an app or set up a continuous delivery pipeline that creates and removes persistent storage regularly. Persistent storage that is dynamically provisioned with a non-retaining storage class can be removed by deleting the PVC.







 Static provisioning 

If you have an existing persistent storage device in your IBM Cloud infrastructure account, you can use static provisioning to make the storage instance available to your cluster.

Static provisioning is a feature that is native to Kubernetes and that allows cluster administrators to make existing storage devices available to a cluster. As a cluster administrator, you must know the details of the storage device, its supported configurations, and mount options.

To make existing storage available to a cluster user, you must manually create the storage device, a PV, and a PVC.

The following image shows how to statically provision file storage in a cluster. This sample flow works similar with other storage types, such as block storage.

Zoom

![Sample flow to statically provision file storage in a cluster, as described in the following list.](https://cloud.ibm.com/docs-content/v1/content/bce0f0917a9eea684d1b4b704ac6343a1f65f446/openshift/images/cs_storage_static-01.svg)

Figure 1. Sample flow to statically provision file storage in a cluster



1. The cluster admin gathers all the details about the existing storage device and creates a persistent volume (PV) in the cluster.
2. Based on the storage details in the PV, the storage plug-in connects the PV with the storage device in your IBM Cloud infrastructure account.
3. The cluster admin or a developer creates a PVC. Because the PV and the storage device already exist, no storage class is specified in the PVC.
4. After the PVC is created, the storage plug-in tries to match the PVC to an existing PV.
By creating the PVC, you exceed the maximum number of storage instances. For more information about the maximum number of volumes that you can create and how to retrieve the number of volumes in your account, see the documentation for [file](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managinglimits) and [block](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-managingstoragelimits) storage. To create a PVC, choose from the following options. - Remove any unused PVCs.<br><br><br><br> * Ask the IBM Cloud account owner to increase your storage quota by [opening a support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).<br><br><br> 
 `Unable to find the exact ItemPriceIds(type size iops) for the specified storageFailed to place storage order with the storage provider 
 Failed to find the datacenter name in configuration file. The data center that you specified in your PVC does not exist. Run ibmcloud ks locations to list available data centers. Correct the data center in your PVC and re-create the PVC. 
 Failed to place storage order with the storage providerStorage with the order ID 12345 could not be created after retrying for xx seconds.Failed to do subnet authorizations for the storage 12345.Storage 12345 has ongoing active transactions and could not be completed after retrying for xx seconds. The storage size, IOPS, and storage type might be incompatible with the storage class that you chose, or the IBM Cloud infrastructure API endpoint is currently unavailable. Review [Deciding on the file storage configuration](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_predefined_storageclass) and [Deciding on the block storage configuration](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_predefined_storageclass) to find supported storage sizes and IOPS for the storage class and storage type that you want to use.
* [Deleting a private repository and any associated charts](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_helm_chartsregistry_helm_charts_repo_remove)







 Cleaning up your namespaces 

[Cleaning up your namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionregistry_retention)



* [Planning retention](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_plan)
* [Clean up your namespaces to keep a set number of images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_images)
* [Set a retention policy for your namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_policy_set)
* [Update a retention policy to keep all your images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_policy_keep)
* [Clean up your namespaces by deleting untagged images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_images_untagged)







 Managing quota limits for storage and pull traffic 

[Managing quota limits for storage and pull traffic](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota)



* [Setting quota limits for storing and pulling images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_set)
* [Reviewing quota limits and usage](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_get)
* [Staying within quota limits](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_quotaregistry_quota_freeup)







 Managing user access
Right-click the left panel for the disk, and choose Initialize Disk.
2. In the Initialize Disk dialog box, select a partition style, and choose OK.



5. Right-click the right panel for the disk, and choose New Simple Volume.
6. In the New Simple Volume Wizard, choose Next.
7. If you want to change the default maximum value, specify the size in MB in the Simple volume size field, and then choose Next.
8. Specify a preferred drive letter, if necessary, and then choose Next.
9. Specify a Volume Label and adjust the default settings as necessary, and then choose Next.
10. Review your settings, and then choose Finish to apply the modifications and close the New Simple Volume wizard.







 Setting up your volume for use with Windows PowerShell 



1. Log in to your Windows instance by using Remote Desktop. For more information, see [Connecting to Windows instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_windows).
2. On the taskbar, open the Start menu, and choose Windows PowerShell.
3. Use the following commands.



Stop-Service -Name ShellHWDetection
Get-Disk | Where PartitionStyle -eq 'raw' | Initialize-Disk -PartitionStyle MBR -PassThru | New-Partition -AssignDriveLetter -UseMaximumSize | Format-Volume -FileSystem NTFS -NewFileSystemLabel "Volume Label" -Confirm:$false
Start-Service -Name ShellHWDetection

The script performs the following actions.



* Stops the ShellHWDetection service.
* Lists the disks where the partition style is raw.
* Creates a partition that spans the maximum size that the disk and partition type can support.
* Assigns an available drive letter.
* Formats the file system as NTFS with the specified file system label.
* Starts the ShellHWDetection service again.
* UI
* CLI
* Terraform







 Managing Snapshots 

Snapshots are a feature of IBM Cloud® Block Storage for Classic. A snapshot represents a volume's contents at a particular point in time. With snapshots, you can protect your data with no performance impact and minimal consumption of space. Learn more about how to manage snapshots by reading the following instructions.



 Adding a Snapshot schedule in the UI 

You decide how often and when you want to create a point in time reference of your storage volume with Snapshot schedules. You can have a maximum of 50 snapshots per storage volume. Schedules are managed through the Storage > Block Storage for Classic tab of the [IBM Cloud® console](https://cloud.ibm.com/classic-gen1).

Before you can set up your initial schedule, you must first purchase snapshot space if you didn't purchase it during the initial provisioning of the storage volume. For more information, see [Ordering Snapshots](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingsnapshots).

Snapshots schedules can be set up for hourly, daily, and weekly intervals, each with a distinct retention cycle. The maximum limit of snapshots is 50 per storage volume, which can be a mix of hourly, daily, and weekly schedules, and manual snapshots.



1. Click your storage volume, click Actions, and click Edit Snapshot Schedule.
2. In the Snapshot Schedule window, you can select from three different snapshot frequencies. Use any combination of the three to create a comprehensive snapshot schedule.



* Hourly



* Specify the minute each hour that a snapshot is to be taken. The default is the current minute.
* Specify the number of hourly snapshots to be retained before the oldest is discarded.



* Daily



* Specify the hour and minute that a snapshot is to be taken. The default is the current hour and minute.
* Select the number of hourly snapshots to be retained before the oldest is discarded.



* Weekly
For more information about configuring these settings in the vSphere Web Client, see [Set storage DRS runtime rules in the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.resmgmt.doc/GUID-AD2D13CE-539B-48C3-BBC9-E55A834874F0.html).





 Storage I/O Control for NFS v3 

When SIOC (Storage I/O Control) is enabled in the environment, it changes the device queue length for the single VM. The change to the device queue length reduces the storage array queue for all VMs to an equal share and throttle of the storage queue. SIOC engages only if resources are constrained and the storage I/O latency is higher than a defined threshold.

In order for SIOC to determine when a storage device is congested or constrained, it requires a defined threshold. The congestion threshold latency is different for different storage types. This design recommends and implements a threshold latency of 10 milliseconds.

You can limit individual virtual disks for individual VMs or grant them different shares with SIOC. By limiting disks and granting different shares, you can match and align the environment to the workload with the acquired file storage volume IOPS number. The limit is set by IOPS and it is possible to set a different weight or shares.

Virtual disks shares set to High (2000 shares) receive twice as much I/O as a disk set to Normal (1000 shares) and four times as much as one set to Low (500 shares). Normal is the default value for all the VMs, so you need to adjust the Normal settings for the VMs that require it.





 Additional storage for NFS v3 

When the need arises to add more storage to the environment due to insufficient space or high latency, you can order another NFS share from the console. After the share is ordered, attach the export to the vSphere ESXi hosts in the cluster and place it into the storage cluster.
* Configure shares individually - Toggle this switch on to specify different configuration settings for each file share.
* Number of shares - When you 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 that use different configuration settings.



Choose performance level options according to your needs.



Table 3. NFS performance level options

 Option Details 

 0.25 IOPS/GB This option is designed for workloads that are not used often. For example, 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. For example, hosting small databases, backing up web applications, or virtual machine 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. For example, transactional databases. 
 10 IOPS/GB This option is designed for the most demanding workload types, such as analytics. For example, 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 

vSAN is available for the Cascade Lake bare metal configuration only.



 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.

For VMware vSphere 7, order up to 10 disks for Dual CPU models and order up to eight disks for Quad CPU models.





 Size for vSAN cache disks 

Review the Size for vSAN cache disks value.





 Number of vSAN cache disks 

Review the Number of vSAN cache disks value.





 Enable vSAN deduplication and compression
The modification to the capacity does not affect the integrity of the data that is stored in the vault. For more information, see [expanding vault capacity](https://cloud.ibm.com/docs/Backup?topic=Backup-expandcapacityexpandcapacity).





 What happens when the IBM Cloud Backup for Classic capacity is exceeded? 

You can still save and retrieve your backups even if you reached the limit of the capacity that you purchased previously. However, you are going to receive an extra charge for every additional GB that was used in the next billing statement.





 How can I set up notifications in the Cloud Backup Portal that can alert me if a backup fails? 

Notifications can be set up on the Advanced tab. Follow the instructions that you can find in Quick Links in the Portal.





 When we use the BMR plug-in, can we move from a single disk to a raid array? 

Yes, that works. However, you need to select a large capacity device due to the size decrease that the raid array causes.





 When we use the BMR plug-in, what happens when the image is restored to a larger disk than the original volume? 

If you restore the image to a larger disk than the original volume, the leftover space is deallocated. So for example - when you have a 500-GB drive and restore its data to a 1-TB disk, you end up with 500 GB of deallocated disk space. With windows 2008, you can use the built-in disk utility to grow the primary partition. However, Windows 2003 does not have a similar built-in capability, so you must allocate the space another way.





 Can BMR be used for regular backup? 

BMR backup isn't a disk image, but a system volume image backup system. The system isn't intended to be used for regular backups, but along with them.





 Can BMR be used for database backups? 

Database backups must be made separately with the normal IBM Cloud Backup for Classic methods. BMR doesn't replace the need for SQL or Oracle plug-ins.
* [Remove the local file storage configuration from the console](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filesat-storage-rm-local-file-ui)
* [Remove the local file storage configuration from the command line](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filerm-local-file-temp-cli)



* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-parameter-reference)



* [4.8 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-4.8-parameters)
* [4.9 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-4.9-parameters)
* [4.10 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-4.10-parameters)
* [4.11 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-4.11-parameters)
* [4.12 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-volume-file-4.12-parameters)



* [Storage class reference for local file storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filelocal-file-sc-reference)
* [Getting help and support for local file storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filesat-local-file-support)
Diagnosing and resolving high storage usage 

This document describes ways to diagnose and, if necessary, reduce the storage usage on your Db2 Warehouse on Cloud system.



 Check storage usage 

Run the following SQL query as an admin user to check the current storage usage on every Db2 partition in your Db2 Warehouse on Cloud instance:

db2 "SELECT DBPARTITIONNUM , ROUND((SUM(FS_USED_SIZE) / SUM(FS_TOTAL_SIZE)::DECFLOAT)* 100,2) AS UTILIZATION_PERCENT, ROUND(( SUM(FS_TOTAL_SIZE) - SUM(FS_USED_SIZE)::DECFLOAT) / 1073741824,2) AS FREE_GB FROM TABLE(ADMIN_GET_STORAGE_PATHS(NULL,-2)) AS T WHERE STORAGE_GROUP_NAME NOT LIKE '%TEMP%' GROUP BY DBPARTITIONNUM ,CASE WHEN DBPARTITIONNUM = 0 THEN 'NP' ELSE 'P' END"

There are two possible causes for high storage usage:



* The storage attached to your system is reaching maximum capacity.
* There is empty space on the disks that must be reclaimed.







 Diagnosing and resolving 

If the output from the previous SQL query indicates that storage usage on your instance is high, the following steps will help to diagnose and resolve this scenario:



1. Check if the instance has reclaimable space by running the following SQL query as an admin user:
* [Preparing your existing storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storageexisting-file-1)
* [Creating a persistent volume and a persistent volume claim](https://cloud.ibm.com/docs/containers?topic=containers-file_storageexisting-file-2)



* [Using File Storage for Classic in a stateful set](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_statefulset)



* [Creating the PVC when you create a stateful set by using dynamic provisioning](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_dynamic_statefulset)
* [Static provisioning: Using an existing PVC with your stateful set](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_static_statefulset)



* [Changing the size and IOPS of your existing storage device](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_change_storage_configuration)
* [Changing the default NFS version](https://cloud.ibm.com/docs/containers?topic=containers-file_storagenfs_version)



* [Creating a customized storage class with a specific NFS version](https://cloud.ibm.com/docs/containers?topic=containers-file_storagecustom-sc-nfs-creat)
* [Changing your existing PV to use a different NFS version](https://cloud.ibm.com/docs/containers?topic=containers-file_storagechanging-pv-nfs)



* [Scaling down the default File Storage for Classic plug-in](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_scaledown_plugin)
* [Backing up and restoring data](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_backup_restore)
Note that if you remove the storage configuration, the local storage operator resources and the sat-local-file-gold storage class is then uninstalled from all assigned clusters. Your PVCs, PVs and data are not removed. However, you might not be able to access your data until you re-install the driver in your cluster again.



 Remove the local file storage configuration from the console 

Use the console to remove a 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.







 Remove the local file storage configuration from the command line 



1. List the resources in the local-storage namespace. When you delete your storage assignment, these resources are removed.

oc get all -n local-storage

Example output

NAME READY STATUS RESTARTS AGE
pod/local-disk-local-diskmaker-clvg6 1/1 Running 0 29h
pod/local-disk-local-diskmaker-kqddq 1/1 Running 0 29h
pod/local-disk-local-diskmaker-p6z9q 1/1 Running 0 29h
pod/local-disk-local-provisioner-dw5g7 1/1 Running 0 29h
pod/local-disk-local-provisioner-hxd9n 1/1 Running 0 29h
pod/local-disk-local-provisioner-tfg95 1/1 Running 0 29h
pod/local-storage-operator-df4994656-7826l 1/1 Running 0 29h

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/local-storage-operator ClusterIP 172.21.147.17 <none> 60000/TCP 29h

NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/local-disk-local-diskmaker 3 3 3 3 3 <none> 29h
daemonset.apps/local-disk-local-provisioner 3 3 3 3 3 <none> 29h