vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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-about&interface=apisnapshots_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.
When a backup is created, an event is triggered in Activity Tracker for the [Backup service](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events&interface=uievents-backup-service) and [Snapshots service](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events&interface=uievents-snapshots). For more information, see [Activity Tracker events](https://cloud.ibm.com/docs/vpc?topic=vpc-at-events).





 Next steps 

You can do the following actions.



* [Apply tags to your resources for backups.](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-use-policies)
* [Create more backup policies.](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create&interface=ui)
* [Restore a volume from a backup snapshot.](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore)
Block Storage for VPC data volumes can be attached to any available instance in your region, based on your customer account and permissions, and within [certain limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits). These volumes are detached by default when the instance is deleted. Detaching by default allows your data to persist beyond the virtual server instance lifecycle. It removes only the volume's association with the instance. You can delete data volumes manually after they are detached. Also, when you create data volumes, you can specify that they be [automatically deleted](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storageauto-delete) when the instance is deleted.

Detached volumes can be attached to an available, running instance without reprovisioning the volume or the instance.

When you create and attach a data volume to a virtual server instance, you can later increase the size of that volume. You indicate capacity in GB increments up to 32,000 GB capacity, depending on your volume profile. For more information, see [expanding Block Storage for VPC volume capacity](https://cloud.ibm.com/docs/vpc?topic=vpc-expanding-block-storage-volumes).

Data volumes are encrypted by default with IBM-managed encryption. You can also encrypt data volumes by using your own root keys.





 Block Storage for VPC IOPS profiles 

When you create a Block Storage for VPC volume in your availability zone, you can use 3 different tiered profiles with predefined IOPS levels and a custom profile with which you can define your own IOPS level based on the volume capacity. All profiles are backed by solid-state drives (SSDs).

For more information, see [Block Storage for VPC profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles)







 Block Storage for VPC encryption 

IBM Cloud takes the need for security seriously and understands the importance of being able to encrypt data to keep it safe.
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-about&interface=uisnapshots_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.
IBM Cloud Object Storage and resource instance ID (service credentials) Your Object Storage bucket is used to store your images and volumes during the migration process and its resource instance ID allows VPC+ Cloud Migration to access your IBM Cloud Object Storage and import the images that you want to migrate. For more information, see [IBM Cloud Object Storage getting started tutorial](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) and [Service credentials](https://cloud.ibm.com/docs/services/cloud-object-storage/iam?topic=cloud-object-storage-service-credentials). 
 (Optional) VRA (Vyatta 5600) configuration file If you want to migrate your Access Control Lists, VPN gateways, and public gateways, you need a VRA set command configuration file in txt format. JSON format is not supported. 







 Establishing connection between classic and VPC 

In some cases, resources in VPC still might need to access resources back in classic, such as databases or interprocess communication. In these cases, creating a transit gateway provides a bridge between the two environments. The VPC+ tool can help create the transit gateway, or you can create it through the IBM Cloud. If you want to learn more, see [About IBM Cloud Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-about).

Review the [Planning for IBM Cloud Transit Gateway](https://cloud.ibm.com/docs/wanclouds-vpc-plus?topic=transit-gateway-helpful-tips) information if you want to establish a connection between your VPC and classic infrastructure.

For IBM Cloud Transit Gateway use cases, check out the following information:



* [Interconnect one or more VPCs in the same MZR and an IBM classic network](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-aboutuse-case-3-interconnect-one-or-more-vpcs-in-the-same-mzr-and-an-ibm-classic-network)
Introduction to IBM Cloud VPC and HANA db backup automation on COS 

You can use Terraform to automate IBM Cloud® VPC provisioning. The VPC provisioned includes virtual server instances with high network performance. The VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers. After the VPC is provisioned, the scripts use the Ansible Playbook to install the SAP system. IBM Cloud VPC infrastructure consists of SAP certified hardware that uses Intel Xeon CPUs and additional Intel technologies.



 IBM Cloud VPC introduction 

A VPC is a public cloud offering that an enterprise uses to establish its own private cloud-like computing environment on shared [public cloud](https://www.ibm.com/cloud/public) infrastructure. VPCs give an enterprise the ability to define and control a virtual network that is logically isolated from all other public cloud tenants, creating a private, secure place on the public cloud.

Imagine that a cloud provider’s infrastructure is a residential apartment building and multiple families live inside. Being a public cloud tenant is akin to sharing an apartment with a few roommates. In contrast, having a VPC is like having your own private condominium; no one else has the key, and no one can enter the space without your permission. A VPC’s logical isolation is implemented by using virtual network functions and security features that give an enterprise customer granular control over which IP addresses or applications can access particular resources. It is analogous to the “friends-only” or “public/private” controls on social media accounts used to restrict who can or can’t see your otherwise public posts.

With IBM Cloud VPC, you can use the UI, CLI, and API to manually provision virtual server instances for VPC with high network performance. VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC. Use the following information to understand a simple use case for planning, creating, and configuring resources for your VPC, and learn about more VPC overviews and VPC tutorials.
Snapshots work as backups and are the first line of defense for data protection. While critical applications need a suite of HA and DR solutions, a non-mission critical and non-production system can rely on backup snapshots.

Snapshots can be taken both on bootable and secondary data volumes. If you experience accidental data deletion, you can create new data volumes from the backup snapshots and selected files can be copied over. If the snapshot was taken on a bootable volume, you can create another virtual server instance from the snapshot. For more information, see [Creating Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-create).





 Storage 

IBM Cloud offers different types of data storage to choose from to meet your application deployment: block, file, and object.



* Block storage data volumes can be attached to any VSI as a secondary volume and not shared with other VSIs. Block offers a range of latency depending on profile and storage hardware but provides the best IOPs and latency of the three choices. Some of the use cases include databases, caching, or mission-critical applications. You can find more information about block storage [here](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about).
* File storage is a Network File System (NFS) that allows data sharing across multiple VSIs within the same zone. Similar to block storage, you have a choice of IOPs profiles, but latency is higher because of the protocol overhead and not being local to the VSI. Some use cases include AI machine learning, media, and file sharing for collaboration. This storage is limited availability and is available only in certain regions. You can learn more about file storage [here](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).
* Object storage stores unstructured data as objects in a flat environment. Objects also include metadata (descriptive information) and a unique ID that better handles large amounts of data with limitless scalability. Data that is stored tends to be static.
File Storage for VPC
: The file service is now integrated with the Security and Compliance Center to help you manage security and compliance for your organization. For more information about this feature, see [Managing security and compliance](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-managing&interface=uifs-vpc-manage-security).





 14 February 2022 

Snapshots for VPC
: The snapshots service is now integrated with the Security and Compliance Center to help you manage security and compliance for your organization. For more information about this feature, see [Managing security and compliance](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-manage-security).





 11 February 2022 

Maximum bandwidth for each vNIC is increased
: The maximum bandwidth for a vNIC is now 25 Gbps instead of the previous 16 Gbps to 25 Gbps. For more information, see [Optimizing network bandwidth allocation for profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bandwidth-allocation-profilesnetwork-perf-notes-for-profiles).





 10 February 2022 

Block storage attachments
: Limits on the number of block storage data volumes you can attach to an instance are amended. Previously, instances that were created from smaller vCPU profiles attached only up to four data volumes. These limits are removed. For all instances, you can attach up to 12 block storage data volumes.





 08 February 2022 

Port ranges for public network load balancers
: When [creating a public network load balancer](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-ui-creating-network-load-balancer&interface=api), you can now specify a range of listener ports.

Bare Metal server support for application load balancers
: Bare Metal server members are now supported on application load balancers.
Backups are created by a schedule defined in a [backup plan](https://cloud.ibm.com/apidocs/vpc-betacreate-backup-policy-plan). Each plan also has a deletion policy for managing backups created by the plan, which you can customize by specifying the deletion_trigger sub-property. At the scheduled interval, a backup snapshot is created of that volume. You can have up to four backup plans per policy. See [Backup for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about).

The backup policy jobs API remains in [beta](https://cloud.ibm.com/apidocs/vpc-beta24-may-2022).







 29 March 2022 

The 2022-03-29 release includes incompatible changes. To avoid regressions in client functionality, be sure to read and follow the [2022-03-29 API migration guide](https://cloud.ibm.com/docs/vpc?topic=vpc-2022-03-29-migration) before specifying version 2022-03-29 or later in any API requests.



 For version 2022-03-29 or later 

Reserved IPs for compute. Using a version query parameter of 2022-03-29 or later, you can now fully control the IP addresses assigned to your network interfaces by specifying a new or existing reserved IP when you [create an instance](https://cloud.ibm.com/apidocs/vpccreate-instance) or [create a bare metal server](https://cloud.ibm.com/apidocs/vpccreate-bare-metal-server).

Migration of network interface IP addresses. In support of reserved IPs, for requests using a version query parameter of 2022-03-29 or later, the network interface primary_ipv4_address string property has been migrated to the primary_ip object property.
VPC API change log 

Read the VPC API change log to learn about updates and improvements to the IBM Cloud® Virtual Private Cloud (VPC) [API](https://cloud.ibm.com/apidocs/vpc). The change log lists changes that are ordered by the date they were released. Changes to existing API versions are designed to be compatible with existing client applications.

By design, new features with backward-incompatible changes apply only to version dates on and after the feature's release. Changes that apply to older versions of the API are designed to maintain compatibility with existing applications and code. If backward-incompatible changes require non-trivial client code changes to use an API version, the API change log might provide links to instructions, tips, or best practices for updating client code.

Some changes, such as new response properties or new optional request parameters, are considered backward compatible. Other changes, such as new required request parameters, are not considered backward compatible. To avoid disruption from changes to the API, use the following best practices when you call the API:



* Catch and log any 4xx or 5xx HTTP status code, along with the included trace property
* Follow HTTP redirect rules for any 3xx HTTP status code
* Consume only the resources and properties your application needs to function
* Avoid depending on behavior that is not explicitly documented



SDK changes are based on API changes. For information about the latest changes to the VPC SDKs, see the change logs in the SDK repositories:



* [Java SDK change log](https://github.com/IBM/vpc-java-sdk/blob/master/CHANGELOG.md)
* [Node SDK change log](https://github.com/IBM/vpc-node-sdk/blob/master/CHANGELOG.md)
* [Python SDK change log](https://github.com/IBM/vpc-python-sdk/blob/master/CHANGELOG.md)
* [Go SDK change log](https://github.com/IBM/vpc-go-sdk/blob/master/CHANGELOG.md)
VPC+ Cloud Migration allows you to discover and choose resources for migration, create, and set up those resources in your VPC environment. You can also run and manage your VPC environment from within the tool.

You can migrate the following key elements of IBM Cloud classic infrastructure to VPC:



* Subnets
* Virtual server instances
* Dedicated hosts
* Storage volumes (primary and secondary)
* Security groups
* Load balancers
* Firewall (ACL) configuration
* VPN configuration
* SSH keys
* Public gateway



For more information, see [Getting started with VPC+ Cloud Migration](https://cloud.ibm.com/docs/cloud-infrastructure?topic=wanclouds-vpc-plus-getting-started-tutorial).





 RMM 

RackWare Management Module (RMM) is a third-party solution, provided by RackWare, that provides an automated, easy, and convenient process to migrate existing compute workloads to IBM Cloud. It lets you create an exact duplicate of a running source image without the burden of rebuilding or re-creating template images and applications. Migrating large, complex environments through a simple intuitive user interface and automated tasks reduces the time that is required from weeks to days. It keeps track of data changes on source until cutover and performs delta syncs to the target server in IBM Cloud. Additionally, it helps you with automated wave planning for migrations that can be further customized.



 Classic to classic infrastructure migration 

You can use RMM solution to simplify the overall bare metal to bare metal migration process. The solution simplifies the process by moving the operating system, applications, and data from one bare metal server to another bare metal server in the IBM Cloud classic environment. The migration can occur either over the public or private interface of the compute resource.

Zoom

![Topology](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/cloud-infrastructure/images/p-p_classic_private_ip_routing2.svg)

Figure 2.
Virtual Private Cloud overview 

The IBM Cloud® Virtual Private Cloud is a virtual network that is linked to your customer account. It gives you cloud security, with the ability to scale dynamically, by providing fine-grained control over your virtual infrastructure and your network traffic segmentation.

Each VPC is deployed to a single region. Within that region, the VPC can span multiple zones.

IBM Cloud virtual or IBM Cloud bare metal server presented in your VPC is attached to subnets. Subnets within the VPC offer private connectivity, thus your servers can communicate within and between the subnets by using an implicit router. Subnets in your VPC can connect to the public internet through an optional public gateway, or you can assign floating IP addresses to any network interface of the servers.

The following diagram shows an overview of IBM Cloud VPC.

Zoom

![IBM VPC connectivity and security](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/vpc-ryo-diagrams-overview-virtual.svg)

Figure 1. IBM Cloud VPC connectivity and security

Review the following concepts to understand how IBM Cloud VPC is constructed. The terminology is used throughout this architecture solution.

A region is an abstraction that is related to the geographic area in which a VPC is deployed. Each region contains multiple zones, which represent independent fault domains. A VPC can span multiple zones within its assigned region. A region is also often referred to a multizone region or MZR.

A zone is an abstraction that refers to the physical data center, which hosts the compute, network, storage resources, and the related cooling and power, which provides services and applications. Zones are isolated from each other, so to create no shared single point of failure, improved fault tolerance, and reduced latency. Each zone is assigned a default address prefix, which specifies the range of addresses in which subnets can be created.
The workload VPC should be created in the same MZR as the management VPC.





 Connectivity to workload VPC 

If the consumer is in the same organization as the application provider, then just like for the management VPC, Direct Link can provide access to the workload VPC. Alternatively, VPN for VPC can be used for site-to-site VPN connectivity.





 Storage and encryption 



 Block Storage for VPC 

Block Storage for VPC is automatically created for the primary book volume when you create a virtual server. You can also create more data volumes by using Block Storage for VPC within any subnet.

By default, all boot and data volumes are encrypted at rest with IBM-managed encryption. There is no additional cost for this service. IBM-managed encryption uses the following industry standard protocols:



* AES-256 encryption
* Keys are managed in-house with Key Management Interoperability Protocol (KMIP)



For all sensitive and consumer-owned data, the application provider should use customer-managed encryption. With this encryption method you can bring your own customer root key (CRK) to the cloud or have a key management service (KMS) generate a key for you. For IBM Cloud for Financial Services, the supported key management service is [Hyper Protect Crypto Services (HPCS)](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-overview). Root keys encrypt volume and custom image passphrases with envelope encryption, a process that encrypts a key with another key.





 Object Storage 

[Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage) is an alternative storage option that is useful for certain use cases, including backup and recovery, data archiving, cloud-native application building, and AI and big data analytics. Object Storage stores encrypted and dispersed data across multiple geographic locations.

By default, all objects that are stored in Object Storage are encrypted by using randomly generated keys and an all-or-nothing-transform (AONT).