vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [IBM Cloud® Object Storage](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-storagestorage-cos)
* [Related controls in IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-storagerelated-controls)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-storagenext-steps)



[Storage for Satellite reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-storagesatellite-architecture-storage)



* [Storage in IBM Cloud](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-storagesatellite-architecture-storage-ibm-cloud)



* [About Object Storage](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-storagesatellite-architecture-storage-ibm-cloud-cos)



* [Storage in Satellite location](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-storagesatellite-architecture-storage-satellite-location)
* [Related controls in IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-storagerelated-controls)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-storagenext-steps)







 Logging and monitoring
Mount and reattach your storage volume to the host.



* [Mount iSCSI LUNs on Linux® - RHEL6 and CentOS6](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinux).
* [Mount iSCSI LUN on Red Hat Enterprise Linux® 8](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingRHEL8).
* [Mount iSCSI LUNs on CloudLinux 6.10](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingCloudLinux).
* [Mount iSCSI LUN on CloudLinux 8](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingCloudLin8).
* [Mount iSCSI LUN on Ubuntu 20](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingUbu20).
* [Mount iSCSI LUN on Debian 10](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingdebian10).
* [Mapping LUNS on Microsoft® Windows®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingWindows).





Restoring a volume results in deleting all snapshots that were taken after the snapshot that was used for the restore.





 Restoring storage volume to a specific point in time by using a snapshot from the SLCLI 

You might need to take your storage volume back to a specific point in time because of user-error or data corruption.



1. Unmount your volume. You must ensure that the host is not trying to connect to the volume during the restore.



* [Unmounting Block Storage for Classic volumes on Linux®](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-mountingLinuxunmountingLin)
Minimum required permissions 

IBM Cloud IAM Viewer 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 retrieve storage classes from. To list Satellite storage configurations, run ibmcloud sat storage config ls.

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





 Example 

ibmcloud sat storage config sc ls --config ocs-config







 ibmcloud sat storage template get 

Get the details of a Satellite storage template.

ibmcloud sat storage template get --name NAME --version VERSION



 Minimum required permissions 

IBM Cloud IAM Viewer 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 

--name NAME
: Required. The name of the storage template that you want to retrieve.

--version VERSION
: Required. The version of the storage template.

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





 Example 

ibmcloud sat storage template get --name ocs --version 4.3







 ibmcloud sat storage template ls 

List your Satellite storage templates.

ibmcloud sat storage template ls [-q]

You can run ibmcloud sat storage templates as an alias of the ibmcloud sat storage template ls command.



 Minimum required permissions 

IBM Cloud IAM Viewer 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 

-q
Show more





 Specifying the zone for multizone clusters 

If you want to create your File Storage for Classic in a specific zone, you can specify the zone and region in a customized storage class.

Use the customized storage class if you want to [statically provision File Storage for Classic](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storageexisting_file) in a specific zone. In all other cases, [specify the zone directly in your PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storageadd_file).

When you create the customized storage class, specify the same region and zone that your cluster and worker nodes are in. To get the region of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID> and look for the region prefix in the Master URL, such as eu-de in https://c2.eu-de.containers.cloud.ibm.com:11111. To get the zone of your worker node, run ibmcloud oc worker ls --cluster <cluster_name_or_ID>.

Example for Endurance File Storage for Classic.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-file-silver-mycustom-storageclass
labels:
kubernetes.io/cluster-service: "true"
provisioner: ibm.io/ibmc-file
parameters:
zone: "dal12"
region: "us-south"
type: "Endurance"
iopsPerGB: "4"
sizeRange: "[20-12000]Gi"
reclaimPolicy: "Delete"
classVersion: "2"
reclaimPolicy: Delete
volumeBindingMode: Immediate
Show more

Example for Performance File Storage for Classic.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-file-performance-storageclass
labels:
Get-SmbServerConfiguration | Select EnableSMB2Protocol
Set-SmbServerConfiguration -EnableSMB2Protocol $true -Force
New-SmbMapping -LocalPath 'Z:' -RemotePath $path -UserName $shareuser -Password $sharepassword -Persistent $true





 Configure storage 

The Microsoft SQL on VPC deployment patterns leverage Microsoft Storage Spaces. Storage Spaces is a technology in Windows Server that is conceptually similar to RAID, and is implemented in the operating system. Storage spaces can be used to group data volumes together into a storage pool and then the capacity from the pool is then used to create Storage spaces (virtual disks). A storage space appears to the Windows operating system as a regular drive from which you can create formatted volumes.



 Configure storage spaces 

From the IBM Cloud console, capture the storage volumes information for the SQL server. For example:

sqldb01-data: 0787-ff88b86a-1e29-4f0d-8a69-67b4deda3d5c-lpcn2
sqldb01-log: 0787-1d41b85e-4e8a-499e-b889-13b96db5251c-2w2n2

The following PowerShell command is used to capture the Windows OS view of the SerialNumber for use in subsequent PowerShell commands; Get-StoragePool -IsPrimordial $true | Get-PhysicalDisk -CanPool $True. As can be seen from the following example, the SerialNumbers can be captured:

Number FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size
------ ------------ ------------ --------- ------- ----------------- ------------ ----- ----
oc cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath>

Copy data from a pod in your cluster to your local machine.

oc cp <namespace>/<pod>:<pod_filepath>/<filename></var> <local_filepath>/<filename>

Copy data from your local machine to a specific container that runs in a pod in your cluster.

oc cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath> -c <container>







 Storage class reference 

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.

Bronze

Silver

Gold



Bronze

 Characteristics Setting 

 Name ibmc-file-bronze <br>ibmc-file-retain-bronze <br>ibmc-file-bronze-gid 
 Type Endurance storage 
 File system NFS 
 IOPS per gigabyte 2 
 Size range in gigabytes 20-12000 Gi 
 Hard disk SSD 
 Reclaim policy ibmc-file-bronze: Delete <br>ibmc-file-retain-bronze: Retain <br>ibmc-file-bronze-gid: Delete 
 Supplemental group ID The supplemental group ID 65531 is automatically set when you use the ibmc-file-bronze-gid storage class to allow non-root users access to your file storage instance. For more information about how to use this storage class or set custom group IDs, see [File storage: Adding non-root user access to persistent storage fails](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_storage_nonroot). 
 Billing Hourly 
 Pricing [Pricing information](https://cloud.ibm.com/cloud-storage/file/order) 







 Sample customized storage classes 

You can create a customized storage class and use the storage class in your PVC.
More commands for managing Key Protect resources could support best practices.



Table 5. Commands for managing other resources

 Command Status v0.8 Description 

 [kp keys](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-keys) List the keys that are available in your Key Protect instance 
 [kp key-rings](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-key-rings) Lists the key rings associated with the kp instance 
 [kp region-set](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-region-set) Target a different regional endpoint 
 [kp registrations](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-registrations) List associations between root keys and other cloud resources
"[3000-3999]Gi:[200-48000]"
"[4000-7999]Gi:[300-48000]"
"[8000-9999]Gi:[500-48000]"
"[10000-12000]Gi:[1000-48000]"
type: "Performance"
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
Show more





 Specifying the zone and region 

If you want to create your block storage in a specific zone, you can specify the zone and region in a customized storage class.

Use the customized storage class if you use the IBM Cloud Block Storage plug-in version 1.0.0 or if you want to [statically provision block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageexisting_block) in a specific zone. In all other cases, [specify the zone directly in your PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageadd_block).

The following .yaml file customizes a storage class that is based on the ibm-block-silver non-retaining storage class: the type is "Endurance", the iopsPerGB is 4, the sizeRange is "[20-12000]Gi", and the reclaimPolicy is set to "Delete". The zone is specified as dal12. To use a different storage class as your base, see the [storage class reference](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_storageclass_reference).

Create the storage class in the same region and zone as your cluster and worker nodes. To get the region of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID> and look for the region prefix in the Master URL, such as eu-de in https://c2.eu-de.containers.cloud.ibm.com:11111.
A visual representation of your data members and their resource allocation is available on the Resources tab of your deployment's Manage page.

![The Scale Resources Panel in Resources](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/images/scaling-update.png){: caption="Figure 1. The Scale Resources Panel in Resources" caption-side="bottom"}

Adjust the slider to increase or decrease the resources that are allocated to your service. The slider controls how much memory or disk is allocated per member. The UI currently uses a coarser-grained resolution of 8 GB increments for disk and 1 GB increments for memory. The UI shows the total allocated memory or disk for the position of the slider. Click Scale to trigger the scaling operations and return to the dashboard overview.





 Resources and Scaling in the CLI 

[IBM Cloud CLI cloud databases plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference) supports viewing and scaling the resources on your deployment. Use the command cdb deployment-groups to see current resource information for your service, including which resource groups are adjustable. To scale any of the available resource groups, use cdb deployment-groups-set command.

For example, the command to view the resource groups for a deployment named "example-deployment":
ibmcloud cdb deployment-groups example-deployment

This produces the output:

Group member
Count 3

+ Memory
| Allocation 3072mb
| Allocation per member 1024mb
| Minimum 3072mb
| Step Size 384mb
| Adjustable true

+ CPU
| Allocation 0
| Allocation per member 0
| Minimum 9
| Step Size 3
| Adjustable true

+ Disk
| Allocation 61440mb
| Allocation per member 20480mb
| Minimum 61440mb
| Step Size 3072mb
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-custom-xfs
labels:
addonmanager.kubernetes.io/mode: Reconcile
provisioner: ibm.io/ibmc-block
parameters:
type: "Endurance"
iopsPerGB: "4"
sizeRange: "[20-12000]Gi"
fsType: "xfs"
reclaimPolicy: "Delete"

Example for Performance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-custom-xfs
labels:
addonmanager.kubernetes.io/mode: Reconcile
provisioner: ibm.io/ibmc-block
parameters:
classVersion: "2"
type: "Performance"
sizeIOPSRange: |-
[20-39]Gi:[100-1000]
[40-79]Gi:[100-2000]
[80-99]Gi:[100-4000]
[100-499]Gi:[100-6000]
[500-999]Gi:[100-10000]
[1000-1999]Gi:[100-20000]
[2000-2999]Gi:[200-40000]
[3000-3999]Gi:[200-48000]
[4000-7999]Gi:[300-48000]
[8000-9999]Gi:[500-48000]
[10000-12000]Gi:[1000-48000]
fsType: "xfs"
reclaimPolicy: "Delete"
Show more







 Removing persistent storage from a cluster
* [Preparing your existing storage](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storageexisting-file-1)
* [Creating a persistent volume and a persistent volume claim](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storageexisting-file-2)



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



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



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



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



* [Backing up and restoring data](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storagefile_backup_restore)
Adding NFS storage to Cyber Recovery instances 

You can expand the capacity of your Cyber Recovery instance according to your business needs by adding Network File System (NFS) storage.



 Before you add NFS storage to Cyber Recovery instances 



* Do not add NFS storage from the VMware vSphere® Web Client. The changes that you make on the vSphere Web Client are not synchronized with the IBM Cloud® for VMware Solutions console.
* IBM® does not manage NFS file shares that you manually add to an instance.
* You can add or remove NFS storage shares to or from an existing NFS or vSAN™ cluster.
* If you mount IBM Cloud Endurance NFS storage to your cluster, consider the following steps:



* Ping the NFS server for the storage and note the subnet for the server IP address.
* Review the VMKernel adapters for the hosts that use storage and make note of the subnet for vmk3. Use the [file storage list](https://cloud.ibm.com/cloud-storage/file) to authorize the vmk3 subnet to access the NFS data store.
* Review the static routes defined on the hosts with the esxcli network ip route ipv4 list command. A static route must be displayed for the NFS server IP subnet to the gateway for the vmk3 subnet listed in the previous step.









 Procedure to add NFS storage to Cyber Recovery instances 



1. From the VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, click the instance for which you want to expand capacity.
3. Click the Infrastructure tab.
4. In the Clusters table, click the cluster to which you want to add NFS storage.
5. In the Storage section, click Add.
6. In the Add NFS storage side panel, complete the storage configuration.



* To add and configure the same settings to all file shares, specify the Number of shares, Size (GB), and Performance.
[Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).

When you run the oc cp command, if you don't specify a container with -c, the command uses the first available container in the pod.

Copy data from your local machine to a pod in your cluster.

oc cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath>

Copy data from a pod in your cluster to your local machine.

oc cp <namespace>/<pod>:<pod_filepath>/<filename> <local_filepath>/<filename>

Copy data from your local machine to a specific container that runs in a pod in your cluster.

oc cp <local_filepath>/<filename> <namespace>/<pod>:<pod_filepath> -c <container>







 Storage class reference 

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.



 Bronze 

Name
: ibmc-block-bronze
: ibmc-block-retain-bronze

Type
: Endurance storage

File system
: ext4

IOPS per gigabyte
: 2

Size range in gigabytes
: 20-12000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-bronze: Delete
: ibmc-block-retain-bronze: Retain





 Silver 

Name
: ibmc-block-silver
: ibmc-block-retain-silver

Type
: Endurance storage

File system
: ext4

IOPS per gigabyte
: 4

Size range in gigabytes
: 20-12000 Gi

Hard disk
: SSD

Reclaim policy
: ibmc-block-silver: Delete
10. Click Complete to assign your storage configuration.







 Creating a configuration in the CLI 



1. Log in to the IBM Cloud CLI.

ibmcloud login
2. List your Satellite locations and note the Managed from column.

ibmcloud sat location ls
3. Target the Managed from region of your Satellite location. For example, for wdc target us-east. For more information, see [Satellite regions](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).

ibmcloud target -r us-east
4. If you use a resource group other than default, target it.

ibmcloud target -g <resource-group>
5. Copy one of the following example command for the template version that you want to use. For more information about the command, see ibmcloud sat storage config create in the [command reference](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-storage-config-create).

Example command to create a version 21.04 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-ontap-san --template-version 21.04 --param "managementLIF=MANAGEMENTLIF" --param "dataLIF=DATALIF" --param "svm=SVM" --param "username=USERNAME" --param "password=PASSWORD" --param "limitVolumeSize=LIMITVOLUMESIZE" --param "limitAggregateUsage=LIMITAGGREGATEUSAGE"

Example command to create a version 22.04 configuration.
* [Removing the local block storage configuration from the command line](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-blockrm-local-block-temp-cli)



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



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



* [Storage class reference for local block storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-blocklocal-block-sc-ref)
* [Getting help and support for local block storage](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-blocksat-local-block-support)



[Local Storage Operator - File](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-local-volume-filestorage-local-volume-file)
sat-local-file-gold ext4 or xfs Retain 







 NetApp ONTAP-NAS 21.04 

Review the Satellite storage classes for NetApp ONTAP-NAS. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.



Table 7. NetApp ONTAP-NAS storage class reference.

 Storage class name Type File system IOPs Encryption Reclaim policy 

 sat-netapp-file-goldDefault ONTAP-NAS NFS no QoS limits Encryption disabled. Delete 
 sat-netapp-file-gold-encrypted ONTAP-NAS NFS no QoS limits Encryption enabled. Delete 
 sat-netapp-file-silver ONTAP-NAS NFS User defined QoS limit. Encryption disabled. Delete 
 sat-netapp-file-silver-encrypted ONTAP-NAS NFS User defined QoS limit. Encryption enabled. Delete 
 sat-netapp-file-bronze ONTAP-NAS NFS User-defined QoS limit. Encryption disabled. Delete 
 sat-netapp-file-bronze-encrypted ONTAP-NAS NFS User-defined QoS limit. Encryption enabled. Delete 







 NetApp ONTAP-NAS 20.07 

Review the Satellite storage classes for NetApp ONTAP-NAS. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.



Table 8. NetApp ONTAP-NAS storage class reference.

 Storage class name Type File system Reclaim policy 

 sat-netapp-file-goldDefault ONTAP-NAS File Delete 
 sat-netapp-file-silver ONTAP-NAS File Delete 
 sat-netapp-file-bronze ONTAP-NAS File Delete 







 NetApp ONTAP-SAN 21.04 

Review the Satellite storage classes for NetApp ONTAP-SAN. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.



Table 9.