vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. On the Block Storage for VPC volume details page, select the Snapshots and Backups tab. A list of snapshots that were created manually or by backup policies is shown.
3. From the list, click the snapshot name to go to its details page.
4. From the Actions menu, click Create volume.
5. Define the new volume in the side panel. The information that you need to provide is the same as when you create a volume from the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=terraformsnapshots-vpc-restore-snaphot-list-ui). See Table 1 for the details.
6. When you're finished, click Save. The new volume is created.







 Creating a volume from a snapshot when you provision a virtual server instance in the UI 

Follow these steps to create a boot and a data volume from snapshots when you provision a new virtual server instance.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), click the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Click Create and provision your new instance. For more information about the required fields, see the table in [Creating virtual server instances in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).
You can also choose Customer Managed and use [your own encryption key](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryption). 



4. When you're finished, click Create volume. You're returned to the Block Storage for VPC volumes page, where a message indicates that the volume is being created (volume status is pending). A second message displays when the volume is created (volume status is available).
5. To see details of the new volume, select the View resource link in the second message to go to the Volume details page.







 Creating a stand-alone Block Storage for VPC volume from a snapshot in the UI 

When you [create a Block Storage for VPC volume](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-standalone-vol), you can select a snapshot and use its data to create the new volume. The snapshots that are presented are in a stable state. The data volume that is created from the snapshot is not attached to an instance and appears in the [list of Block Storage for VPC volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storage&interface=uiviewvols-ui). You can later attach the volume to an instance.

You can restore a boot volume from a "bootable" snapshot. The boot volume is restored when you create a new virtual server instance.



1. [IBM Cloud console)](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Select Create.
3. Specify the volume name, optional resource group and tags, and specify the location. You're going to use the data from a snapshot to provision the volume.
4. Under Snapshot (optional), click Select snapshot.
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/icons/action-menu-icon.svg) and selecting Add Snapshot Space.

It's important to note that VMware® environments are not aware of snapshots. The File Storage for Classic snapshot capability must not be confused with VMware® snapshots. Any recovery that uses the File Storage for Classic snapshot feature must be handled from the [IBM Cloud® console](https://cloud.ibm.com/login).

Restoring the File Storage for Classic volume requires powering off all the VMs on the File Storage for Classic. The volume needs to be temporarily unmounted from the ESXi hosts to avoid any data corruption during the process.

For more information, see the [snapshots](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-snapshots) article.





 Using replication 

Replication uses one of your snapshot schedules to automatically copy snapshots to a destination volume in a remote data center. The copies can be recovered in the remote site if a catastrophic event or data corruption occurs.

With replicas, you can



* Recover from site failures and other disasters quickly by failing over to the destination volume,
* Fail over to a specific point in time with the DR copy.



Replication keeps your data in sync in two different locations. 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.
[menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. On the Block Storage for VPC volume details page, select the Snapshots and Backups tab. A list of snapshots that were created manually or by backup policies is shown.
3. From the list, click the snapshot name to go to its details page.
4. From the Actions menu, click Create volume.
5. Define the new volume in the side panel. The information that you need to provide is the same as when you create a volume from the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=apisnapshots-vpc-restore-snaphot-list-ui). See Table 1 for the details.
6. When you're finished, click Save. The new volume is created.







 Creating a volume from a snapshot when you provision a virtual server instance in the UI 

Follow these steps to create a boot and a data volume from snapshots when you provision a new virtual server instance.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), click the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Click Create and provision your new instance. For more information about the required fields, see the table in [Creating virtual server instances in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).
* [Fail over to the replication site](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-failover&interface=ui) - The read/writes from the source file share are paused and a final copy of the file share data is pulled into the replica share. The replica share becomes read/write accessible, and a reverse replication relationship is established. The original source file share now becomes the replica share and set to read-only. The service then begins pulling data from the new source file share.

If a source file share is compromised, replica shares are a good way to recover operations. A [failover](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-failover) to a replica share assures no disruption to your services.

When you initiate the failover, you can specify what happens to the replication relationship if the failover process times out or fails. This option is commonly used when you have a time requirement for how long your file share can be offline. You must specify what you want to happen if the operation times out or if the replication fails due to the original site, which is degraded or unavailable.



* If the source site is not available due to a planned maintenance, you can choose to keep the replication relationship. The replication resumes as scheduled when the original source site is operational again.
* In a disaster recovery situation, you can choose to split the volumes to bring the replica share online as soon as possible. However, in this case, you might not have the latest data set available and you might need to manually reconcile the state in your application. Because the replication relationship is severed, you need to set up replication anew when the original site becomes operational again.



* [Remove the replication relationship](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-manage-replication) - In this case, you split the two shares apart and create two independent file shares. Both shares are read/write accessible and data is no longer synchronized between the two.
26 April 2022 | Updated: PL/Java installation

For security reasons, you can only connect through the IBM Cloud private network and ports 80 and 443 for PL/Java function installation.

22 April 2022 | Added: Service-managed cross-region backup and restore

Hyper Protect DBaaS for PostgreSQL supports service-managed cross-region backup and restore through integration with IBM Cloud Object Storage.

22 April 2022 | Updated: Frequency of automatic local backups

Hyper Protect DBaaS for PostgreSQL automatically triggers a backup of your complete databases on local storage once every 8 hours (previously every 24 hours).

3 March 2022 | Added: Changing max_prepared_transactions

One more configuration setting that you can change.

28 January 2022 | Updated: Supported cipher suites

Hyper Protect DBaaS for PostgreSQL stops supporting some weaker cipher suites in TLS connections to the service to enhance data security. Make sure that your client is configured to use only the allowed list of ciphers.

8 November 2021 | Added: Integration with the Security and Compliance Center

Hyper Protect DBaaS for PostgreSQL is integrated with the Security and Compliance Center to help you manage security and compliance for your organization.

28 October 2021 | Updated: Reduced connection delay under normal operations

Reconnection delay during the switchover off the primary node is reduced to about 5 seconds.

24 September 2021 | Added: Support for PostgreSQL 13

Hyper Protect DBaaS for PostgreSQL now supports PostgreSQL 13 and 10.

28 August 2021 | Updated: Free-plan service instances don't have automatic backups.

Free-plan service instances no longer have automatic backups.

31 July 2021 | Added: Using virtual private endpoints for VPC

If you want to connect to Hyper Protect DBaaS for PostgreSQL from your IBM Cloud Virtual Private Cloud (VPC) network, you can create and configure a virtual private endpoint (VPE) for your VPC.

8 June 2021 | Added: Using Terraform to create a service instance

Terraform is an open source software to configure and automate cloud resource provisioning and management.
--------------------



  Backup and restore 

A snapshot backup of the database is taken daily. Management and configuration of daily snapshot backups is built into the web console.

You can use the web console to restore from a snapshot backup if needed. While the restore is in progress, all writes in the system are queued, and all reads that don’t depend on the queued writes will continue. The RPO for snapshot backups is 24 hours. The RTO when restoring from a snapshot backup is 1 hour.



  IBM Cloud 

The last 7 daily snapshots are retained by default. Snapshot backups are encrypted and stored in block storage local to the Db2 Warehouse on Cloud system. Snapshot backups are free of charge.





  Amazon Web Services 

The last 7 daily snapshots are retained by default. When deployed on Amazon Web Services, you can use the web console to configure a longer retention period for snapshot backups if desired. Potentially unlimited snapshots can be retained. Snapshot backups are encrypted and stored in Amazon Web services S3. S3 keeps copies of each snapshot backup across 3 availability zones (AZs) in each region by default, so there are 3 copies of each snapshot backup in total.

With the current generation of plans, you are charged for all backups. The backup process backs up data on both block and object storage. The backup in this case includes snapshots of block storage and AWS S3 backup of object storage data.



Table 1. Snapshot backup frequency and retention period

 Cloud provider       Backup frequency  Number of retained backups                                                        Retention period                                                                                 

 IBM Cloud            1 / day           Up to 7                                                                           7 days; FIFO* rollover                                                                           
 Amazon Web Services  1 / day           Up to 7 by default. Can be configured to retain potentially unlimited backups.    7 days; FIFO* rollover by default. Can be configured to retain potentially unlimited backups.    



*First in, first out





  Logical schema backup and restore 

This feature provides the ability to do full, cumulative incremental, or delta incremental backup of a Db2 schema followed by full restore of the schema or table(s) within the schema. Logical schema backup is a flexible and lightweight way to backup and restore table level data.
* UI
* CLI
* API
* Terraform







 Replication failover 

Failover to the replica file share keeps your file share available if your source file share becomes unavailable. Failover switches the replication relationship so that the replica file share becomes the source file share and the source share becomes the read-only replica 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.



 Replication failover concepts 

When you create a replica file share, the replica pulls data from the source file share based on a replication schedule. The data on the replica file share is set to read-only. Failover switches the replication relationship. The read-only replica file share becomes the read/write source file share and the original share becomes read-only. You can now manage the share as a regular file share (for example, you can [adjust IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops)).

When you initiate a failover, you can choose what happens if the failover operation fails or times out.



* If you decide to keep the replication relationship, the system "falls back" to the source share, and the replication is in a failed status. The system attempts to replicate again at the next scheduled time. This option can be used for [routine maintenance](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-failover&interface=uifs-failover-maintenance) on the primary site or when the site is having problems. You can fall back to the original share when the maintenance is complete and the site is stable again.
* If you decide to remove the replication relationship, the system splits the two file shares apart, and they become independent read/write file shares.
Use this option when you're not sure which virtual server instance you want to attach the volume to. Or, if you want to restore data from an unattached volume that was detached from an instance.

To restore a stand-alone data volume from a snapshot, make a POST /volumes request and specify the ID, CRN, or URL of the snapshot in the source_snapshot property. The restored volume capacity (in GBs) must be at least the snapshot's minimum_capacity.

The following example request creates a 100-GB volume that is based on a 5 IOPS/GB profile. It specifies a different root key than the original snapshot. The source snapshot is specified by ID.

curl -X POST "$vpc_api_endpoint/v1/volumes/?version=2022-06-14&generation=2" -H "Authorization: $iam_token" -H "Content-Type: application/json" -d '{
"name": "volume-from-snapshot-1",
"capacity": 100,
"profile": {
"name": "5iops-tier"
},
"zone": {
"name": "us-south-1"
},
"encryption_key":{
"crn":"crn:[...]"
},
"source_snapshot:" {
"id": "bdcdc984-ba4e-4aef-84fb-e8448c3116b1"
}
}
Show more







 Restoring a volume from a snapshot with Terraform 

To use Terraform, download the Terraform CLI and configure the IBM Cloud Provider plug-in. For more information, see [Getting started with Terraform](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

VPC infrastructure services use a regional specific based endpoint, which targets to us-south by default.
When you configure a load balancer [pool](https://cloud.ibm.com/apidocs/vpccreate-load-balancer-pool) to use proxy protocol, the pool will pass information about the client to a back-end pool member when a connection is opened.

You can also configure a load balancer [listener](https://cloud.ibm.com/apidocs/vpccreate-load-balancer-listener) to accept proxy protocol information. This feature is useful when the client is, itself, a proxy (which, in turn, was connected to by the actual client) that supports the proxy protocol. This allows client information to be obtained and passed on to any pools that, themselves, have the proxy protocol enabled.

For more information, see [Enabling proxy protocol](https://cloud.ibm.com/docs/vpc?topic=vpc-advanced-traffic-managementproxy-protocol-enablement).









 5 October 2020 



 For all version dates 

Encrypted images. Use the VPC API to create your own image, encrypt it with your own key, and import it, encrypted, into IBM Cloud. After you import the image, use it like any other image. If you use the image to provision an instance, its boot volume is encrypted using the image's root encryption key or another root encryption key of your choosing.

Dive into the APIs to [import an encrypted image](https://cloud.ibm.com/apidocs/vpccreate-image) and [provision an instance](https://cloud.ibm.com/apidocs/vpccreate-instance) from that encrypted image. See also [Creating an encrypted custom image](https://cloud.ibm.com/docs/vpc?topic=vpc-create-encrypted-custom-image).







 31 August 2020 



 For all version dates 

Network load balancers.
For more information, see [Adjusting IOPS for block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-volume-iops).

Client-to-site VPN servers (Beta)
: Until now, the IBM Cloud VPN for VPC service that is supported only site-to-site connectivity, which connects your on-premises network to the IBM Cloud VPC network. This Beta adds client-to-site connectivity, which allows users to connect to their IBM Cloud VPC infrastructure through a secure or encrypted connection over the internet. This service is especially useful for individuals that are working at home, traveling, or at locations where site-to-site VPN might not be available. For more information, see [About client-to-site VPN servers](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-overview).





 24 August 2021 

HTTPS redirect listeners
: The [HTTPS redirect feature](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancershttps-redirect-listener) is now available on Application Load Balancer for VPC to redirect traffic from an HTTP load balancer listener to an HTTPS listener. You can configure an HTTPS redirect on either [load balancer listeners](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers), [load balancer policies](https://cloud.ibm.com/docs/vpc?topic=vpc-layer-7-load-balancing), or both.

Virtual server instances for VPC
: When you provision an instance, you can now allocate I/O bandwidth between storage and network bandwidth from the total instance bandwidth. The maximum bandwidth capacity is determined by the instance profile that you selected during instance provisioning. For more information, see [Bandwidth allocation for instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profiles).





 19 August 2021
A pre-formatted command for a specific backup or PITR is available in detailed view of the backup.

When restoring through the CLI, optional parameters are available. Use them to customize resources or use a Key Protect key for BYOK encryption on the new deployment.

ibmcloud resource service-instance-create <SERVICE_INSTANCE_NAME> <service-id> standard <region> <--service-endpoints SERVICE_ENDPOINTS_TYPE> -p
'{"point_in_time_recovery_deployment_id":"DEPLOYMENT_ID", "point_in_time_recovery_time":"TIMESTAMP","key_protect_key":"KEY_PROTECT_KEY_CRN", "members_disk_allocation_mb":"DESIRED_DISK_IN_MB", "members_memory_allocation_mb":"DESIRED_MEMORY_IN_MB", "members_cpu_allocation_count":"NUMBER_OF_CORES", "version":" "}'





 Recovery in the API 

The Resource Controller supports provisioning of database deployments, and provisioning and restoring are the responsibility of the Resource Controller API. You need to complete [the necessary steps to use the resource controller API](https://cloud.ibm.com/docs/databases-for-postgresql?topic=cloud-databases-provisioningprovisioning-through-the-resource-controller-api) before you can use it to restore from a backup.

Once you have all the information, the create request is a POST to the [/resource_instances](https://cloud.ibm.com/apidocs/resource-controllercreate-provision-a-new-resource-instance) endpoint.

curl -X POST https://resource-controller.cloud.ibm.com/v2/resource_instances -H 'Authorization: Bearer <>' -H 'Content-Type: application/json' -d '{
"name": "<SERVICE_INSTANCE_NAME>",
"target": "<region>",
"resource_group": "<your-resource-group>",
"resource_plan_id": "<service-id>"
[menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. On the Block Storage for VPC volume details page, select the Snapshots and Backups tab. A list of snapshots that were created manually or by backup policies is shown.
3. From the list, click the snapshot name to go to its details page.
4. From the Actions menu, click Create volume.
5. Define the new volume in the side panel. The information that you need to provide is the same as when you create a volume from the [list of snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=uisnapshots-vpc-restore-snaphot-list-ui). See Table 1 for the details.
6. When you're finished, click Save. The new volume is created.







 Creating a volume from a snapshot when you provision a virtual server instance in the UI 

Follow these steps to create a boot and a data volume from snapshots when you provision a new virtual server instance.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), click the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Click Create and provision your new instance. For more information about the required fields, see the table in [Creating virtual server instances in the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).
IBM Cloud File Storage for Classic plug-in 344 345 Added support for [private cloud service endpoints](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_clusterset-up-private-se). 
 Kernel 4.4.0-141 4.4.0-143 Updated worker node images with kernel update for [CVE-2019-6133](https://ubuntu.com/security/CVE-2019-6133.html). 
 Key Management Service provider 136 166 Updated image for [CVE-2018-16890](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16890), [CVE-2019-3822](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3822), and [CVE-2019-3823](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3823).