vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [About Snapshots for VPC (Beta)](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about).

UI enhancement
: When creating or editing a VPN policy (IKE or IPsec), a new authentication option is available, SHA512. Additionally, a new Diffie-Hellman key exchange group is supported: group 19.







 February 2021 



 25 February 2021 

Dedicated hosts
: You can now use dedicated hosts to carve out a single-tenant compute node for IBM Cloud VPC in the following regions: Dallas, Washington DC, London, Tokyo, and Osaka. For more information, see [Creating dedicated hosts and groups](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances).

Application load balancer security group integration
: For enhanced security, application load balancers can now be associated with security groups. You can specify one or more security groups when you create the application load balancer, and associate security groups with your existing application load balancers. For more information, see [Integrating an IBM Cloud Application Load Balancer for VPC with security groups](https://cloud.ibm.com/docs/vpc?topic=vpc-alb-integration-with-security-groups).

UI enhancement
: On the New virtual server for VPC page, selected SSH keys persist if you leave the page and then return to it during a single logged in session. If you log out or switch your account, the selected SSH keys change.

VPC address prefixes are no longer restricted to RFC-1918 addresses
: You must now configure VPCs that use both non-RFC-1918 addresses and have public connectivity (floating IPs or public gateways) using a custom route that contains the new Delegate-VPC action. You must specify this action for destination CIDRs that are non-RFC-1918 compliant and also outside of the VPC, such as for destinations that are reachable through Direct Link, Transit Gateway, or VPC classic access.
For more information, see [Backup for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about).

The backup API is now generally available, with the exception of the backup jobs API, which remains in beta. See the [Change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log21-june-2022).

The backup jobs API is now generally available. See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log20-december-2022)







 17 May 2022 



 For all version dates 

File share replication. Accounts that have been granted special approval to preview this feature can now set up replication between a file share in one zone and a replica file share in another zone in the same region. [Using replication](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-replication) is a good way to recover from an incident at your primary site, if data becomes inaccessible or an applications fails.



* When [creating a new file share](https://cloud.ibm.com/apidocs/vpc-betacreate-share), you can now configure replication by specifying the new replica_share property. To create a replica for an existing file share, create a new share and specify the existing file share as source_share, along with the replication schedule, using the replication_cron_spec property.
* You can now [retrieve the source file share for a replica file share](https://cloud.ibm.com/apidocs/vpc-betaget-share-source). Returned information also includes the replication schedule, role, status, and status reasons.
* You can now [split the source file from a replica share](https://cloud.ibm.com/apidocs/vpc-betadelete-share-source), which removes the replication relationship between a source share and its replica share, resulting in two independent read-write file shares. This action cannot be reversed.
For shared file–level or block storage, service–provider–managed encryption at rest is available by default in select data centers or it is optional by using vSphere encryption. You must manage the necessary encryption keys.
* Enabling consistent management and governance of the deployed hybrid cloud by providing full administrative access to virtualization management, thus preserving your existing VMware tools, scripts, and investments in training.
* Using VMware expertise at global scale with IBM Professional and Managed Services spanning 40+ IBM Cloud data centers worldwide.







 Related links 



* [Design overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-design_overview)
* [Scaling capacity](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_scaling)
* [Backing up components](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_backingup)
* [Post-deployment considerations for your VMware instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_considerations)
For more information, see [Custom image lifecycle](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images&interface=uicustom-image-lifecycle) in [Getting started with custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images&interface=ui).



* available: The image can be used to create an instance.
* deprecated: The image can be used to create an instance. Using the deprecated status can discourage use of the image before the status changes to obsolete.
* obsolete: The image can't be used to create an instance.









 June 2023 



 27 June 2023 

Snapshots for VPC Cross Regional Copy (GA)
: Customers can now create a copy of a snapshot in a different region, and later use that copy to restore a volume in the new region. This feature can be beneficial in disaster recovery scenarios when the customer needs to start their virtual server instance and data volumes in a different region. Customers can also use the remote copy to create storage volumes in a new region and expand their VPC in new locations. For more information, see [Cross Regional Snapshot copies](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_crossregion_copy).

Backup for VPC Cross Regional Copy (GA)
: Customers can now save a copy of their backup in a different region. Customers can copy the backup snapshot to another region manually or add the copy option to their backup policy plans. Customers can manage and use the cross-regional copy in the target region independently from the parent volume or the original backup. For more information, see [Cross Regional backup copies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-crc).





 22 June 2023 

New Ed25519 SSH key type is available (GA)
Restoring from a bootable snapshot is slower than using a regular boot volume.

While the creation of the backup requires the volumes to be attached to a running virtual server instance, you can also restore a data volume from a snapshot of an unattached volume. Backups, like snapshots, have a lifecycle that is independent from the source Block Storage for VPC volume.

The restored volume has the same capacity and IOPS tier profile as the original volume. For more information, see [Restoring a volume from a backup snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore).





 Restoring a volume by using fast restore 

When you restore a volume by using fast restore, a fully hydrated volume is created.

You can create a [backup policy plan](https://cloud.ibm.com/docs/vpc?topic=vpc-create-backup-policy-and-plan&interface=uibackup-plan-ui) with fast restore zones, and add or remove zones later as needed. The fast restore feature caches one or more copies of a backup snapshot to the zones that you selected. Later, you can use these backup clones to create volumes in any zone within the same region.

For more information, see [Restoring a volume from a backup snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore).





 Cross-regional backup copies 

New

You can copy a backup snapshot from one region to another region, and later use that snapshot to restore a volume in the new region. You can use and manage the cross-regional snapshot in the target region independently from the parent volume or the original snapshot.

If the source snapshot is not encrypted with a customer key, the encryption of the copy remains provider-managed. If the source snapshot is protected by a customer-managed key, you must specify the customer-managed key that you want to use to encrypt the new copy.

Only one copy of the backup snapshot can exist in each region.
Key Protect <br><br> * [Snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-planning)<br> * [Block storage volume](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=ui)<br> * [File Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-planning)<br> * [Image service](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images)<br><br><br> Cloud Block Storage (server-protect) 
 Hyper Protect Crypto service <br><br> * [Snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-planning)<br> * [Block storage volume](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=ui)<br> * [File Storage](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-planning)<br> * [Image service](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images)<br><br><br> Cloud Block Storage (server-protect) 
 Virtual Server Instances <br><br> * [Auto scale](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group)<br><br><br> VPC Infrastructure Services (is) 
 Various VPC Infrastructure Services - Block Storage Volume, Security Groups, Subnets <br><br> * [IBM Kubernetes Service](https://cloud.ibm.com/docs/containers)<br><br><br> IBM Kubernetes Service (containers-kubernetes)
For more information, see [Expanding block storage volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes).

If you expand an existing data volume, be aware that existing applications will be exposed to the new updating value. To avoid disruption, first check that your applications are written to gracefully handle unexpected status values.









 24 August 2021 



 For all version dates 

Application load balancers. Use the [HTTPS redirect feature](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancershttps-redirect-listener) to redirect traffic from an HTTP load balancer listener to an HTTPS listener.

An HTTPS redirect can be configured on either [load balancer listeners](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers) or [load balancer policies](https://cloud.ibm.com/docs/vpc?topic=vpc-layer-7-load-balancing), or both. An HTTPS redirect is configured on the listener using the new https_redirect property, and will be used if none of the listener policy's rules match (or if it has no rules). An HTTPS redirect is configured on a load balancer policy using the new policy action value of https_redirect, and will be used only when all of the policy's rules match.

If you configure an HTTPS redirect on a listener policy, be aware that existing applications will be exposed to the new https_redirect value. To avoid disruption, check that your applications are written to gracefully handle unexpected action values first.

Additional API restrictions are enforced after an HTTPS redirect is configured:



* You will not be able to [update the protocol and accept_proxy_protocol properties](https://cloud.ibm.com/apidocs/vpcupdate-load-balancer-listener) of the HTTP and HTTPS listeners. Instead, delete the listener and create a new listener with the new property values.
If you use VMware Shared, your workload data exists in an IBM–managed cloud infrastructure account. You are provided with the default vSphere encryption option for your VMs, which uses IBM–managed keys that are backed by the IBM Cloud KMIP for VMware and Hyper Protect Crypto Services. You can optionally implement your own encryption solutions within your VMware workloads.





 Data storage and encryption in the VMware Shared Veeam Availability Suite service 

When you onboard to VMware Shared and order instances, you can get extra services, such as Veeam Availability Suite™, which is relevant to data storage and encryption.

The Veeam Availability Suite backup storage uses a unique scale-out backup repository (SOBR) object for each customer. The SOBR is programmatically configured for each customer, with a dedicated location on each disk and a generated backup file encryption password. The SOBR includes an extent that is backed by IBM block storage in each of the physical data centers within the specific region. For example, if the virtual data center is in Dallas 10, the SOBR has extents in Dallas 10, Dallas 12, and Dallas 13. The SOBR includes a customer-specific Cloud Object Storage bucket for more cost-effective long-term storage and as a second copy. Depending on the regions and compliance requirements of each geography, the Cloud Object Storage buckets remain in the same country, which is sometimes the same physical site.

When you decide to use the Veeam self-service portal to create backup jobs, identify which vApp and VM instances from any virtual data center in the organization participate in the backup job. Those backups are stored in the organizations SOBR.

You can manage (restore or delete) backups in the Veeam self-service portal. All backups are deleted if a virtual organization is deleted.





 Protecting your sensitive data in VMware Solutions 



 IBM Cloud Support access 

IBM Cloud Support has access to your VMware virtualization environment.



* For VMware Shared, IBM Cloud manages the virtualization environment and this access cannot be revoked.
* For vCenter Server, IBM maintains this access to enable automated Day 2 operations such as capacity expansion, and to enable support for problem resolution. For more information, see the following topics.
This is the process of migrating from a classic physical bare metal server to a bare metal or virtual server instance on VPC environment. The RackWare Management Module (RMM) solution simplifies the overall migration process of moving the operating system, applications, and data from the classic bare metal to bare metal or virtual server instance on an IBM Cloud® VPC.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+2

Transit Gateway,Building infrastructure



* 25 minutes
* 2022-12-16



[VPN into a secure private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-configuring-IPSEC-VPN)VPN into a secure private network

The need to create a private connection between a remote network environment and servers on the private network of the IBM Cloud is a common requirement. Most typically this connectivity supports hybrid workloads, data transfers, private workloads or administration of systems on the IBM Cloud. A site-to-site Virtual Private Network (VPN) tunnel is the usual approach to securing connectivity between networks.

Virtual Router Appliance



* 2023-05-05



[Linking secure private networks over the IBM network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-linking-secure-network-enclosures)Linking secure private networks over the IBM network

This tutorial presents setup of a privately routed IP connection over the IBM Cloud private network between two secure private networks hosted in different data centers. All resources are owned by one IBM Cloud account. It uses the Isolate workloads with a secure private network tutorial to deploy two private networks that are securely linked over the IBM Cloud private network using the VLAN Spanning service.

Virtual Router Appliance Virtual Servers for Classic

+1

VLANs



* 2023-05-05



[Configure NAT for Internet access from a private network](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-nat-config-private)Configure NAT for Internet access from a private network
<br><br> * Demo video: [Integrating IBM Cloud Object Storage with Hyper Protect Crypto Services](https://mediacenter.ibm.com/media/0_mgxwp16v)<br> * Instruction: [Server-side encryption with Hyper Protect Crypto Services](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-hpcs)<br><br><br> 
 [IBM Cloud Block Storage for Classic for Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about) Block Storage for Classic for VPC provides hypervisor-mounted, high-performance data storage for your virtual server instances that you can provision within your VPC. [Creating block storage volumes with customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryption) 







 Database service integrations 

The data that you store in IBM Cloud database services is encrypted by default by using randomly generated keys. If you want to control the encryption keys and use your own keys to encrypt your databases, you can associate root keys that you manage in Hyper Protect Crypto Services to your database service and leverages [envelope encryption](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-envelope-encryption) to add another layer of protection to your data. As root keys are encrypted by the master key that is owned by the user, no one else including IBM Cloud administrators can access your data.



Table 2. Supported database services

 Service Description Integration instruction 

 [IBM Cloud Databases for DataStax](https://cloud.ibm.com/docs/databases-for-cassandra) IBM Cloud Databases for DataStax is a scale-out NoSQL database service that is built on Apache Cassandra. It is designed to power real-time applications with high availability and massive scalability.
Using the [backup service](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about), you can regularly back up your volume data based on a schedule that you set up. You can create backup snapshots as frequently as 1 hour. You can also create copies of your backup snapshot in other regions. However, the backup service does not provide continual backup with automatic failover. Restoring a volume from a backup or snapshot is a manual operation that takes time. If you require a higher level of service for automatic disaster recovery, see IBM's [Cloud disaster recovery solutions](https://www.ibm.com/cloud/disaster-recovery).





 How many copies of my backup can I create in other regions? 

You can copy a backup snapshot from one region to another region, and later use that snapshot to restore a volume in the new region. Only one copy of the backup snapshot can exist in each region. You can't create a copy of the backup snapshot in the source (local) region.



* Can I use data backups for disaster recovery?

 Can I use data backups for disaster recovery? 

Using the [backup service](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about), you can regularly back up your volume data based on a schedule that you set up. You can create backup snapshots as frequently as 1 hour. You can also create copies of your backup snapshot in other regions. However, the backup service does not provide continual backup with automatic failover. Restoring a volume from a backup or snapshot is a manual operation that takes time. If you require a higher level of service for automatic disaster recovery, see IBM's [Cloud disaster recovery solutions](https://www.ibm.com/cloud/disaster-recovery).
* How many copies of my backup can I create in other regions?

 How many copies of my backup can I create in other regions? 

You can copy a backup snapshot from one region to another region, and later use that snapshot to restore a volume in the new region.
For example, setting "7" for Age retains a week's worth of backups.
4. Under Optional, you can configure two options.



* Fast snapshot restore - When you enable this feature, you must specify the zone or zones where you want [fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_fast_restore) enabled. You can also specify the maximum number of fast restore snapshots that you want to retain. Fast restore is billed at an [extra rate per hour](https://www.ibm.com/cloud/virtual-servers/pricing) for each zone in which it is enabled.
* Tagging, specify more tags that apply to the backup when the plan runs.



* Select the box to copy all tags from the source volume to all backups.
* Under Tags for backups, you can manually add any extra plan tags in this field.





5. Click Next to proceed to configure remote copies, which are optional part of the plan.



1. To create cross-regional copies of your backup, select the geography and regions where you want to have a copy. Remember, you can have only one copy per region.
2. Click the toggle to enable remote copy in the selected region.
3. If the source snapshot is encrypted by using a customer-managed key, you must select the encryption service instance and provide the key name. If you prefer, you can create a new service instance or encryption key by following the links.



* Key Protect - it can be used when the original back is encrypted by using the Key Protect service.
* Hyper Protect Crypto Services - it can be used when the original back is encrypted by using the Hyper Protect Crypto Services service.





Tags are automatically copied over from the parent backup.
6. Click Save.
7. The Summary updates automatically with the selections that you made. For example, the plan might be "Every Monday at -5:53 UTC (12:30 AM CDT) starting on 26 March 2022."
"name": "custom"
},
"resource_group": {
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/4bbce614c13444cd8fc5e7e878ef8e21",
"id": "4bbce614c13444cd8fc5e7e878ef8e21",
"name": "Default"
},
"status": "available",
"status_reasons": [],
"volume_attachments": [],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-2",
"name": "us-south-2"
}
}





 Creating a data volume from a snapshot of an unattached volume with the API 

You can specify a snapshot ID in a POST /volumes call to create a stand-alone data volume. Data is fully restored when you attach the data volume to a virtual server instance. For more information, see [About restoring a volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=uisnapshots-vpc-restore-concepts). For an example API call, see [Restoring a data volume from a snapshot of an unattached volume](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=apisnapshots-vpc-restore-unattached-api).







 Creating Block Storage for VPC volumes with Terraform 

To use Terraform, download the Terraform CLI and configure the IBM Cloud® Provider plug-in.
You can also restore a [stand-alone (unattached) data volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=apirestoring-from-an-unattached-snapshot) by using the UI, CLI, or the volumes API and specifying the snapshot ID. The volume from which the snapshot was created does not have to be attached to an instance.





 Limitations 

The following limitations apply to this release:



* You can take up to [750 snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_considerations) per volume in a region.
* You cannot take a snapshot of a volume in a [degraded state](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storage&interface=uiblock-storage-vpc-health-states).
* You can't create a copy of a snapshot in the source (local) region.
* When you create copies of a snapshot in other regions, only one copy can exist in each region. That means 9 copies globally.
* Taking a snapshot of a volume greater than 10 TB is not supported.
* You can delete any snapshot that you take. However, snapshots must be in a stable or pending state and not actively restoring a volume.
* You can delete a Block Storage for VPC volume and all its snapshots. All snapshots must be in a stable or pending state. No snapshot can be actively restoring a volume.







 Create and work with snapshots 

You can create and manage your snapshots. For more information about creating a snapshot, viewing a list of snapshots, and restoring a volume from a snapshot, see the following items.



* To use the UI, log in to the [IBM Cloud console](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create&interface=ui).