vania-janet/multiturn-rag-retrieval-data huggingface dataset:
resource "ibm_storage_block" "test1" {
type = "Endurance"
datacenter = "dal05"
capacity = 20
iops = 0.25
os_format_type = "Linux"

 Optional fields
allowed_virtual_guest_ids = [ 27699397 ]
allowed_ip_addresses = ["10.40.98.193", "10.40.98.200"]
snapshot_capacity = 10
hourly_billing = true

 Optional fields for snapshot
snapshot_schedule {
schedule_type = "WEEKLY"
retention_count = 20
minute = 20
hour = 13
day_of_week = "SUNDAY"
enable = true
}
snapshot_schedule {
schedule_type = "HOURLY"
retention_count = 20
minute = 2
enable = true
}
}

If you want to update the schedule, change these values and apply them to your resources. If you want to delete the schedule, remove its details from the ibm_storage_block resource definition, and apply your changes.





 Taking a manual Snapshot in the UI 

Manual snapshots can be taken at various points during an application upgrade or maintenance. You can also take snapshots across multiple servers that were temporarily deactivated at the application level.

The maximum limit of snapshots per storage volume is 50.



1. Click your storage volume.
2. Click Actions.
3. Click Take Manual Snapshot.



The snapshot is taken and displayed in the Snapshots section of the Block Storage for Classic Detail page. Its schedule appears Manual.





 Taking a manual Snapshot from the SLCLI 

You can use the following command to create a snapshot from the SLCLI.

 slcli block snapshot-create --help
Usage: slcli block snapshot-create [OPTIONS] VOLUME_ID

Options:
-n, --notes TEXT Notes to set on the new snapshot
-h, --help Show this message and exit.
You can indicate capacity in GB increments up to 16,000 GB capacity, depending on your volume profile. For more information, see [Increasing Block Storage for VPC volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes).





 Can I increase capacity of a boot volume? 

Boot volume capacity can be increased during instance provisioning or later, by directly modifying the boot volume. This feature applies to instances that are created from stock or custom images. You can also specify a larger boot volume capacity when you create an instance template. The boot volume can't be unattached from an instance (that is, stored as stand-alone data volume). For more information, see [Increasing boot volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes).





 Can I change boot volume capacity for an existing instance? 

Yes, boot volume capacity can be increased for an existing instance. However, you increase capacity on the storage side. That is, by modifying the boot volume details. For example, in the UI, you'd select a boot volume from the list of Block Storage for VPC volumes and then resize the volume from the volume details page. For more information, see [Increase boot volume capacity from the list of Block Storage for VPC volumes in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=uiresize-boot-vol-list-ui). You can also use the [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=cliexpand-existing-boot-vol-cli) or the [API](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=apiexpand-existing-boot-vol-api).





 How many volumes can I provision on my account? 

You can provision up to 300 Block Storage for VPC volumes per account in a region.
Adding and deleting hosts 

You can increase or decrease the capacity of your deployment by adding or deleting hosts to and from a cluster.



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 a cluster name to expand its details.
5.  Click Edit host quantity.
6.  In the Edit host quantity window, increase or decrease the current host quantity.
7.  Review the new cost, select the confirmation checkbox, and click Change to confirm.





  Related links 



*  [Adding virtual data centers](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-adding)
*  [Viewing and deleting virtual data centers](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-view-delete)
*  [Viewing VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-viewing)
Autoscaling configurations based on memory usage are currently not available.

Disk - Disk autoscaling can scale when either disk usage reaches a certain threshold, Disk I/O utilization reach a certain threshold, or both. (The "or" in the UI operates as an inclusive or, |, v.) The amount of IOPS available to your deployment increases with disk size at a ratio of 10 IOPS for each GB.

The resource numbers refer to each database member in a deployment. For example, there are three data members in a MySQL deployment and if the deployment is scaled with 10 GB of disk and 1 GB of RAM, that means each member gets 10 GB of disk and 1 GB of RAM. The total resources added to your deployment is 30 GB of disk and 3 GB of RAM.





 Autoscaling Considerations 



* Scaling your deployment up might cause your databases to restart. If your scaled deployment needs to be moved to a host with more capacity, then the databases are restarted as part of the move.
* Disk cannot be scaled down.
* A few scaling operations can be more long running than others. Drastically increasing RAM or Disk can take longer than smaller increases to account for provisioning more underlying hardware resources.
* Autoscaling operations are logged in [IBM Cloud® Activity Tracker](https://cloud.ibm.com/docs/databases-for-mysql?topic=cloud-databases-activity-tracker).
* Limits



* can't set anything to scale in an interval less than 60 seconds.
* Maximum Disk = 3 TB per member
* Maximum RAM = 112 GB per member



* Autoscaling does not scale down deployments where disk or memory usage has shrunk. The RAM provisioned to your deployment remains for your future needs, or until you scale down your deployment manually. The disk provisioned to your deployment remains because disk can not be scaled down.
* If you just need to add resources to your deployment occasionally or rarely, you can [manually scale](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-resources-scaling) your deployment.







 Configuring Autoscaling in the UI
If you want to use a different file system, such as xfs or ext3, [create a customized storage class](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc-customize-storage-class).



* 10 IOPS/GB: ibmc-vpc-block-10iops-tier or ibmc-vpc-block-retain-10iops-tier
* 5 IOPS/GB: ibmc-vpc-block-5iops-tier or ibmc-vpc-block-retain-5iops-tier
* 3 IOPS/GB: ibmc-vpc-block-general-purpose or ibmc-vpc-block-retain-general-purpose
* Custom: ibmc-vpc-block-custom or ibmc-vpc-block-retain-custom



3. Decide on your Block Storage for VPC configuration.



1. Choose a size for your storage. Make sure that the size is supported by the Block Storage for VPC profile that you chose.
2. Choose if you want to keep your data after the cluster or the persistent volume claim (PVC) is deleted.



* If you want to keep your data, then choose a retain storage class. When you delete the PVC, only the PVC is deleted. The persistent volume (PV), the physical storage device in your IBM Cloud 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 Block Storage for VPC.
* If you want the PV, the data, and your physical Block Storage for VPC device to be deleted when you delete the PVC, choose a storage class without retain.





4. Create a configuration file to define your persistent volume claim and save the configuration as a YAML file.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: <pvc_name> Enter a name for your PVC.
spec:
accessModes:
- ReadWriteOnce ReadWriteOnce is the only supported access mode.
* UI
* CLI
* API
* Terraform







 Managing file shares 

Manage file shares that you created. You can rename a file. You can increase its capacity and modify its IOPS. You can add mount targets to a file share, mount, and unmount a file share from virtual server instances. You can rename or delete a mount target, and you can delete a file share.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.

File Storage for VPC service requires IAM permissions for role-based access control. For example, to create a file share, you need to at least editor permissions. For more information, see the [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls) for file shares.



 Manage file shares and mount points in the UI 

In the console, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apirename-file-share-ui).
* [Add mount target to a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apiadd-mount-target-ui).
* [Rename a mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apirename-mount-target-ui).
* [Update a file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=apifs-update-profile-ui)
6. If you receive an error message that indicates the resource quota is exceeded, delete apps or app revisions before you can deploy additional apps or app revisions.



* To manage your apps, use the [ibmcloud ce app list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-list) command to display a list of all your apps in the current project. Use the [ibmcloud ce app delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-delete) command to remove apps as needed.
* To manage your app revisions, use the [ibmcloud ce revision list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-revision-list) command to display all your app revisions.



7. To address the Docker Hub rate limit problem, you can take the following actions.



* Authenticate with Docker Hub to increase the rate limit. Be aware of [Docker rate limits](https://docs.docker.com/docker-hub/download-rate-limit).
* Pull the image from Docker Hub and publish the image in a different registry, such as IBM Cloud® Container Registry. Then, pull your image from the new location.





If these solutions do not solve your issue, for further debugging, try retrieving the logs or the system event information for your app. For more information, see [How do I get logs for my apps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-appsts-app-gettinglogs) and [How do I get system event information for my apps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-appsts-app-gettingevent).

For more about working with apps, see [Deploying apps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads).
Erase all hard disks This option is available only on physical devices and requires special user permissions set by the account administrator.

OS reload with disk preservation This option configures your current primary disk as a secondary disk (retaining all data), and creates a new primary disk. The OS is installed on the new primary disk. Retains all data on the current primary disk during the OS Reload process. Retains all data on the current primary disk during the OS Reload process. Disk preservation converts the primary drive to a Portable Storage device. This option is available only on virtual devices and incurs charges based on the billing patterns (hourly or monthly) of the device. Charges might be canceled by canceling the Portable Storage device anytime after it was created.
6. Click Load selected image.
7. Review the image configuration and click Next to proceed to the next screen or Cancel to cancel the action.

After you click Next, all network ports for the device are systematically shut down and the device is unavailable for up to 15 minutes. During this time, the action can be canceled at any time by clicking Cancel. The next step must be completed within 15 minutes of clicking Next or the previous steps must be completed again. This process is in place as a safeguard to ensure that no additional data is added to a device between the configuration confirmation and the OS Reload initiation.
8. Click Confirm OS Reload to confirm the action and begin the OS reload process. Click Cancel to cancel the action.







 What's next? 

After you initiate the OS Reload process, the device is taken offline and the OS Reload process begins. The time period in which an OS reload takes place varies based on the current and new configuration of the device. Throughout the configuration process, the minimum time for the OS Reload is displayed on each screen. The timeframe that is displayed is an estimate that is made by the system and is given as a courtesy. If the reload takes longer than 24 hours, contact [IBM Support](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-gettinghelp).

When the device returns online, it functions as specified in the new configuration for the OS Reload.
By default, the new deployment is auto-sized to the same disk and memory allocation as the source deployment at the time of the backup from which you are restoring. To adjust the resources that are allocated to the new deployment, use the optional fields in the UI, CLI, or API to resize the new deployment. Be sure to allocate enough for your data and workload; if the deployment is not given enough resources, the restore fails.

Do not delete the source deployment while the backup is restoring. Before you delete the old deployment, wait until the new deployment is provisioned and the backup is restored. Deleting a deployment also deletes its backups.



 Restoring a backup in the UI 

To restore a backup to a new service instance,



1. Click in the corresponding row to expand the options for the backup that you want to restore.
2. Click Restore.
3. Use the dialog box to select from some available options.



* The new deployment is automatically named <name>-restore-[timestamp], but you can rename it.
* You can also select the region where the new deployment is located. Cross region restores are supported, except for restoring into or out of the eu-de region.
* You can choose the initial resource allocation, either to expand or shrink the resources on the new deployment. You can also enable or disable dedicated cores.



4. Click Restore. A "restore from backup started" message appears. Clicking Your new instance is available now. takes you to your Resources List.







 Restoring a backup in the CLI 

The Resource Controller supports provisioning of database deployments, and provisioning and restoring are the responsibility of the Resource Controller CLI. Use the [resource service-instance-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_create) command.

ibmcloud resource service-instance-create <SERVICE_INSTANCE_NAME> <service-id> standard <region> -p '{"backup_id":"BACKUP_ID"}'
Depending on how you created your storage, you might need to delete all three components separately.



 Understanding your storage removal options 

Removing persistent storage from your IBM Cloud account varies depending on how you provisioned the storage and what components you already removed.

Is my persistent storage deleted when I delete my cluster?
: During cluster deletion, you have the option to remove your persistent storage. However, depending on how your storage was provisioned, the removal of your storage might not include all storage components.

If you [dynamically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsdynamic_provisioning) storage with a storage class that sets reclaimPolicy: Delete, your PVC, PV, and the storage instance are automatically deleted when you delete the cluster. For storage that was [statically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsstatic_provisioning), or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, the PVC and the PV are removed when you delete the cluster, but your storage instance and your data remain. You are still charged for your storage instance. Also, if you deleted your cluster in an unhealthy state, the storage might still exist even if you chose to remove it.

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

How does the billing stop after I delete my storage?
* UI
* CLI
* API
* Terraform







 Managing file shares 

Manage file shares that you created. You can rename a file. You can increase its capacity and modify its IOPS. You can add mount targets to a file share, mount, and unmount a file share from virtual server instances. You can rename or delete a mount target, and you can delete a file share.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.

File Storage for VPC service requires IAM permissions for role-based access control. For example, to create a file share, you need to at least editor permissions. For more information, see the [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls) for file shares.



 Manage file shares and mount points in the UI 

In the console, you can:



* [Rename a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingrename-file-share-ui).
* [Add mount target to a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingadd-mount-target-ui).
* [Rename a mount target of a file share](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingrename-mount-target-ui).
* [Update a file share profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managingfs-update-profile-ui)
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg) > Modify Volume.
3. Under Adjust Storage IOPS, make a new selection:



* For Endurance (Tiered IOPS), select an IOPS Tier greater than 0.25 IOPS/GB of your storage. You can increase the IOPS tier at any time. However, decreasing is available only once a month.
* For Performance (Allocated IOPS), specify new IOPS option for your storage by entering a value in the range 100-48,000 IOPS.



Be sure to look at any specific boundaries that are required by size in the order form.
4. Review your selection and the new pricing.
5. Click Modify.
6. Your new storage allocation is available in a few minutes.







 Adjusting the IOPS on your Storage from the SLCLI 

By using the following command, you can adjust the IOPS through the SLCLI.

 slcli block volume-modify --help
Usage: slcli block volume-modify [OPTIONS] VOLUME_ID

Options:
-c, --new-size INTEGER New Size of block volume in GB. If no size
is given, the original size of volume is
used.
Potential Sizes: [20, 40, 80, 100,
250, 500, 1000, 2000, 4000, 8000, 12000]
Minimum: [the original size of the volume]
-i, --new-iops INTEGER Performance Storage IOPS, between 100 and 6000
in multiples of 100 [only for performance
volumes] If no IOPS value is specified, the
original IOPS value of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is less than 0.3, new IOPS/GB
must also be less than 0.3. If original
IOPS/GB for the volume is greater than or
If you are concerned about how much space MongoDB is using to store your data, you can run some native MongoDB [data storage diagnostics](https://docs.mongodb.com/manual/faq/storage/data-storage-diagnostics) to find the sizes of things like databases, collections, and indexes. If the approximate size of your data set is known and fixed, you can manually scale your disk to accommodate your data. If your data set grows at predictable rate over time, you can configure autoscaling to increase disk size when your disk usage hits a certain threshold.





 Disk I/O 

The number of Input-Output Operations per second (IOPS) on Databases for MongoDB deployments is limited by the type of storage volume. Storage volumes for Databases for MongoDB deployments are [Block Storage Endurance Volumes in the 10 IOPS per GB tier](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-orderingthroughConsoleorderingthroughConsoleEndurance). Hitting I/O utilization limits can cause your databases to respond slowly or appear unresponsive. Things like unoptimized queries, [index building](https://docs.mongodb.com/manual/core/index-creation/), and creating new indexes can cause spikes in IOPS, but it's also possible that normal work loads for your applications can exceed the available IOPS for your deployment.

You can increase the number IOPS available to your deployment by increasing disk space. You can also configure autoscaling to increase disk size automatically if your deployment's I/O utilization hits a certain saturation point for an extended period of time.

For more information, see the [MongoDB documentation](https://docs.mongodb.com/manual/faq/storage/how-frequently-does-wiredtiger-write-to-disk).





 WiredTiger Cache and Memory
The system skips the 90%-exceeded warning.

By default, snapshot warning notifications are enabled for every customer. However, you can choose to disable them. When this feature is disabled, all ticket generation and notifications are stopped. You can disable and enable notifications for the volume at any time.

To check whether the notifications are enabled for the storage volume, use the following command.

 slcli block snapshot-get-notification-status
Usage: slcli block snapshot-get-notification-status [OPTIONS] VOLUME_ID
Get snapshots space usage threshold warning flag setting for a given volume

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

To change the status of the notification setting, use the following command.

 slcli block snapshot-set-notification VOLUME_ID
Usage: slcli block snapshot-set-notification VOLUME_ID [OPTIONS]

Options:
--disable Disable snapshot threshold warning notification for the storage volume
--enable Enable snapshot threshold warning notification for the storage volume
-h, --help Show this message and exit.





 Increasing the amount of Snapshot space for a volume in the UI 

You might need to add snapshot space to a volume that didn't previously have any or might require extra snapshot space.

Snapshot space can be increased. It can't be reduced. You can select a smaller amount of space until you determine how much space you need. Remember, automated, and manual snapshots share the space.

Snapshot space is changed through Storage > Block Storage for Classic.



1. Click your storage volume, click Actions, and click Change Snapshot Space.
2. Select from a range of sizes from the prompt. Sizes typically range from 0 to the size of your volume.
3. Click Continue.
4. Enter any Promo Code that you have, and click Recalculate. The Charges for this order and Order Review fields are completed by default.
5. Read the service agreement, and if you agree with the terms click checkbox, and click Place Order.