vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To delete a volume, complete the following steps.



1. Go to the list of all Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Locate the volume that you want to delete and then click the overflow icon (...) to open a list of options.
3. From the options menu, click Delete.
4. Confirm the deletion.







 Automatically delete Block Storage for VPC data volumes 

By using the Auto Delete feature, you can specify that a Block Storage for VPC data volume is automatically deleted when you delete an instance to which it is attached.

You don't need to set automatic deletion for boot volumes. Boot volumes are created during instance creation and automatic deletion is enabled by default. When you delete the instance, the boot volume is also deleted.

To enable Auto Delete for an existing Block Storage for VPC data volume that is attached to an instance, follow these steps:



1. Locate the virtual server instance to which the data volume is attached. In the [IBM Cloud console)](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Under Attached Block Storage for VPC volumes, select a volume.
3. On the next page, click Auto Delete to enable.
4. Confirm your selection.



Alternatively, select a data volume from the list of Block Storage for VPC(Storage > Block storage volumes). On the volume details page, under Attached instances, click the Auto delete toggle to enable or disable automatic deletion.
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/containers?topic=containers-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)
Satellite Storage <br><br> * Provide an interface to initiate a change management operation, such as deleting storage configurations or removing a cluster from a storage configuration.<br> * Provide version updates for IBM-provided storage templates.<br><br><br> <br><br> * Use the tools to delete storage configurations and cluster assignments. Note that if you remove these configurations, the storage drivers are uninstalled in the assigned clusters. Your PVCs, PVs, and data are not deleted. However, you might not be able to access your data until storage drivers are re-installed and storage configurations are restored in your cluster.<br> * Apply IBM-provided storage template version updates to ensure compliance and support for installed storage drivers.<br><br><br> 
 Satellite-enabled services <br><br> * Review each service's documentation for additional responsibilities that IBM maintains. For example, with Red Hat OpenShift on IBM Cloud clusters, IBM provides patch version updates for the masters automatically and for the worker nodes that you initiate.<br><br><br> <br><br> * Review each service's documentation for additional responsibilities that you fulfill when you use these services.<br><br><br> 
 Satellite Connector Provide an interface to initiate change management activities, such as to delete connectors. Before you delete any connectors, save and back up all the endpoints you have created for the connector. 







 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access. For more information, see [Managing access for Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-iam).



Table 4. Responsibilities for identity and access management.

 Task IBM responsibilities Your responsibilities 

 Satellite Location <br><br> * Provide an interface to assign access control to locations via IAM.<br><br><br> <br><br> * Use the provided tools to [manage authentication, authorization, and access control policies](https://cloud.ibm.com/docs/satellite?topic=satellite-iam).<br><br><br>
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. Then, delete the PVC and re-create the PVC. 
 Failed to find the storage with storage id 12345. You want to create a PVC for an existing storage instance by using Kubernetes static provisioning, but the storage instance that you specified could not be found. Follow the instructions to provision existing [file storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storageexisting_file) or [block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageexisting_block) in your cluster and make sure to retrieve the correct information for your existing storage instance. Then, delete the PVC and re-create the PVC. 
 Storage type not provided, expected storage type is Endurance or Performance. You created a custom storage class and specified a storage type that is not supported. Update your custom storage class to specify Endurance or Performance as your storage type. To find examples for custom storage classes, see the sample custom storage classes for [file storage](https://cloud.ibm.com/docs/containers?topic=containers-file_storagefile_custom_storageclass) and [block storage](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_custom_storageclass).
Adding and deleting clusters 

You can increase or decrease the capacity of your deployment by adding clusters to or deleting clusters from an instance. VMware vCenter clusters are the building blocks of VMware Cloud Director provider virtual data centers (PVDCs) and are added to existing PVDCs or are added as part of a PVDC creation.



 Procedure to add clusters to VMware as a Service instances 



1. In the VMware Solutions console, click Resources > VMware as a Service from the left navigation pane.
2. In the VMware as a Service table, click the Cloud director sites tab, then click an instance name.
3. Click the Infrastructure tab.
4. On the Clusters tab, click Add cluster +.
5. On the Add cluster window, specify the settings for the new cluster.



1. Specify the cluster name.
2. Select the profile storage type.
3. Select the host profile.
4. Select the host quantity.



* For NFS only storage, select a minimum of 2.
* For vSAN™ storage, select a minimum of 6.



5. Click Next.



6. Specify the attached NFS storage settings.
7. Review the new cost, select the confirmation checkbox, and click Order to confirm.







 Before you delete clusters 

Workload virtual machines (VMs) are deployed in virtual data centers (VDCs) that logically exist in the scope of a PVDC. PVDCs physically consist of one or more VMware vCenter clusters. When the PVDC contains multiple clusters and one cluster is deleted, all VMs running in that cluster are migrated to other clusters in the same PVDC.

VMs deployed to a specific storage performance tier are only migrated to the same performance tier of storage in the remaining clusters. You must ensure that the remaining clusters have compatible storage performance layers of the deleted cluster. The remaining clusters must also have enough CPU and memory to contain the VMs of the deleted cluster.

If not enough CPU, RAM, or equivalent storage performance for the cluster exists, the delete operation does not succeed.
You can select Immediately for an immediate update, or schedule a time for the update to become active by choosing a date and time for the update. You can also specify any applicable notes for your device.
5. In the Computing instance section, you can select new vCPU and RAM for your device.
6. If you need extra storage, you can attach storage disks to your device. The type of storage disks that are available to you depend on the profile that you select.

For public virtual servers, if you are upgrading local storage and require more vCPU or RAM, you might lose your secondary disk. When you modify a virtual server profile that uses local storage, the profile is preset for you. You can't select profiles that aren't comparable.
7. Click Resize to confirm your order and apply the changes to your device.
Before you remove your storage configuration, remove the app pods and PVCs that are using your NetApp storage.



1. List your PVCs and note the name of the PVC and the corresponding PV that you want to remove.

oc get pvc
2. List all the pods that currently mount the PVC that you want to delete. If no pods are returned, you do not have any pods that currently use your PVC.

oc get pods --all-namespaces -o=jsonpath='{range .items[]}{"n"}{.metadata.name}{":t"}{range .spec.volumes[]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"

Example output

app sat-netapp-file-gold
3. If the pod is part of a deployment, delete the deployment.

oc delete deployment <deployment_name>
4. Verify that the pod or the deployment is removed.

oc get pods

oc get deployments
5. Delete the PVC.

oc delete pvc <pvc_name>
6. Delete the corresponding PV.

oc delete pv <pv_name>
7. [Remove your NetApp ONTAP-NAS storage configuration from your cluster](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-netapp-ontap-nasnetapp-nas-template-rm-cli-2104)





 Removing the NetApp ONTAP-NAS storage assignment and configuration from the CLI 

Use the CLI to remove a storage assignment and 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.
* 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 4. 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 Skylake and Cascade Lake bare metal configurations 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. You can order up to 10 disks for Dual CPU models and up to 8 disks for Quad CPU models.

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 selected the High performance with Intel Optane checkbox.





 Number of vSAN cache disks 

Review Number of vSAN cache disks.
* Nondisruptively create point-in-time recovery points,
* Revert volumes to previous points-in-time.



You must purchase some amount of snapshot space for your volume first so you can take snapshots of it. The snapshot space can be added during the initial order or afterward through the Volume Details page. Scheduled and manual snapshots share the snapshot space, so make sure you order enough Snapshot space. See the [Ordering Snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-ordering-snapshots) article for more details and guidance.



 Snapshot best practices 

Snapshot design depends on the customer’s environment. The following design considerations can help you to plan and implement Snapshot copies:



* Up to 50 snapshots can be created through a schedule and up to 50 manually on each volume.
* Don't over snap. Make sure that your scheduled snapshot frequency meets your RTO and RPO needs and your application business requirements by scheduling hourly, daily, or weekly snapshots.
* Snapshot AutoDelete can be used to control the growth of storage consumption.

The AutoDelete threshold is fixed at 95 percent.



Snapshots are not replacements for actual off-site Disaster Recovery replication or long-retention backup.





 Security 

All snapshots and replicas of encrypted File Storage for Classic are also encrypted by default. This feature can't be turned off on a volume basis. For more information about provider-managed encryption-at-rest, see [Securing your data](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-mng-data).





 How Snapshots affect the disk space 

Snapshot copies minimize disk consumption by preserving individual blocks rather than whole files. Snapshot copies use extra space only when files in the active file system are changed or deleted.

In the active file system, the changed blocks are rewritten to different locations on the disk or removed as active file blocks entirely. When files are changed or deleted, the original file blocks are preserved as part of one or more Snapshot copies.
You can choose the RAM size from 128 GB, 192 GB, 384 GB, 768 GB, and 1.5 TB.





 Number of bare metal servers 



* If you are planning to use NFS storage, you can order 3-51 servers.
* If you are planning to use vSAN™ storage, you can order 4-51 servers.
* All servers that you order have the same configuration.







 Storage 

Storage settings are based on your selection of the storage type.

For deployed instances, you can add NFS storage shares to an existing NFS or vSAN cluster. For more information, see [Adding NFS storage to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingnfs).



 NFS storage 

When you select NFS storage, you can add file-level shared storage for your instance where all shares use the same settings or you can specify different configuration settings for each file share. The number of file shares must be in the range 1 - 100.

Specify the following NFS options:



* 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 1. 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 virtual machine disk images for a hypervisor.
In addition, a console message with more details is displayed and you are notified by email. The message displays the expected capacity for all services that do not meet the requirements.

To install the service, you must increase the capacity in your cluster either by adding more VMware ESXi™ servers or by freeing up RAM, CPU, or disk space. After that, you can add the service or services again. To remove the existing service in the Capacity Validation Failed state, click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) next to it.

The following table provides the resource requirements for the services for which a capacity check is completed.



Table 2. Resources required for the services that the system checks for capacity requirements

 Service name Resource requirements 

 Caveonix RiskForesight CPU - 8 CPUs <br>RAM - 32 GB <br>Storage - 100 GB 
 F5 BIG-IP<br><br>[1] CPU - 4, 8, or 16 CPUs, depending on license and bandwidth chosen <br>RAM - 8, 16, or 32 GB, depending on license and bandwidth chosen 
 FortiGate Virtual Appliance CPU - 2, 4, 8, 16, or 32 CPUs, depending on deployment size chosen <br>RAM - 4, 6, or 12 GB, depending on deployment size chosen 
 Entrust CloudControl CPU - 4 CPUs <br>RAM - 16 GB <br>Storage - 186 GB VMDK 
 Juniper vSRX You must have enough available capacity to accommodate two VMs with the following requirements, on different hosts: <br>CPU - 6 CPUs <br>RAM - 16 GB <br>Storage - 18 GB <br>If you install Juniper vSRX on clusters with 25 Gb uplink speed, the following capacity requirements apply. <br>CPU - 10 CPUs <br>RAM - 16 GB <br>Storage - 18 GB 
 Red Hat OpenShift If you install Red Hat OpenShift with vSAN™ storage, the following capacity requirements apply.
Assign a drive letter to the LUN, and then click Next.
8. Enter the parameters to format the LUN.



* On a Windows® Server, only NTFS is supported.
* Set the allocation unit size to 64 K.
* Provide a label for your Storage volume.



9. Click Next.
10. Check the values for your volume, and then click Finish. On the Disk Management page, the volume now appears as Online.









 Verifying whether MPIO is configured correctly in Windows® Operating systems 

It's possible to attach Block Storage for Classic with only a single path, but it is important that connections are established on both paths to ensure no disruption of service. To verify whether Windows® MPIO is configured, you must first ensure that the MPIO Add-on is enabled and then, restart the server.

Zoom

![Roles_Features_0](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/BlockStorage//images/Roles_Features_0.svg)

Figure 12. Multipath I/O is shown as checked.

After the restart is complete, take the following steps to view all of the active paths.



1. On the desktop, click Start.
2. In the Start Search field, type diskmgmt.msc.
3. In the Programs list, click diskmgmt.
4. Right-click each disk for which you want to verify the multiple paths and then click Properties.
5. On the MPIO tab, in the Select the MPIO policy list, click all the paths that are active.

Zoom

![Windows® MPIO properties.](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/BlockStorage//images/DeviceDetails_0.svg)

Figure 13.