vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Verify that the volume is detached from the instance by making a GET /instances/{instance_id} call.





 Applying user tags that are associated with a backup policy to a volume with the API 

To add user tags to a volume, you first make a GET /volumes/{volume_id} call and copy the hash string from Etag property in the response header. You then use the hash string when you specify If-Match in a PATCH /volumes/{volume_id} request to create new user tags.

For more information, see [Apply tags to Block Storage for VPC volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-use-policies&interface=apibackup-apply-tags-volumes-api) in the VPC backup service documentation.







 Applying access management tags to a Block Storage for VPC volume 

Access management tags are metadata that you can add to your Block Storage for VPCto help organize access control resource relationships. You first create the tag and then apply it to a new volume or to an existing volume. You can apply the same access management tag to multiple Block Storage for VPC volumes. You then assign access to the tag in IAM. Optionally, you can create an IAM access group and manage users.

Access management tags are not used by [backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-use-policies) to create backup snapshots. Backup snapshots are created when user tags match backup policy tags for target resources to volume user tags.



 Step 1 - Creating an IAM access management tag in the UI 

In the console, complete the following steps.



1. Go to Manage > Account, and then select Tags.
2. Click the Access management tags tab. Add a tag name in the field. Access management tags require a key:value format.
3. Click Create Tags.







 Step 1 - Creating an IAM access management tag with the API
To add volumes to a policy, add user tags to the volume that are in the backup policy's tags for target resources. When you remove tags from a volume that are in a backup policy, the volume is no longer be backed up.



1. Go to the list of Block Storage for VPC volumes. In [IBM Cloud console)](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Locate the volume that you want and click the name link.
3. From the Block Storage for VPC volumes details page, click the Backup policies tab. Table 5 describes the information on the Backup policies page.
4. Click Attach to apply a new backup policy to this volume. In the side panel, select a backup policy from the menu, and select the policy tags to apply to the volume. You can also view the plan details that can help you decide whether to use that policy. If satisfied, click Apply policy and tags.





Table 5. Backup policies associated with a Block Storage for VPC volume.

 Field Description 

 Policy name Click the policy name to go to that backup policy. 
 Status [Status of the backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-manage&interface=uibackup-policy-statuses). 
 Last run time The last scheduled run of the backup policy that created a backup. 









 Viewing Block Storage for VPC volumes from the CLI 

View details about a Block Storage for VPC volume or summary information about all volumes from the CLI.

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.
4.6.3 release, 23 february 2023 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.6.3 is available.

For a list of new features and bug fixes, see [What's new and changed in Watson Discovery](https://www.ibm.com/docs/SSQNUZ_4.6.x/fixlist/discovery-fixlist.html)

Features that are not available in this release
: The following features are generally available from managed IBM Cloud deployments at the time of this release, but not from installed deployments:



* Answer finding
* Manage data page



Important: Back up your data before upgrading to version 4.6.3
: Before upgrading to version 4.6.3, you must make a backup of your data. Preserve the backup in a safe location. For more information about backing up your data, see [Backing up and restoring data in IBM Cloud Pak for Data](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-backup-restore). That topic also includes information about restoring your data if that becomes necessary.





 4.6.2 release, 30 January 2023 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.6.2 is available.

For a list of new features and bug fixes, see [What's new and changed in Watson Discovery](https://www.ibm.com/docs/SSQNUZ_4.6.x/fixlist/discovery-fixlist.html)

Features that are not available in this release
: The following features are generally available from managed IBM Cloud deployments at the time of this release, but not from installed deployments:



* Answer finding
* Manage data page







 4.6.1 release, December 2022 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data was not refreshed as part of 4.6.1. However, the product documentation was updated with fixes and enhancements.





 4.6 release, 30 November 2022 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.6 is available.
[menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Snapshots.
2. Click the row to select the snapshot that you want to delete.
3. From the Actions menu (ellipsis), select Delete all for volume.
4. Confirm the deletion by typing delete and then click Delete.







 Deleting snapshots from the Block Storage for VPC details page in the UI 

You can delete the most recently created snapshot from the list of snapshots from the Block Storage for VPC volume details page. Optionally, you can delete all snapshots from this view.



1. Go to the list of all Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Select a volume from the list and click the volume name to go to the volume details page.
3. Click Snapshots to see a list of snapshots taken of this volume.
4. Click Delete all to delete all snapshots for this volume.
5. Alternatively, select a single snapshot in the list for deletion and then:



1. Click the Actions menu (ellipsis).
2. Select Delete from the overflow menu.
3. Confirm the deletion.











 Deleting snapshots from the CLI 

You can delete any snapshot for a volume or all snapshots for a volume. To be able to delete a snapshot, it must meet to the following prerequisites:



* Be in a stable or pending state.
* Not be actively restoring a volume.





 Deleting a single snapshot from the CLI
FAQs for Backup for VPC 

The following questions pertain to the VPC Backup service. If you have other questions you'd like to see answered here, provide feedback by using the Open doc issue or Edit topic links after the FAQs.



 What is the VPC backup service? 

With the VPC backup service, you can create backup policies for your Block Storage for VPC volumes. A backup policy contains a backup plan, where you set a scheduled backup of your volumes. You can create up to four backup plans per policy. When a backup is triggered, it creates a snapshot of the volume contents. You can also set a retention period for your backups so that the oldest ones are deleted either by date or total count. For more information, see [Backup service concepts](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-aboutbackup-service-concepts).





 How do I set up the backup service? 

Before you can create backup policies, you need to grant [service-to-service authorizations](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-s2s-auth&interface=api), and specify user roles to enable the backup service. Then, you add user tags for new or existing data volumes that you associate with a backup policy. Finally, you create backup policies and plans to schedule automatic backups. For more information, see [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create&interface=ui).





 How does the backup service work? 

You add [user tags](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-about-tags) to your volumes and specify the same tags in a backup policy. When the tags match, a backup is triggered based on the backup plan schedule.
ibp-operator 1/1 1 1 48d
orderer1node1 1/1 1 1 20h
orderer2node1 1/1 1 1 22h
orderer3node1 1/1 1 1 22h
orderer4node1 1/1 1 1 22h
orderer5node1 1/1 1 1 22h
ordererorgca 1/1 1 1 48d
peera 0/0 0 0 20h
peerc 1/1 1 1 20h
peerorg1ca 1/1 1 1 48d

Note that peera is not ready.

Use the commands in the [Peer snapshot](https://cloud.ibm.com/docs/blockchain?topic=blockchain-backup-restorebackup-restore-peer-snapshot) section to find the persistent volumes that are associated with the peer. Peers using CouchDB have two volumes.

For each volume, list the available snapshots for that volume. For information on how to list available snapshots, see [Listing all Snapshots with Space Used Information and Management functions](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-managingSnapshotslistsnapshotUI).

For our example, we use CLI and restore a specific snapshot from our volume ID for the CouchDB pod that is associated with peera:

ibmcloud sl file snapshot-list 155617812

Which shows the available snapshots:

id user_name created size_bytes notes
167189176 IBM02SEV2046428_106 2020-09-03T03:00:00-05:00 143089

Pick the snapshot you'd like to restore from the list, keeping in mind that the CouchDB backup must be older than the peer pod backup, and restore it.
* We recommend that you attach extra storage to the instance, locate SAP installation files on this separate disk, and export them over NFS. The disk size must be large enough to host all the data from IBM Cloud Object Storage that is relevant for all the installations and setups.



4. Attach the security group to the virtual server instance that you created in the previous step. Detach the default security group.
5. After some time, instance becomes status 'running'.









 Deploying IBM Cloud VPC for workload services (workload VPC) 

IBM Cloud VPC for workload services (workload VPC) is a mandatory component in the SAP on IBM Power Virtual Services best practices. This service hosts the instances with management components that are used by operating systems and workloads that are running in Power® Systems Virtual Servers.



* Set up Virtual Private Cloud for management services. For more information, see [Creating a VPC and subnet](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-consolecreating-a-vpc-and-subnet).
* Take care about the default network prefix. We recommend reducing the default network prefix, so it does not overlap between all your IBM Cloud VPC services.
* Do not attach a public gateway to the subnet and do not use floating IP addresses. The hosts are communication with the internet over SQUID proxy.





 Deploying host for workload services in workload VPC 

Host for workload services is a mandatory component in the SAP on IBM Power Virtual Services best practices. This virtual server instance hosts optional NFS server, NTP forwarder, DNS forwarder, and LDAP server. If you have already some of these services in your environment that are accessible from Power Systems Virtual Server networks, then you can use them and do not need to install here. Execute following steps to deploy host for private services.

By the using the following setup, we open ports for standard widely used management components: NFS service provided by Linux distributions, NTP service over 'chrony', DNS service over 'bind' and open LDAP.
For more information, see [Viewing backup policy jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policy-jobs).





 Deleting a backup policy in the UI 



1. Go to the [list of backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policies&interface=uibackup-list-all-policies).
2. Locate the policy that you want to delete.
3. From the Actions menu, select Delete.

Confirm that the volumes that are associated with the backup policy are no longer to be backed up, and that backups that were created by the policy continue to exist. You must go to the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-delete-snapshot-ui) and delete each one manually.
4. Enter delete to confirm, the click Delete policy.



The policy is deleted. Existing backups are retained until their expiration date. No further backups for the volumes are made after you delete the plan.





 Deleting a backup plan in the UI 



1. Go to the [list of backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-view-policies&interface=uibackup-list-all-policies) and locate the backup policy.
2. On the backup policy details page, select the plan that you want to delete. You can have up to four backup plans per policy.









 Managing backup policies and plan from the CLI 

Delete a backup policy, rename a policy, and edit user tags from the CLI.



 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 [Root key regional and cross-regional considerations](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutbyok-cross-region-keys).

You can share root keys across accounts by linking accounts. Root keys in a primary account can be accessed and used to encrypt new volumes and file shares that are created in a secondary account. For more information, see [Cross-account encryption for file storage resources](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-byok-cross-acct-key-file).

Customer-managed encryption is available for custom images, boot volumes, data volumes, snapshots, and file shares.



* Data in the instance's boot volume is encrypted by using the [custom image encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutbyok-about-encrypted-images). You can also encrypt the boot volume with a different root key.
* [Data volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-aboutsecondary-data-volumes) can be encrypted by using their own root keys when you provision a virtual server instance or when you create a stand-alone volume. Or, you can use the same root key that you specified for the boot volume.
* Snapshots that are taken of a source volume inherit the encryption from the volume. [File shares](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-encryption) provide a customer-managed encryption option similar to Block Storage for VPC volumes.





 Advantages of customer-managed encryption 

Customer-managed encryption has several advantages over IBM-managed encryption.

You control your keys:



* Because you bring your own keys (BYOK) to the cloud, you control encryption of your Block Storage for VPC volumes, file shares, and custom images.
Delete [Delete](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagedelete) the volume. You must first detach the volume from an instance before you attempt to delete it. 







 Viewing attached Block Storage for VPC volume details in instance details 

You can view information about an attached Block Storage for VPC volume from the Virtual server instance details page:



1. In the [IBM Cloud console)](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances and select an instance.
2. Under Attached block storage volumes, click the name of a volume to go to the volume details page.







 Viewing all snapshots that were created from the Block Storage for VPC volume 

If you created snapshots of a Block Storage for VPC boot or data volume, you can see the snapshots on the volume details page.



1. Go to the list of Block Storage for VPC volumes. In [IBM Cloud console)](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Select a volume from the list.
3. On the volume details page, click the Snapshots and Backups tab. A list of snapshots is displayed with the name, status, size, encryption type, and when it was created. It also shows whether the snapshot was created by the user or a [backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibaas-comparison). The snapshots display in descending order, with the most recently created snapshot in first place.
Establishing service to service authorizations 

Before you can create backup policies, you need to establish service-to-service authorizations and specify user roles. This authorization enables the Backup for VPC service to detect volume tags and create backups.



 Overview 

Every user that accesses VPC infrastructure resources must be assigned one or more access policies that define their IAM roles. These policies determine the actions that a user can perform within the context of the service or instance that you select. The allowable actions are customized and defined by the IBM Cloud® service as operations that are allowed to be performed on the service. The actions are then mapped to IAM user roles.

To use Backup for VPC to create backups of block storage volumes, you must create service-to-service authorizations and user roles:



* IBM Cloud Backup for VPC (source) to Block Storage for VPC (target) as Operator.
* IBM Cloud Backup for VPC (source) to Block Storage Snapshots for VPC (target) as Editor.
* IBM Cloud Backup for VPC (source) to Virtual Server for VPC (target) as Operator.



For more information about managing access to IBM Cloud® Virtual Private Cloud (VPC) resources, see [Getting Started with IAM](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started&interface=ui).

If you set up service authorizations incorrectly, the backup service is designed not to create backup policies. For more information, see the troubleshooting topic [Backup policy not created due to incorrect authorizations](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-troubleshoot&interface=uibaas-ts-3).





 Enabling authorization 

When you create a backup policy, the UI and APIU display a notification when service-to-service authorizations are incorrect or missing on your account. Enabling the source service to delegate its access to other dependent services automatically creates authorization policies for those services.

To manage IAM access to create the service-to-service authorization policies in the UI, follow this procedure:



1. In the IBM Cloud console, go to Manage > Access (IAM).
[Enabling Auto scale for better capacity and resiliency](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-auto-scale)Enabling Auto scale for better capacity and resiliency

This tutorial shows you how to set up compute (virtual server instance) Auto scale for horizontal scaling. You create an Auto scale instance template that defines the details of the virtual server instances that are created. After you define the template, you define instance groups to set the scaling policies that determine when and how many virtual server instances are added or removed. The instance group setup includes enabling the backend orchestration to add the newly created virtual server instances to the backend server pool for the cloud load balancer.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 45 minutes
* 2021-04-20



[Regional snapshots in 3-tier architecture](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-regional-snapshots-3-tier-arch)Regional snapshots in 3-tier architecture

Block storage snapshots can be created in IBM Cloud® VPC Gen2. You can use this feature for a backup and restore of a 3-tier application. Block storage snapshots can also be used to scale out a 3-tier system with minimal changes to your application.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 2021-06-25



[Deploying n-tier application with IBM Cloud single availability zone](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-deploy-n-tier-app-saz)Deploying n-tier application with IBM Cloud single availability zone

This tutorial walks you through setting up a resilient environment for an n-tier application in an IBM Cloud® for a single availability zone.The IBM Cloud VPC infrastructure that is created uses Intel Xeon CPUs and additional Intel technologies.
IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 60 minutes
* 2022-06-22



[Enabling Auto scale for better capacity and resiliency](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-auto-scale)Enabling Auto scale for better capacity and resiliency

This tutorial shows you how to set up compute (virtual server instance) Auto scale for horizontal scaling. You create an Auto scale instance template that defines the details of the virtual server instances that are created. After you define the template, you define instance groups to set the scaling policies that determine when and how many virtual server instances are added or removed. The instance group setup includes enabling the backend orchestration to add the newly created virtual server instances to the backend server pool for the cloud load balancer.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 45 minutes
* 2021-04-20



[Regional snapshots in 3-tier architecture](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-regional-snapshots-3-tier-arch)Regional snapshots in 3-tier architecture

Block storage snapshots can be created in IBM Cloud® VPC Gen2. You can use this feature for a backup and restore of a 3-tier application. Block storage snapshots can also be used to scale out a 3-tier system with minimal changes to your application.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

IBM Cloud Load Balancer,High availability and resiliency for infrastructure



* 2021-06-25



[Deploying n-tier application with IBM Cloud single availability zone](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-deploy-n-tier-app-saz)Deploying n-tier application with IBM Cloud single availability zone