vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The first volume has 4 GB of data and the second 20 GB. An average of the two would be 12 GB.
* Number of backups per volume per month. You can take a maximum of 750 backup snapshots per volume.
* Percent of incremental change after the initial backup. For example, 15 percent increase in size for each subsequent backup.



3. When you're finished, click Calculate cost.



The cost estimate summary shows how the costs are calculated and breaks down the storage cost, providing a monthly estimate. Click Save to see the details on the cost estimator panel.







 Creating backup policies and plans from the CLI 

You can create a backup policy from the command-line interface (CLI). The following examples show how to create a policy with no plan, a policy and a plan together, and a separate backup plan for an existing policy. They also show how to create multiple plans for an existing policy and how to create a plan with fast restore for backups.

For more information about available command options, see [ibmcloud is backup-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-create).



 Before you begin 

Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in. For more information, see the [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).



1. Log in to IBM Cloud®.

ibmcloud login --sso -a cloud.ibm.com

This command returns a URL and prompts for a passcode. Go to that URL in your browser and log in. If successful, you get a one-time passcode. Copy this passcode and paste it as a response on the prompt. After successful authentication, you are prompted to choose your account. If you have access to multiple accounts, select the account that you want to log in as. Respond to any remaining prompts to finish logging in.
: Version 0.5.0 of the IBM Cloud for Financial Services profile is now available with new goals and controls. For more information, see the [IBM Cloud for Financial Services profile change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-fs-change-log).





 9 August 2022 

New available: Longer default storage
: The data that is generated during a scan is now stored for 180 days. This is an increase from 30 days. For more information about how your data is stored, see [Storing and encrypting data in Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-mng-data).





 3 August 2022 

Change to permission requirements for integrations
: As of today, Security and Compliance Integrations permissions for viewing, creating, updating, and deleting integrations in Security and Compliance Center are no longer supported. To work with integrations use the following action to role mappings:



* compliance.posture-management.integrations-read: View an integration in Security and Compliance Center.
* compliance.posture-management.integrations-create: Create an integration in Security and Compliance Center.
* compliance.posture-management.integrations-update: Update an integration in Security and Compliance Center.
* compliance.posture-management.integrations-delete: Delete an integration in Security and Compliance Center.



For more information about required permissions, view [Managing IAM access for Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-access-management).





 2 August 2022 

Deprecated: Credential passphrase
: As of today, the ability to create a passphrase to manage the security of your credentials is deprecated in favor of the Bring Your Own Key (BYOK) functionality. If you are currently using a passphrase to protect your credentials, you must disable the passphrase by returning to IBM-managed encryption before 1 September 2022. Then, you can enable BYOK on the Settings page of the Security and Compliance Center UI.
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. Your additional snapshot space is provisioned in a few minutes.







 Deleting a snapshot schedule in the UI 

Snapshot schedules can be canceled through Storage > Block Storage for Classic.



1. Click the volume ID to display its related information.
2. Click Snapshots.
3. Click the schedule to be deleted in the Snapshot Schedules frame.
4. Click the checkbox next to the schedule to be deleted and click Save.



If you're using the replication feature, be sure that the schedule you're deleting isn't the schedule that is used by replication. For more information about deleting a replication schedule, see [Replicating Data](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-replication).





 Deleting a snapshot schedule from the SLCLI 

You can accomplish this task by using the following command.

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

Disables snapshots on the specified schedule for a given volume

Options:
--schedule-type TEXT Snapshot schedule [INTERVAL|HOURLY|DAILY|WEEKLY]
[required]
-h, --help Show this message and exit.

If you're using the replication feature, be sure that the schedule you're deleting isn't the schedule that is used by replication. For more information about deleting a replication schedule, see [Replicating Data](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-replication).





 Deleting a snapshot in the UI
Options:
--sortby TEXT Column to sort by
--columns TEXT Columns to display. Options: ID, Username, Account ID,
Capacity (GB), Hardware ID, Guest ID, Host ID
-h, --help Show this message and exit.





 Viewing the replication history in the UI 

To view the Replication history, click Manage on the main menu bar. Select Account, and scroll to the Audit Log. The Storage Replication Events list contains the names of the volume, a description of the replication event and the timestamp of the event.





 Editing the Replication Schedule in the UI 

The replication schedule is based on an existing snapshot schedule. To change the replica schedule from Hourly to Daily or Weekly or vice versa, you must cancel the replica volume and set up a new one.

However, if you want to change the time of day when your Daily replication occurs, you can adjust the existing schedule on the active volume.



1. On the active volume details page, click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg).
2. Select Edit Snapshot Schedule.
3. Look in the Snapshot frame under Schedule to determine which Daily schedule you're using for replication. Change the schedule that you want.
4. Click Save.







 Deleting an existing replica file share in the UI 

You can cancel replication either immediately or on the anniversary date, which causes billing to end.



1. Click the volume from the File Storage for Classic page.
2. Click Actions![Actions icon](https://cloud.ibm.com/docs-content/v1/content/14cf2f2f32b430cf4ed67ad14b3cecc010f91c45/icons/action-menu-icon.svg).
3. Select Delete Replica.
4. Select when to cancel.
The tooling is therefore unable to show a list of ingestion notices, and there is no easy way to determine which, if any, documents crawled by the Data Crawler failed to be ingested. : Document status information is not always accurate. : If an ingestion operation takes longer than the configured timeout of 10 minutes, the service reports that the document is not known to the service until the ingestion operation completes. After the operation completes, the document status is available and accurate. : Documents that are successfully indexed but generated errors can have a status of failed for a short period of time until the document fully commits to the index. After the document commits to the index, the listed status is accurate. : You cannot use the tooling to replace a specific document. If you attempt to do so, the second document is uploaded as a separate document. If you are using the API and know the ID of the document you want to replace, you can do so; see [Update a document](https://cloud.ibm.com/apidocs/discoveryupdate-a-document) in the API reference. If you are using the Data Crawler, uploading an updated document from the same URL as a previous document replaces the original document. : If you are using the tooling to edit the enrichments in your configuration, you can edit only enrichments used for extraction. If you want to add or edit other enrichments (for example, custom enrichments from a IBM Watson™ Knowledge Studio model), you must use the API. See the [Update a configuration](https://cloud.ibm.com/apidocs/discoveryupdate-a-configuration) method in the API reference for information. : The Java, Python, and Node.js SDKs for Discovery do not provide all of the functionality provided by the default REST (cURL) API. Not all cURL methods have an equivalent method in the non-cURL SDKs, and not all non-cURL methods provide all of the same features that their cURL equivalents have. In other words, the Java, Python, and Node.js SDKs currently provide only a subset of the cURL API's capabilities.
Delete the VPN gateway and retry.

There was a request to delete a subnet, but the subnet still has a VPN gateway attached to it. You must delete the VPN gateway before you can delete the subnet.

If using the CLI, you can run ibmcloud is vpn-gateways to list the VPN gateways. Look at the "Subnets" value to determine its subnet and "Status" to determine its status. Run ibmcloud is vpn-gateway-delete to delete a VPN gateway that doesn't already have a status of "deleting".

In some situations, this error can occur even when the console shows 0 VPN gateways. Deletion is asynchronous, and it may take a few minutes for the internal status to change. Try your subnet deletion again in a few minutes.

If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 subnet_out_of_ip_addresses 

Message: There are no more IP addresses available in the subnet.

There was a request to allocate an IP address in the subnet, but the subnet is out of IP addresses. Try using a different subnet, or delete IP addresses in the subnet to free up space.

To find the IP addresses currently allocated in the subnet, run the API command GET /v1/subnets/{subnet ID}/reserved_ips?version=$version&future_version=true&generation=1 (disclaimer: this is currently a Beta API).





 subnet_unknown_state 

Message: The subnet <subnet_id> is in an invalid state for the requested operation.

The subnet must be in available status before you can operate it. Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).
Publishing a deployment record (deprecated) 

You can publish a deployment record by using idra (deprecated) to integrate your Delivery Pipeline with DevOps Insights. Deployment records inform IBM Cloud® DevOps Insights about the deployments that are made during the deployment process. This record contains the application name, build ID, environment name, status of the deployment, and more. The application name and build ID in the deployment record must match the ones that are used in the build record for a specific build.



 Before you begin 

Before you publish a deployment a record, you must publish a build record. For more information about publishing a build record, see [Publishing a build record by using idra (deprecated)](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-publish-build-idra).





 Publishing a deployment record (deprecated) 

In the deployment job, use the following script to upload a deployment record. The --env flag identifies the deployment environment.

!/bin/bash
 Add user api key to stage environment variable as a secured property
export LOGICAL_APP_NAME="SampleApp"
export BUILD_PREFIX="master"

 node 4.x or above is needed
export PATH=/opt/IBM/node-v4.2/bin:$PATH
npm install -g grunt-idra3

idra --publishdeployrecord --env=staging --status=pass

Environment variables that you define in the pipeline provide context for publishing these records. You can define them by using the export command in your jobs' scripts. You can also set them in each pipeline stage's Environment Properties menu.



Table 1. Environment variable and purpose

 Environment Variable Purpose Required 

 IBM_CLOUD_API_KEY The IBM Cloud user's API key. All jobs that start the idra CLI and enforce DevOps Insights risk policies. 
 LOGICAL_APP_NAME The app's name on the dashboard. All jobs that build, test, deploy, and enforce DevOps Insights risk policies. 
 BUILD_PREFIX Text that is added as a prefix to the stage's builds.
: ibmc-block-custom: Delete
: ibmc-block-retain-custom: Retain







 Sample customized storage classes 

You can create a customized storage class and use the storage class in your PVC.

IBM Cloud Kubernetes Service provides [pre-defined storage classes](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_storageclass_reference) to provision block storage with a particular tier and configuration. Sometimes, you might want to provision storage with a different configuration that is not covered in the pre-defined storage classes. You can use the examples in this topic to find sample customized storage classes.

To create your customized storage class, see [Customizing a storage class](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_custom_storageclass). Then, [use your customized storage class in your PVC](https://cloud.ibm.com/docs/containers?topic=containers-block_storageadd_block).



 Creating topology-aware storage 

To use block storage in a multizone cluster, your pod must be scheduled in the same zone as your block storage instance so that you can read and write to the volume. Before topology-aware volume scheduling was introduced by Kubernetes, the dynamic provisioning of your storage automatically created the block storage instance when a PVC was created. Then, when you created your pod, the Kubernetes scheduler tried to deploy the pod to the same data center as your block storage instance.

Creating the block storage instance without knowing the constraints of the pod can lead to unwanted results. For example, your pod might not be able to be scheduled to the same worker node as your storage because the worker node has insufficient resources or the worker node is tainted and does not allow the pod to be scheduled. With topology-aware volume scheduling, the block storage instance is delayed until the first pod that uses the storage is created.

To use topology-aware volume scheduling, make sure that you installed the IBM Cloud Block Storage plug-in version 1.2.0 or later.
If you want to clone your volume and use it independently from the original volume, see [Creating a duplicate File Volume](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-duplicatevolume).

Before you can replicate, you must create a snapshot schedule.

When you fail over, you are “flipping the switch” from your storage volume in your primary data center to the destination volume in your remote data center. For example, your primary data center is in London and your secondary data center is in Amsterdam. If a failure event occurs, you’d fail over to Amsterdam. Failing over means connecting to the now-primary volume from a vSphere Cluster instance in Amsterdam. After your volume in London is repaired, a snapshot is taken of the Amsterdam volume. Then, you can fail back to London and the once-again primary volume from a compute instance in London.

Before the volume fails back to the primary data center, it needs to stop being used at the remote site. A snapshot of any new or changed information is taken and replicated to the primary data center before it can be mounted again on the production site ESXi hosts.

For more information about configuring replicas, see [Replication](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-replication).

Invalid data, whether corrupted, hacked, or infected replicate according to the snapshot schedule and snapshot retention. Using the smallest replication windows can provide for a better recovery point objective. However, it also can provide less time to react to the replication of invalid data.







 Ordering File Storage for Classic 

Follow the instructions the [Advanced Single-Site VMware® Reference Architecture](https://cloud.ibm.com/docs/virtualization?topic=virtualization-advanced-single-site-vmware-reference-architecture) to configure your VMware environment.
Deprecated: Credential passphrase
: As of today, the ability to create a passphrase to manage the security of your credentials is deprecated in favor of the Bring Your Own Key (BYOK) functionality. If you are currently using a passphrase to protect your credentials, you must disable the passphrase by returning to IBM-managed encryption before 1 September 2022. Then, you can enable BYOK on the Settings page of the Security and Compliance Center UI. For more information about how your credentials are protected, see [Storing and encrypting data in Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-mng-data).





 25 July 2022 

Now available: Profile updates
: Goal updates are now available IBM Cloud Security Best Practices Profiles. For more information see the [IBM Cloud Security Best Practices change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-ibm-sec-best-practices-change-log).





 12 July 2022 

Now available: New region - WDC
: Security and Compliance Center is now configured to use the Washington DC region as a back up should a disaster scenario occur.





 23 June 2022 

Now available: New version of the IBM Cloud for Financial Services profile
: Version 0.4.0 of the IBM Cloud for Financial Services profile is now available with new goals and controls. For more information, see the [IBM Cloud for Financial Services profile change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-fs-change-log).





 1 June 2022 

As of 1 June 2022, the Security Insights component of Security and Compliance Center is deprecated and support was removed. A replacement has not yet been found. Please note, this discontinuation does not affect the other features in Security and Compliance Center. If you have comments, questions, or concerns, please reach out to Jessica Doherty by email at jpbonner@us.ibm.com.





 27 May 2022
Cloning a volume 

The clone operation creates a full copy of the volume. You can select multiple volumes and initiate a group clone operation. When multiple volumes are selected, the clone operation ensures that a consistent data copy is created.

The clone operation continues to copy data from the source disks to target disks in the background. Depending on the size of the source disks and the amount of data to be copied, the clone operation can take a significant amount of time.

You cannot modify the source or target disk attributes, such as disk size, while the clone operation is in progress.

Best practice: Quiesce all of the applications on the volume that you want to clone.

Use case: You can perform the clone operation on multiple volumes that are attached to the VM and that are in an available state.

Restrictions and considerations: When the clone operation is performed on an volume that is in-use, the Power Systems Virtual Server creates a consistent group snapshot and re-creates the copy of the cloned volume by using the group snapshot.

Steps: Performing the clone operation on a volume consists of three steps: prepare, start, and execute the volumes-clone request. These steps allow you to perform preparatory actions and to authorize the ongoing I/O operations on the source volumes. Breaking the clone operation on a volume into multiple steps provides consistent clones and reduces the VM quiesce time. The clone operation on a volume consists the following steps:

When any of the prepare, start, or clone step fails then you must first perform cancel clone and then re-run all the three step.



 1. Create a volumes-clone request and initiate the Prepare action 



* Requirements



* Minimum of two volumes
* Minimum of one volume to be in the in-use state
* A unique volumes-clone name



* Status change When the preparatory actions are initiated, the initial status of the volumes clone request is set to Preparing. When the preparatory actions are completed successfully, the status changes to Prepared. If an error occurs during the preparatory actions, the status changes to Failed.
This action can take considerable amount of time. Expect a message that shows the failover is in progress. Additionally, an icon appears next to your volume on the File Storage for Classic that indicates that an active transaction is occurring. Hovering over the icon produces a window that shows the transaction. The icon disappears when the transaction is complete. During the Failback process, configuration-related actions are read-only. You can't edit any snapshot schedule or change snapshot space. The event is logged in replication history.
4. In the upper right, click View All File Storage for Classic.
5. Click your replica volume ("source"). This volume now has an Inactive status.
6. Mount and attach your storage volume to the host. For more information, see [connecting your storage](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-getting-startedmountingstorage).



If you need further assistance, create a [support case](https://cloud.ibm.com/unifiedsupport/supportcenter).





 Fail back from the SLCLI 

To fail back a file volume from a specific replicant volume, use the following command.

 slcli file replica-failback --help
Usage: slcli file replica-failback [OPTIONS] VOLUME_ID

Options:
--replicant-id TEXT ID of the replicant volume
-h, --help Show this message and exit.

During the Disaster Recovery Failover, the system is forced to fail over to the replica site and the replication relationship is severed. To be able to fail back to the original site after the site is restored to normal operations, the system must reestablish the replication bond. This action can take considerable amount of time. During the Failback process, configuration-related actions are read-only. You can't edit any snapshot schedule or change snapshot space. The event is logged in the replication history.

When the original volume is active, you can mount and attach it to the host.