vania-janet/multiturn-rag-retrieval-data huggingface dataset:
By 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. However, the backup service does not provide continual backup with automatic failover, and 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).





 What is restoring a volume from a snapshot? 

Restoring from a snapshot creates a new, fully provisioned boot or data volume. You can restore storage volumes during instance creation, instance modification, or when you provision a new stand-alone volume. For data volumes, you can also use the volumes API to create a data volume from a snapshot. For more information, see [Restoring a volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore).

For best performance, you can enable snapshots for fast restore. By using the fast restore feature, you can create a volume from a snapshot that is fully provisioned when the volume is created. For more information, see [Snapshots fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_fast_restore).





 Can I add tags to a volume? 

Yes, you can add user tags and access management tags to your volumes. User tags are used by the backup service to automatically create backup snapshots of the volume. Access management tags help organize access to your Block Storage for VPC volumes. For more information, see [Tags for Block Storage for VPC volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-about&interface=uistorage-about-tags).







 Performance questions
Encryption Provider-managed or customer-managed encryption. For customer-managed encryption, the KMS instance, root key name, and root key ID are shown. 
 Fast restore panel Use [fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_fast_restore) to create a volume from this snapshot that is fully provisioned. Click edit to [enable fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-edit-fast-restore) in a zone. 
 Actions menu [Create a volume from the snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restoresnapshots-restore-create-vol-ui), [Edit fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-managesnapshots-edit-fast-restore), or delete a snapshot. 









 Viewing snapshots from the CLI 

You can use the CLI to list all snapshots, all snapshots for a volume, and details about a particular snapshot.



 Before you begin 

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



1. Log in to IBM Cloud®.

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

This command returns a URL and prompts for a passcode. Go to that URL in your browser and log in. If successful, you get a one-time passcode. Copy this passcode and paste it as a response on the prompt. After successful authentication, you are prompted to choose your account.
* When you create an unattached (stand-alone) Block Storage for VPC volume from a snapshot, you can still attach the volume to an instance later.







 Limitations of restoring a volume from a snapshot 

The following limitations apply when you restore a volume from a snapshot.



* To restore a volume, the snapshot must be in a stable state.
* You can delete the new volume at any time. However, you can't delete the snapshot from which the volume is restored from unless the hydration is complete or the volume is deleted.
* If snapshot is protected with customer-managed encryption and you don't specify a different root key CRN, the restored volume is encrypted with the snapshot's encryption key. The encryption cannot be changed later.
* When the new volume is created, data restoration begins immediately, but performance is degraded until the volume is fully hydrated.





 Performance impact 

The performance of boot and data volumes is initially degraded when data is restored from a snapshot. Performance degradation occurs during the restoration because your data is copied from IBM Cloud® Object Storage to Block Storage for VPC in the background.

At first, the restored volume appears as pending or degraded, and the service begins pulling data from the snapshot that is stored in Object Storage. While the data is restoring, the volume's health state is monitored by the volume resource. If the volume that was created from snapshot is attached to an instance before its data is fully restored, volume hydration pauses on the service node and continues on the compute node. If the volume is detached while the hydration is in progress, the hydration pauses on compute node and continues on the storage node. You cannot delete a snapshot that is used to hydrate a volume. After the restoration process is complete, you can realize full IOPS on the new volume.

Volumes that are restored from fast restore clones don't require hydration. The data is available as soon as the volume is created. However, to achieve the best performance and efficiency when you provision multiple instances, boot from an existing image. Custom images that you provide are better than stock images for this purpose. Images have a maximum size of 250 GB.







 Restoring a volume with fast restore
* UI
* CLI
* API
* Terraform







 Restoring a volume from a snapshot 

Restoring data from a snapshot creates a new, fully provisioned volume that you can use to start an instance or attach as auxiliary storage. You can restore boot and data volumes during instance creation or when you modify an existing instance. You can also restore a data volume from a snapshot of a volume that is not attached to an instance. Volumes can be restored from snapshots that were created manually or by a backup policy. You can restore volumes from fast restore clones and cross-regional copies of snapshots, too. You can create volumes from snapshots in the UI, from the CLI, with the API, or Terraform.



 About restoring a volume from a snapshot 

Restoring a volume from a snapshot creates a boot or data volume, depending on whether the snapshot is bootable or nonbootable.



* Restoring from a bootable snapshot creates a boot volume that you can use to start a virtual server instance. The boot volume uses a general-purpose profile and is limited to 250 GB.
* A new data volume that was created from nonbootable snapshot inherits its properties from the original volume, such as [profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles), capacity, data, and metadata. If the source volume used [customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutvpc-customer-managed-encryption), the volume inherits that encryption with the original customer root key (CRK). However, you can specify a larger volume size, different IOPS profile, and different CRK if you prefer.



You can restore volumes from a manually created snapshot or from a snapshot that was created by a backup policy. This type of snapshot is called a backup. For more information, see [Restoring a volume from a backup snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore).
For more information, see [Tags for Block Storage for VPC snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about&interface=uisnapshots-about-tags).
* Can I use volume snapshot for disaster recovery?

 Can I use volume snapshot for disaster recovery? 

You can use your snapshots and backups to create volumes in case of an emergency. You can also create copies of your snapshot in other regions and use them to create volumes there. However, the snapshot and ackup services do 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 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 snapshot can exist in each region. You can't create a copy of the snapshot in the source (local) region.
* Can I map IBM Cloud services to a VPE from the service catalog?

IBM Cloud services cannot be mapped to a VPE from the service catalog during the time of purchase.
* Can I map an IBM Cloud service to a Public endpoint?

Public endpoints of IBM Cloud services are not eligible for VPE. VPE can be mapped only to a private endpoint of IBM Cloud services.
* Is a VPE created in high-availability mode?

A VPE is not created in high-availability (HA) mode, by default. HA comes primarily from the IBM Cloud service.
* Can I access an IBM Cloud service by using a private service endpoint IP address?

When an IBM Cloud service is created, IBM Cloud DNS Services are automatically set up to resolve the IBM Cloud service FQDN to the IBM Cloud private service address.
VPC Instance Metadata API change log 

Read the API change log to learn about updates and improvements to the IBM Cloud® Virtual Private Cloud (VPC) [Instance Metadata API](https://cloud.ibm.com/apidocs/vpc-metadata). 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





 27 June 2023 



 For all version dates 

Extended SSH key encryption. The type property now includes ed25519 when [listing](https://cloud.ibm.com/apidocs/vpc-metadatalist-keys) and [retrieving](https://cloud.ibm.com/apidocs/vpc-metadataget-key) public SSH keys. For more information, see [Getting started with SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys&interface=api). See also [Extended SSH key encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log27-june-2023) in the VPC API change log.







 14 February 2023 



 For all version dates
For more information about this service, 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).





 10 June 2022 

Block Storage for VPC
: You can use the volumes API to restore an unattached data volume from a snapshot. Restoring from a snapshot creates a new, fully provisioned volume. The data volume that was created from the snapshot is fully hydrated (data is restored) when you later attach it to an instance. For more information, see [Restoring an unattached data volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=apisnapshots-vpc-restore-unattached-vol).





 01 June 2022 

File Storage for VPC
: For accounts authorized to preview this service, you can increase or decrease file share IOPS to meet your performance needs. Adjust IOPS within an IOPS tier profile or a custom profile. Or, adjust IOPS between profiles, for example, from a 3 IOPS/GB tiered profile to a custom profile. Adjusting IOPS within a profile or between profiles depends on the file share size. For more information, see [Adjusting file share IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops).







 May 2022 



 27 May 2022 

Secrets Manager for application load balancers
: Application load balancers now support [IBM Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-getting-started). With Secrets Manager, you can create, lease, and centrally manage secrets that are used in IBM Cloud® services or your custom-built applications.
: As a reminder, end of support for IBM Cloud Certificate Manager was 31 December 2022. Remaining instances of Certificate Manager have been deleted.
Restoring a volume from a snapshot creates an entirely new boot or data volume. The new volume has the same properties of the original volume, including encryption. If you restore from a bootable snapshot, you create a boot volume. Similarly, you can create a data volume from a snapshot of a data volume. The volume that you create from the snapshot uses the same volume profile and contains the same data and metadata as the original volume. You can restore a volume when you provision an instance, update an existing instance, or create a stand-alone volume by using the UI, CLI, or the volumes API. For more information, see [Restoring a volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore).

For best performance, you can enable snapshots for fast restore. By using the fast restore feature, you can create a volume from a snapshot that is fully provisioned when the volume is created. For more information, see [Snapshots fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_fast_restore).



 I restored a Block Storage for VPC volume from a snapshot, and it's not performing at the expected levels. Is this normal? 

Performance of boot and data volumes is initially degraded when data is restored from a snapshot. Performance degradation occurs during the restoration because your data is copied from IBM Cloud® Object Storage to Block Storage for VPC in the background. After the restoration process is complete, you can realize full IOPS on the new volume.

Volumes that are restored from fast restore clones do not require hydration. The data is available as soon as the volume is created.



* I restored a Block Storage for VPC volume from a snapshot, and it's not performing at the expected levels. Is this normal?

 I restored a Block Storage for VPC volume from a snapshot, and it's not performing at the expected levels. Is this normal? 

Performance of boot and data volumes is initially degraded when data is restored from a snapshot.
Change log: IBM Cloud Security Best Practices 

The IBM Cloud Security Best Practices library is a collection of controls and goals that meet IBM Cloud and industry best practices. The library is consistently updated and can change at any time, which can cause your compliance score to change without any update to your configuration. When new controls or specifications are edited or removed from the library in a way that is not compatible with the current version, a new version is released.



 Profile versioning 

When goals or controls are edited, removed from, or added to a profile in a way that is not compatible with the current version, a new minor version is released. To take advantage of the changes in a new version, update your scans to use the newest profile version.

This profile is consistently updated and is not an exhaustive list of all the controls that might be required for every organization. Users can validate the available goals and determine where a need to supplement their workloads with other security measures exists.



 Active versions 

The following table shows the service behavior changes for each version date. Switching to a later version date activates all changes that are introduced in earlier versions.



Table. Active versions of the IBM Cloud Security Best Practices profile

 Version number Release date 

 Version 1.2.0 2023-06-20 
 Version 1.1.0 2023-04-17 
 Version 1.0.0 2022-12-14 









 Version 1.2.0 

The following changes have been made to the IBM Cloud Security Best Practices library and profile.



Table. Rule updates for the IBM Cloud Security Best Practices profile version 1.2.0

 Rule Associated controls Update 

 Check whether Virtual Private Cloud (VPC) network access control lists don't allow ingress from 0.0.0.0/0 to SSH port 4.43 The rule was removed. 
 Check whether Virtual Private Cloud (VPC) network access control lists don't allow ingress from 0.0.0.0/0 to RDP port 4.44 The rule was removed. 
 Check whether Virtual Private Cloud (VPC) security groups have no inbound rules that specify source IP 0.0.0.0/0 to SSH port 4.4 The rule was removed.
The volume's data is fully restored later, when you attach it to an instance. Volume performance is initially degraded until the volume data is fully restored. For more information, see [Restoring an unattached data volume from a snapshot with the API](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=apisnapshots-vpc-restore-unattached-api).

Cross-zone member support for network load balancers. You can now [create a load balancer pool](https://cloud.ibm.com/apidocs/vpc/latestcreate-load-balancer-pool) with members across any zone in the region. You can also use the [create pool member](https://cloud.ibm.com/apidocs/vpc/latestcreate-load-balancer-pool-member) and [replace pool member](https://cloud.ibm.com/apidocs/vpc/latestreplace-load-balancer-pool-members) methods to update an existing pool with members across any zone in the region. The zone of the network load balancer is still identified by the subnet that you specify when you create a load balancer.

Network load balancers with route_mode enabled do not support cross zone members.







 21 June 2022 



 For all version dates 

Backup for VPC. You can now create backup policies to schedule automatic backups of your block storage volumes. Backups are made when a user tag in a block storage volume matches a user tag defined in a backup policy. 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.
* Mount file shares on Red Hat, CentOS, or Ubuntu Linux distributions.



For more information, see [About File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).





 Snapshots for VPC 

Snapshots for VPC are a regional offering that creates a point-in-time copy of your block storage boot or data volume that you manually create. The initial snapshot that you take is a full backup of the volume. Subsequent snapshots of the same volume are incremental; only the changes since the last snapshots are captured.

You can select a snapshot during instance provisioning, and restore a new, fully provisioned boot volume to start the instance. You can also create and attach a data volume from a snapshot within a running virtual server instance.

Snapshots have a lifecycle that is independent of the source block storage volume. You can delete the original volume and the snapshot persists. Snapshots inherit encryption from the source volume.

You can create, list, view details, and manage snapshots from the UI, CLI, and API.

For more information, see [About Snapshots for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about).





 Instance storage 

Instance storage is allocated from one or more local SSDs on the server that is hosting the instance. An instance storage disk provides fast, affordable, temporary storage to improve the performance of cloud native workloads with scratch space, caching buffers, or a place for replicated data.

Data that is stored on instance storage is tied directly to the instance lifecycle and is only held temporarily. The instance storage disk is automatically created and destroyed with the instance. However, instance storage data is not lost when an instance is rebooted. For more information, see [About instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage).





 Backup for VPC
For more information, see [Creating Block Storage for VPC volumes with customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryption). 
 Encryption Instance Optional. A link to the provisioned KMS instance for a customer-managed encryption volume. 
 Key Optional. The name and copiable ID of the root key that is used to encrypt the passphrase, which secures a customer-managed encryption volume. 
 Backup policies The number of backup policies that are associated with the volume. Click the number link to go to the backup policies tab. 
 Snapshots The number of snapshots that were created of the volume. Click the number link to go to the Snapshots and Backups tab. 
 Attached virtual server Volumes attached to a virtual server instance are listed here. Click Attach to select an instance to attach this volume. For more information, see [Attaching a volume to an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storage). 
 Status Tracks the overall lifecycle state of the volume, which ranges from volume creation to volume deletion. Attachment status, for example, attached when the volume is attached to an instance and attaching when in progress. 
 Name Click the name of the virtual server instance to see instance details. 
 Auto delete When enabled, the volume is automatically deleted when you delete the instance. Click the toggle to enable automatic deletion. 
 Backup policies Shows backup policies that are associated with this volume. To associate backup policies, you can add a backup policy's tags for target resources to this volume. Click Apply to select a backup policy, then apply its tags for the target resource to the volume. 



Table 4 shows Actions menu options from the volume details page.



Table 4. Actions menu options one the volume details page.

 Action Description 

 Create snapshot Create a snapshot from a data volume or a "bootable snapshot" from a boot volume. Data volumes must be attached to a virtual server instance.