vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The instance must be in a running state.
3. On the Instance details page, scroll to the list of Storage volumes and click Attach volumes. A side panel opens for you to define the volume attachment.
4. From the Attach storage volume panel, expand the list of Block Volumes, and select Create a data volume.
5. Select Import from snapshot. Expand the Snapshot list and select a snapshot.
6. The snapshot contains the properties of the original source volume, including the auto-delete status, tags, profile, and encryption. You can change all these properties. Keep in mind that you can change the volume name, profile, size, and IOPS later, but you cannot change encryption type or CRK after the volume is created.
7. Select a unique name, specify the size, and click Save. The data volume information is added in the Data volume list.
8. Click Save. The side panel closes and messages indicate that the restored volume is being attached to the instance. The new volume appears in the list of Storage volumes. Hover over the camera icon to see the name of the snapshot from which it was created.









 Restoring a volume from a snapshot from the CLI 

During the "create and attach" phase of instance provisioning, you can select a snapshot to restore the volume. Restoring from a bootable snapshot creates a boot volume that you cab use to provision a virtual server instance. The boot volume uses a general-purpose profile and is limited to 250 GB. Data volumes are created and can be attached to the instance. You can restore volumes from a snapshot outside of instance provisioning as well, you can create stand-alone volumes and new auxiliary volumes for existing instances.



 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®.
You can restore a volume from a backup snapshot of a boot volume in multiple ways.



* You can restore a boot volume when you provision an instance to start the new instance.
* You can restore a boot volume as a stand-alone volume, and use it later to start a new instance. The restoration process starts when the boot volume is attached to the instance.







 Restoring from a nonbootable backup 

You can restore a volume from a backup snapshot of a data volume in multiple ways.



* You can restore a data volume when you provision an instance. During provisioning, you can select a nonbootable backup snapshot to create a data volume hat is then attached to the instance as auxiliary storage.
* You can restore a data volume when you want to add more storage to an existing instance.
* You can restore a data volume to create a stand-alone volume, which you can attach to an instance later.









 Restoring a volume from a backup snapshot in the UI 

Restoring a volume from a backup snapshot in the UI creates a fully provisioned boot or data volume. You can restore a volume from the list of Block storage snapshots and from the snapshot details page.

You can restore a volume from a backup snapshot in the following ways.



* When you [provision an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore&interface=uibaas-vpc-restore-vol-ui), specify a snapshot of a boot or data volume. Data volumes are automatically attached to the instance as auxiliary storage. Use the restored boot volume to start the new instance.
* From a snapshot of a [previously created volume](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restore&interface=uibaas-vpc-create-from-vol-ui). The created volume from snapshot is automatically attached to the instance as auxiliary storage.
In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Backup policies. The Create tab is selected by default.

The UI diplays a notification message when service-to-service authorizations are incorrect or missing on your account.

If your account doesn't allow for the required service-to-service authorizations and user access roles to create a backup policy, [contact IBM support](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-help&interface=ui) for help.
2. Enter information for each section of the provisioning form. Optionally create a backup plan for the policy.



Table 2. Backup policy provisioning selections

 Field Description 

 Location Select the location where you want to create the backup policy. 
 <br><br> * Geography<br><br><br> Select the appropriate value from the list of available geographies. 
 <br><br> * Region<br><br><br> Select the appropriate value from the list of available regions in the selected geography. 
 Details Enter details to define the policy. A policy defines what volumes are backed up. 
 <br><br> * Name<br><br><br> Provide a unique name for your backup policy that easily identifies the policy. Standard naming conventions apply to policies, plans, and backups. For example, see the [naming conventions for Snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage&interface=uisnapshots-vpc-naming). 
 <br><br> * Resource group<br><br><br> Optionally, specify a resource group for your policy. It can't be changed after you enter it.
<br><br> * Zone<br><br><br> Inherited from the snapshot. 
 <br><br> * Auto-delete<br><br><br> Inherited from the snapshot. 
 <br><br> * Size<br><br><br> Enter a volume size allowed by the profile. The default is the minimum provisioning size based on the snapshot. 
 Profile Defaults to the snapshot's IOPS tier or custom profile. You can change the profile. 
 <br><br> * IOPS<br><br><br> For IOPS tiers, specify IOPS tier profile. For custom IOPS, select a range. 
 <br><br> * Size<br><br><br> Enter a volume size allowed by the profile. The default is the minimum size required. 
 Encryption Inherited from the snapshot. If the encryption is provider-managed, you can change it to customer-managed encryption and select either Key Protect or Hyper Protect Crypto Services. If the encryption is already customer-managed, you can choose a different key management service but not to provider-managed encryption. 



5. When you're finished, click Save. The new volume is created.



Hover over the name of a volume that is attached to an instance in the instance details. The text shows whether the volume was created from a backup or regular snapshot.





 Creating a volume from the snapshot details page 

Use the following steps to create a volume from the snaphots details page.



1. Go to the list of Block Storage for VPC volumes. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block Storage for VPC snapshots.

You can go to the backup snapshots details page in other ways.
For more information, see [Create a stand-alone Block Storage for VPC volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storage&interface=clicreate-vol-from-snapshot-cli).

For more information about available command options, see [ibmcloud is volume-create](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencevolume-create).







 Restoring a volume from a snapshot with the API 

Use the VPC API to restore a volume from a snapshot. During the "create and attach" phase of instance provisioning, you can select a snapshot to restore the volume. Restoring from a bootable snapshot with the API is not supported.



 Creating a boot volume when you provision an instance with the API 

To restore a boot volume from a bootable snapshot when you create an instance, make a POST /instances request and specify the boot_volume_attachment property and the bootable snapshot ID in the source_snapshot subproperty.

See the following example.

curl -X POST "$vpc_api_endpoint/v1/instances?version=2023-03-07&generation=2" -H "Authorization: $iam_token" -H "Content-Type: application/json" -d '{
"name": "my-server-name",
"zone": {
"name": "us-south-1"
},
"vpc": {
"id": "4d27c489-8ad7-3c18-cbf4-2103d9f8da93"
},
"profile": {
"name": "cx2-2x4"
},
"primary_network_interface": {
"name": "region1example-net1",
"subnet": {
"id": ""
}
},
"boot_volume_attachment": {
"attach_user_tags": [
"my-daily-backup-plan"
],
"copy_user_tags": true,
"created_at": "2022-04-22T22:51:31.303Z",
"cron_spec": "/5 1,2,3 * * ",
"deletion_trigger": {
"delete_after": 20
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/8758bd18-344b-486a-b606-5b8cb8cdd044/plans/4cf9171a-0043-4434-8727-15b53dbc374c",
"id": "4cf9171a-0043-4434-8727-15b53dbc374c",
"lifecycle_state": "stable",
"name": "my-backup-plan",
"resource_type": "backup_policy_plan"
}
Show more





 Creating a backup plan with fast restore option with the API 

When you create a backup plan for an existing policy, you can specify that clones of backup snapshots are created. Because these clones are created in different zones in your region, you can quickly restore a fully provisioned volume. For more information about this option, see [Restoring a volume by using fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=uisnapshots-vpc-use-fast-restore).

Make a POST /backup_policies/{backup_policy_id}/plans request to create a backup plan for the policy that is identified by ID. Specify the clone_policy property and zones subproperty to indicate which zone in your region you want to create the backup snapshot clone. The zone must be different than your source zone. You can specify multiple zones.
A side panel displays for creating a new data volume.



1. Select Import from snapshot. Expand the list to select a data snapshot. The most recent data snapshot is selected by default. Optionally, select a different snapshot from the list. The snapshot contains the properties of the original source volume, including the IOPS tier and encryption.
2. Optionally, change the size of the volume.
3. Click Save. The new data volume is created from the snapshot. It is attached to the instance, and shown in the Data volume list.



5. When you're finished provisioning your new instance, click Create virtual server instance. The new instance appears in the list of virtual server instances.



After the instance is created, you can click the instance name to see the instance details. The boot volume that you restored from the backup snapshot is listed under Storage volumes. The camera icon indicates that the volume was created from a snapshot.





 Creating a data volume from a backup snapshot for an existing virtual server instance 

You can create a data volume from a snapshot for an existing instance. Choose from the list of virtual server instances.



1. In the [IBM Cloud console](https://cloud.ibm.com/login), go to the menu ![menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. From the list, click the name of an instance. The instance must be in a Running state.
3. On the Instance details page, scroll to the list of Storage volumes and click Attach volumes. A side panel opens for you to define the volume attachment.
4. From the Attach data volume panel, expand the list of Block volumes, and select Create a data volume.
5. Select Import from snapshot. Expand the Snapshot list and select a backup snapshot.
6.
* You can restore a boot volume when you provision an instance to start the new instance.
* You can restore a boot volume as a stand-alone volume, and use it later to start a new instance. The restoration process starts when the boot volume is attached to the instance.







 Restoring from a nonbootable backup 

You can restore a volume from a backup snapshot of a data volume in multiple ways.



* You can restore a data volume when you provision an instance. During provisioning, you can select a nonbootable backup snapshot to create a data volume hat is then attached to the instance as auxiliary storage.
* You can restore a data volume when you want to add more storage to an existing instance.
* You can restore a data volume to create a stand-alone volume, which you can attach to an instance later.









 Restoring a volume from a backup snapshot in the UI 

Restoring a volume from a backup snapshot in the UI creates a fully provisioned boot or data volume. You can restore a volume from the list of Block storage snapshots and from the snapshot details page.

You can restore a volume from a backup snapshot in the following ways.



* When you [provision an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restorebaas-vpc-restore-vol-ui), specify a snapshot of a boot or data volume. Data volumes are automatically attached to the instance as auxiliary storage. Use the restored boot volume to start the new instance.
* From a snapshot of a [previously created volume](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restorebaas-vpc-create-from-vol-ui). The created volume from snapshot is automatically attached to the instance as auxiliary storage.
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. 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. If your VPC is created in another region, make sure to target the right region in the provider block in the provider.tf file.

See the following example of targeting a region other than the default us-south.

provider "ibm" {
region = "eu-de"
}

Valid volume names can include a combination of lowercase alpha-numeric characters (a-z, 0-9) and the hyphen (-), up to 63 characters. Volume names must begin with a lowercase letter. Volume names must be unique across the entire VPC infrastructure. For example, if you create two volumes with the same name in the same account and region, a "volume name duplicate" error is triggered.



 Creating stand-alone Block Storage for VPC volumes with Terraform 

To create a Block Storage for VPC volume, use the ibm_is_volume resource. The following example creates a volume with 4 TB capacity and the 10iops-tier performance profile.

resource "ibm_is_volume" "example" {
name = "example-volume"
profile = "10iops-tier"
zone = "us-south-1"
capacity = 4000
}

The following example creates a volume with a custom profile. The volume that is created has 200 MB capacity and can perform 1000 IOPS.
(The created_at property indicates when the [snapshot creation](https://cloud.ibm.com/apidocs/vpccreate-snapshot) process was initiated.)

If captured_at is absent from the response, the snapshot's data has not yet been captured. Additionally, the property may be absent for snapshots created before 1 January 2022.







 23 November 2021 



 For all version dates 

Snapshots for VPC. Restrictions have been removed for deleting snapshots. You can now [delete](https://cloud.ibm.com/apidocs/vpcdelete-snapshot) any snapshot in the chain of snapshots. If the snapshot is actively being used to restore a volume, the snapshot will remain in deleting until the restore completes. The deletable property, which indicated whether a snapshot could be deleted, has been deprecated.







 19 October 2021 



 For all version dates 

GPU instances. Updated instance and instance profile methods now include details about GPUs attached to the instance. New profiles provide support for GPUs. These GPUs provide accelerated computing to help you run workloads with more powerful compute capabilities.

The [list all instances](https://cloud.ibm.com/apidocs/vpclist-instances) method returns a new gpu property with additional sub-properties: count, manufacturer, model, and memory. The [retrieve an instance profile](https://cloud.ibm.com/apidocs/vpcget-instance-profile) method returns new properties: gpu_count, gpu_manufacturer, gpu_model, and gpu_memory. For more information, see [Managing GPUs](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-gpus).







 28 September 2021 



 For all version dates 

Route mode for VNF support for network load balancers.
All resources are configured.<br><br><br><br> * VPC<br> * Subnet<br> * Security Group<br> * ALB LBaaS<br> * web VSI + host placement groups<br> * Private LBaaS<br> * App VSI + host placement groups<br> * DB VSI + secondary block volumes + power placement groups<br> * Instance group<br> * Public or Private (web LBaaS)<br><br><br> 
 Features The optional features for a multi-zone region infrastructure. You can select as many as you need.<br><br><br><br> * Autoscale<br> * Cloud Object Storage<br> * Public Gateway<br> * VPN<br><br><br> 







 What is created 

A VPC is a private space in IBM Cloud where you can run an isolated environment with custom network policies. The variables that you define are used by the scripts to provision the virtual private cloud infrastructure resources for you. The default values in the scripts are used to create these resources in a multi-zone region:



 Resource Name Quantity 

 VPC 01 
 Security Groups 05 
 Subnets 10 
 Bastion VSI 01 
 App VSI 05 
 Web VSI 05 
 Database VSI 06 
 Floating IP 01 



The scripts use variables to specify your account information, VSI server information, Load Balancer information, Auto scale, and Anti-Affinity

The scripts automatically install these software packages:



* PHP
* Apache
* MariaDB
* Word Press Application







 Caveats 

The bastion server is important to access other VSIs.

Don’t delete the bastion server or update its OS image after creation (Apply plan) because the bastion server is used to access other servers. If the Bastion server is removed, you lose access to your infrastructure. Get a snapshot of the bastion server for backup and recovery.





 Before you begin 



* [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key).
cloudshell:$ ibmcloud is snapshot r138-4463eb2c-4913-43b1-b9bf-62a94f74c146
Getting snapshot r138-4463eb2c-4913-43b1-b9bf-62a94f74c146 under account Test Account as user test.user@ibm.com...

ID r138-4463eb2c-4913-43b1-b9bf-62a94f74c146
Name cli-snapshot-test
CRN crn:v1:bluemix:public:is:eu-de:a/a10d63fa66daffc9b9b5286ce1533080::snapshot:r138-4463eb2c-4913-43b1-b9bf-62a94f74c146
Status stable
Clones Zone Available Created
eu-de-1 true 2023-02-17T20:15:46+00:00

Source volume ID Name
r010-df8ffd90-f2e5-470b-83d7-76e64995a1aa block-test1

Bootable false
Encryption provider_managed
Encryption key -
Minimum capacity(GB) 20
Size(GB) 1
Resource group ID Name
6edefe513d934fdd872e78ee6a8e73ef defaults

Created 2023-02-17T20:15:43+00:00
Captured at 2023-02-17T20:15:44+00:00
Tags env:prod,env:test

For more information about available command options, see [ibmcloud is snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencesnapshots).





 Viewing all fast restore snapshot clones from the CLI 

You can list all available fast restore clones of a snapshot by issuing the ibmcloud is snapshot-cls command.
For more information about available command options, see [ibmcloud is backup-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-vpc-referencebackup-policy-create).





 Creating a backup plan from the CLI 

Run the backup-policy-plan-create command to create a backup plan and attach it to an existing policy. Identify the policy by ID or name.

Syntax:

ibmcloud is backup-policy-plan-create POLICY --cron-spec CRON_SPEC [--name NAME] [--active] [--attach-tags ATTACH_TAGS] [--copy-tags true | false] [--delete-after DELETE_AFTER] [--delete-over-count DELETE_OVER_COUNT] [--output JSON] [-q, --quiet] [--copy-remote-regions TBD] [--encryption-key TBD]

The following example creates a backup plan for an existing policy, which is identified by name my-backup-policy-v1. It attaches backup policy tags to the backup snapshots that are created by the new plan that is called not-just-another-plan. The backup jobs run at 01:05 every morning, and copies source volume tags to the backup snapshot. Fast restore clones are not enabled and the oldest backup is deleted after 80 backup snapshots are taken.

cloudshell:$ ibmcloud is backup-policy-plan-create my-backup-policy-v1 --attach-tags dev:test --copy-tags true --cron-spec '05 01 * * ' --delete-after 80 --name not-just-another-plan
Creating plan not-just-another-plan of backup policy my-backup-policy-v1 under account Test Account as user test.user@ibm.com...

ID r138-4d77d84c-929c-49e9-9f05-952be9486406
Name not-just-another-plan
Active true
Lifecycle state pending
Clone policy Max snapshots Zones
0
: The [quota of snapshots and backup snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasblock-storage-quotas) you can create per volume has been increased to 750. For more information about how these quotas are applied, see [Considerations when creating snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_considerations).





 01 August 2022 

Sharing images across an enterprise account (beta)
: You can now share or publish custom images to other accounts within your enterprise by using a private catalog. A private catalog provides a way for you to manage access to products for multiple accounts. You can use any existing x86 virtual server custom image with a private catalog, with the exception of an encrypted image. For more information, see [Getting started with custom images](https://test.cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images&interface=uicustom-image-cloud-private-catalog).







 June 2022 



 30 June 2022 

IBM Wazi as a Service (s390x processor architecture)
: You can now create virtual server instances of IBM z/OS with IBM Wazi as a Service (Wazi aaS) image on IBM Z (s390x processor architecture) in IBM Cloud in the Japan (Tokyo), Brazil (São Paulo), Canada (Toronto), and United Kingdom (London) regions. The option to select the Wazi aaS z/OS dev and test image is offered as an IBM Cloud allow-listed service. For more information, see [IBM Wazi as a Service product page](https://www.ibm.com/cloud/wazi-as-a-service).

File storage for VPC
: You can now access a customer root key (CRK) from one account, and then use that key to encrypt file shares you create in another account. When you create the file share, you specify the CRN of a root key from the account that contains the key.