vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Step 5: Scaling the database resources in Databases for MongoDB 

If your service needs additional storage, or you want to reduce the amount of storage allocated to your service, you can do this by scaling resources.



1. Access the Databases for MongoDB service instance from the [Resource List](https://cloud.ibm.com/resources) Under Databases.
2. Click on the Resources panel.

Zoom

![Scale Resources](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution7/MongoDB_ScaleResources.png)

Scale Resources
3. Adjust the slider to raise or lower the storage allocated to your Databases for MongoDB database service.
4. Click Scale Deployment to trigger the rescaling and return to the dashboard overview. It will indicate that the rescaling is in progress.
5. Alternatively configure autoscaling rules to automatically increase the database resources as its usage is increasing.







 Step 6: Remove resources 

To remove resource, follow these steps:



1. With the command below, delete the project to delete all it's components (applications, jobs and so on).

ibmcloud code-engine project delete --name mean-stack
2. Delete the Databases for MongoDB service key.

ibmcloud resource service-key-delete mean-sample-mongodb-key
3. Delete the Databases for MongoDB service.

ibmcloud resource service-instance-delete mean-sample-mongodb



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related Content
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.
* 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 individual file share. You must select at least one file share. For more information, see [NFS storage](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-consold-clustervc_orderinginstance-nfs-storage).



7. Review the estimated price and click Add.







 Results after you add NFS storage to Cyber Recovery instances 



1. You might experience a slight delay on the console while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2. You are notified by email that your request to add NFS storage is being processed. On the console, the status of the cluster that is associated with the NFS storage is changed to Modifying.
3. If you do not see that the new NFS storage is added to the list in the cluster, check your email or console notifications for more details.







 Related links 



* [Planning for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_planning)
* [Requirements for Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance_reqs)
Editing your discovered resources 

VPC+ Cloud Migration creates a workspace after discovering your environment. In the workspace you can add, delete, or edit any section of your VPC. For example, you can attach a new load balancer or add a new virtual server instance by clicking the Add icon next to Load Balancers and Instances. You can also delete items that you do not want to migrate.

To manage your VPCs, select Manage VPCs in the navigation menu and choose your Cloud Account and Region.

You can manage your VPC in a tabular or graphical form by toggling between the two views.

As you proceed to make changes to any component in your VPC, the changes are reflected in your graphical view, which can make it easier to manage and add information or new components.



  Next steps 

Refer to [Provisioning your resources in VPC](https://cloud.ibm.com/docs/wanclouds-vpc-plus?topic=wanclouds-vpc-plus-migrate-provision).
Managing volume count and capacity limits 

Block Storage for VPC offers block-level data storage volumes that can be attached to an instance as either a boot volume or as a data volume. Answer the following questions when you're ordering block storage volumes or requesting an increase in your volume or capacity limits.



 Overview 

With Block Storage for VPC, you can create up to 750 boot and data block storage volumes per account in a region. You can request an increase of this quota by contacting [IBM Support](https://cloud.ibm.com/unifiedsupport/cases/add) and submitting a support case.

Capacity for secondary volumes ranges 10 - 16,000 GB. You can also expand volume capacity within its IOPS tier profile or custom band. For more information, see [expanding block storage volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes).





 Volume count and storage limits checklist 

Review the following checklist items and record your answers. Provide this information when you create a support case.



* Ticket Subject: "Request to Increase VPC Volume Count Limit".
* How many extra volumes do you need? Provide your account, region, and the zone where you want more volumes. For example, "200 volumes in US South-2".
* How many volumes are primary boot volumes versus secondary data volumes? For example, "50% primary volumes, 50% secondary volumes" or "100 primary volumes, 100 secondary volumes".
* Of the secondary volumes, how many secondary volumes do you need and of what capacity? For example, "75% of the secondary volumes are under 250 GB and 25% are up to 16,000 GB.
* How many total volumes use customer-managed encryption? For example, "100 volumes (or 50%) are to use customer-managed encryption".
* Provide an estimate of when you expect or plan to provision all of the requested volumes. For example, "I expect to create these volumes within 90 days".
* Provide a 90-day forecast of expected average capacity usage of these volumes.
You can obtain more information about the volume, such as how much disk space is taken and how much is available, from your Compute host's operating system.

You can use the following commands.



* Linux®:

df -h

The command provides an output that shows how much space is available space and the percentage used.

$ df -hT /dev/sda1
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 disk 6.0G 1.2G 4.9G 20% /
* Windows®: you have two options.

fsutil volume diskfree C:

dir C:

The last line of the output shows how much space is unused.

You can also view the free disk space in the File Explorer by clicking This PC.



* Does the volume need to be pre-warmed to achieve expected throughput?

Pre-warming is not needed. You can observe specified throughput immediately upon provisioning the volume.
* Can more throughput be achieved by using a faster Ethernet connection?

Throughput limits are set at the LUN level and a faster Ethernet connection doesn't increase that limit. However, with a slower Ethernet connection, your bandwidth can be a potential bottleneck.
* Do firewalls and security groups impact performance?

It's best to run storage traffic on a VLAN, which bypasses the firewall. Running storage traffic through software firewalls increases latency and adversely affects storage performance.
* How do I route Block Storage for Classic traffic to its own VLAN interface and bypass a firewall?

To enact this best practice, complete the following steps.



1. Provision a VLAN in the same data center as the host and the Block Storage for Classic device. For more information, see [Getting started with VLANs](https://cloud.ibm.com/docs/vlans?topic=vlans-getting-started).
2. Provision a secondary private subnet to the new VLAN.3
3. Trunk the new VLAN to the private interface of the host.
For details on establishing a hard quota that prevents usage beyond a set bucket size, see [Using Bucket Quota](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-quota).





 Why am I unable to delete a Object Storage instance? 

It isn't possible to delete an instance if the API key or Service ID being used is locked. You'll need to navigate in the console to Manage > Access (IAM) and unlock the API Key or Service ID. The error provided may seem ambiguous but is intended to increase security:

> An error occurred during an attempt to complete the operation. Try fixing the issue or try the operation again later. Description: 400

This is intentionally vague to prevent any useful information from being conveyed to a possible attacker. For more information on locking API keys or Service IDs, [see the IAM documentation](https://cloud.ibm.com/docs/account?topic=account-serviceids&interface=uilock_serviceid).





 How do I download the Root CA certificate for Object Storage? 

Object Storage root CA certificates can be downloaded from [https://www.digicert.com/kb/digicert-root-certificates.htm](https://www.digicert.com/kb/digicert-root-certificates.htm). Please download PEM or DER/CRT format from "DigiCert TLS RSA SHA256 2020 CA1" that is located under "Other intermediate certificates."
Move the Netezza unit (NZU) slider to the required position, or select from the drop-down.
6. Move the Storage density slider to the required position, or select from the drop-down.
7. Click Scale.







 Initiating on demand scaling 



1. Go to Workload patterns.
2. Click Scaling.
3. Type the name for your scaling job.
4. Move the Netezza unit (NZU) slider to the required position, or select from the drop-down.
5. Click Scale.







 Scheduling scaling 



1. Go to Workload patterns.
2. Click Scaling.
3. Type the name for your scaling job.
4. Select the Schedule for a later time checkbox.
5. Select the required parameters.
6. Click Scale.







 Editing scheduled scaling 



1. Go to Workload patterns > Schedules.
2. Select the operation that you want to edit.
3. Click Edit.
4. Select the required parameters.
5. Click Save.







 Deleting scheduled scaling 



1. Go to Workload patterns > Schedules.
2. Select the operation that you want to delete.
3. Click Delete.
4. Click Delete.







 Checking scaling history 



1. Go to Workload patterns > History.
2. Depending on your requirements, perform one of the following actions:



* Filter by Time completed or Owner.
* In Find history, type the name of the operation.
* 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. Click Modify.
5. Your new storage allocation is going to be available in a few minutes.







 Adjusting the IOPS on your Storage from the CLI 

You can update your IOPS from the SLCLI by using the following command.

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

Options:
-c, --new-size INTEGER New Size of file 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
equal to 0.3, new IOPS/GB for the volume must
also be greater than or equal to 0.3.]
-t, --new-tier [0.25|2|4|10] Endurance Storage Tier (IOPS per GB) [only for
endurance volumes] If no tier is specified,
the original tier of the volume will be
used.
* I expanded the volume size of my Block Storage for Classic through the Cloud console, but the size on my server is still the same. How do I fix it?

To see the new expanded LUN size, you need to rescan and reconfigure your existing Block Storage for Classic disk on the server. See the following examples. For more information, see your operating system Documentation.



 Windows® 2016 



1. Go to Server Manager > Tools > Computer Management > Disk Management.
2. Click Action > Refresh.
3. Click Action > Rescan Disks. This process can take up to 5 minutes or more to finish. The additional capacity displays as a deallocated partition on the existing Disk.
4. Partition the deallocated space as you want. For more information, see [Microsoft® - Extend a basic volume](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).







 Linux 



1. Log out of each multipath session of the block storage device that you expanded.

 iscsiadm --mode node --portal <Target IP> --logout
2. Log in again.

 iscsiadm --mode node --portal <Target IP> --login
3. Rescan the iscsi sessions.

 iscsiadm -m session --rescan
4. List the new size by using fdisk -l to confirm that the storage was expanded.
5. Reload multipath device map.

 multipath -r <WWID>

 multipath -r 3600a09803830477039244e6b4a396b30
reload: 3600a09803830477039244e6b4a396b30 undef NETAPP ,LUN C-Mode
size=30G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=undef
From the VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server 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.
* 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 individual file share. You must select at least one file share. For more information, see [NFS storage](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-consold-clustervc_orderinginstance-nfs-storage).



7. Review the estimated price and click Add.







 Results after you add NFS storage to vCenter Server instances 



1. You might experience a slight delay on the console while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2. You are notified by email that your request to add NFS storage is being processed. On the console, the status of the cluster that is associated with the NFS storage is changed to Modifying.
3. If you do not see that the new NFS storage is added to the list in the cluster, check your email or view the console notifications to find more details.







 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
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-cassandra?topic=cloud-databases-activity-tracker).
* Limits



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



* Autoscaling does not scale down deployments where disk or memory usage 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 cannot be scaled down.
* If you need to add resources to your deployment occasionally or rarely, you can [manually scale](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-resources-scaling) your deployment.







 Configuring Autoscaling in the UI 

The Autoscaling pane is on the Resources tab of your deployment's Manage page. To enable scaling, enter your parameters. Then, check the boxes to enable the parameters you are using. Be sure to click Save Changes for your configuration to be saved and your changes to take effect.

To disable autoscaling, clear the boxes for the parameters that you no longer want to use. If you clear all the boxes, autoscaling is disabled. Click Save Changes to save the configuration.





 Configuring Autoscaling in the CLI 

You can get the autoscaling parameters for your deployment through the CLI by using the [cdb deployment-autoscaling](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-reference-ibmcloud-cdb-deployment-autoscaling-) command.

ibmcloud cdb deployment-autoscaling <deployment name or CRN> member
If this message occurs again, go to the [IBM Cloud status](https://cloud.ibm.com/status) page to check whether a service or component has an issue.





 Can't perform requested actions 

You can't complete actions without appropriate access authority.

 What’s happening 

When you try to perform actions for a service instance or an app instance, you can't complete the requested actions and see one of the following error messages:

BXNUI0514E: You are not a developer for any of the spaces in the <orgName> organization.

Server error, status code: 403, error code: 10003, message: You are not authorized to perform the requested action.

 Why it’s happening 

You don't have the appropriate level of authority to perform the actions.

 How to fix it 

To get the appropriate authority level, use one of the following methods.



* Select another organization and space for which you have the Developer role.
* Ask the org manager to change your role to Developer or to create a space and then assign you a Developer role. See [Cloud Foundry access](https://cloud.ibm.com/docs/account?topic=account-mngcf) for details.







 Disk quota is exceeded 

If you run out of disk space, you can manually modify the disk quota to get more disk space.

 What’s happening 

When you run out of disk space, you might see a message that states that the disk quota is exceeded. To resolve the problem, you might have tried scaling up your app instance to get more disk space. For example, you might scale from 256 - 1256 MB by changing the memory quota on the app details page. However, because the disk quota remained the same, you didn't get more disk space.

 Why it’s happening 

The default disk quota that is allocated for an app is 1 GB. If you need more disk space, you must manually specify the disk quota.

 How to fix it 

Use one of the following methods to specify your disk quota. The maximum disk quota that you can specify is 2 GB.
For example, [RHEL 8 - Modifying Logical Volume](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/modifying-the-size-of-a-logical-volume_configuring-and-managing-logical-volumes) or [Microsoft® - Extend a basic volume](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).





 Resizing storage with Terraform 

You can increase your storage capacity by using the ibm_storage_block resource, and specifying a larger number in the capacity argument. The following example increases the capacity of an Endurance volume to 40 GB.

resource "ibm_storage_block" "test1" {
type = "Endurance"
datacenter = "dal09"
capacity = 40
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
}

The following example increases the capacity of a Performance volume to 40 GB.

resource "ibm_storage_block" "test2" {
type = "Performance"
datacenter = "dal09"
capacity = 40
iops = 100
os_format_type = "Linux"

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

For more information about the arguments and attributes, see [ibm_storage_block](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/storage_block).
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 file snapshot-get-notification-status
Usage: slcli file 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 file snapshot-set-notification VOLUME_ID
Usage: slcli file 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 increased through Storage > File 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.
So when you determine how much Snapshot space that you need, consider the rate of change carefully. It's a huge influence on how much snapshot space is needed. A bigger volume is more likely to change more often. However, a 500-GB volume with 5 GB of change and a 10-TB volume with 5 GB of change use the same amount of snapshot space.

Additionally, for most workloads, the larger a volume is the less space needs to be set aside initially. It's primarily due to the underlying data efficiencies, and the nature of how snapshots work in the environment.





 Ordering Snapshot space in the UI 



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/catalog), and click the menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/icon_hamburger.svg). Then, select Classic Infrastructure![Classic icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/classic.svg).
2. Access your Storage LUN through Storage > Block Storage for Classic.
3. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg), then click Change Snapshot Space.
4. Select the storage size that you need.
5. Click Continue.
6. Enter any Promo Code that you have, and click Recalculate. The Charges for this order and Order Review fields are completed by default.

Discounts are applied when the order is processed.
7.