vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Naming conventions for backups that are created by the plan are the same as snapshots. For more information, see [Naming snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-managesnapshots-vpc-naming). 
 Creating backups: 
 Prerequisites Verify that the volume is attached to a virtual server instance and that the instance is in a running state. 
 Backup frequency Verify that the plan that you selected is creating backups at the interval that you want. Backups do not occur instaneously like manually created snapshots. Backups usually occur within an hour of being triggered by a backup plan schedule. 
 Tags Verify that at least one of your policy tags matches at least one tag of each volume that you want to back up. 
 Restoring a volume from a backup snapshot: 
 Volume restore performance Review these [performance considerations](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restorebaas-performance-considerations) when you restore a volume from a backup snapshot. You might also experience different regional performance when you restore a volume. <br>Evaluate when to enable [fast restore clones](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-aboutbackup-service-fastrestore). Fast restore snapshots reduce latency by restoring a volume from a snapshot clone. The new volume data is immediately restored. 
 Instance provisioning performance Review these performance considerations when you decide on [provisioning an instance from a bootable snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-baas-vpc-restorebaas-boot-perf). 







 Next steps 

After you plan your backups, you can [Create backup policies](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-policy-create) to back up your volumes.
Classic VMware VM to IBM Cloud VPC migration with RMM 

The RackWare Management Module (RMM) migration solution provides a seamless virtual-to-virtual replatforming for VMware virtual machine (VM) to IBM Cloud® virtual server instance migration. It allows the adoption of existing capabilities of IBM Cloud. Its intuitive GUI permits moving the OS, application, and data from VMware ESXi in IBM Cloud classic to IBM Cloud VPC virtual server instances.

This guide shows you how to complete a migration from VMware ESXi in IBM Cloud classic to IBM Cloud VPC.



 Supported operating systems 



* CentOS 7.8, 7.9
* RHEL 7.2, 7.3, 7.4, 8.1
* Ubuntu 18.04, 20.04
* Debian 9.x, 10.x
* Windows 2012, 2012R2, 2016, 2019







 Architecture diagram 

Zoom

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

Figure 1. Architecture diagram





 Before you begin 



* Check for correct IBM Cloud VPC user permissions. Be sure that your user account has sufficient permissions to create and manage VPC resources. See the list of [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources) for VPC.
* Understand the capability differences between VMware and VPC infrastructures (the following list is not exhaustive):



* VPC does not support shared volumes or file-based volumes
* GPU is not supported in VPC
* Encrypted volumes are not supported





To improve data transfer rate, adjust the bandwidth allocation of the RMM server.
Volume names must begin with a lowercase letter and be unique across the entire VPC infrastructure.

You can change the name of an existing volume in the UI. For more information, see [Managing Block Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storagerename).





 Does the volume need to be pre-warmed to achieve expected throughput? 

You do not have to pre-warm a volume. You can see the specified throughput immediately upon provisioning the volume when you create the volume from an image. You can experience degraded performance when you provision the volume by restoring a snapshot.





 What is a Block Storage for VPC snapshot? 

Snapshots are a point-in-time copy of your Block Storage for VPC boot or data volume that you manually create. The first snapshot is a full backup of the volume. Subsequent snapshots of the same volume capture only the changes since the last snapshot. For more information, see [About Block Storage for VPC Snapshots for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-about).





 What is a backup snapshot? 

Backup snapshots, simply called "backups", are snapshots that are automatically created by the Backup for VPC service. For more information, see [About Backup for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about).





 What can I do about data backups for disaster recovery? 

Block Storage for VPC secures your data across redundant fault zones in your region. 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.
Snapshots retention Evaluate how many snapshots to retain, how long you need to retain them, and when to delete snapshots. Review the [snapshots limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots-vpc-limitations) before you perform these actions. 
 Restoring a volume Consider when you might want to restore a volume from a snapshot. If you need to revert to an earlier version of the volume, plan which snapshot you want to use to create the volume. Evaluate the volumes that you need to restore and attach to an instance, and the volumes that you might restore as unattached volumes. 
 Fast restore Evaluate when to enable snapshots for [fast restore](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restoresnapshots-vpc-use-fast-restore). This feature can be used in disaster recovery scenarios when you need to restore volumes in a different zone of the same region. The fast restore feature can achieve a<br><br>recovery time objective<br><br>(RTO) quicker than restoring from a regular snapshot. 
 Cross-regional copy <br><br>New You can create and store a copy of a snapshot in another region, and use it to create volumes in the target region. This feature can be used in disaster recovery scenarios when you need to start your virtual server instance and data volumes in a different region. Think about whether you need to restore data in other regions. 
 Virtual server instances To create a snapshot from a volume that is attached to an instance, verify that the instance is in a running state. <br>To create an instance from a snapshot of a boot volume, use a snapshot in the same region. 
 Billing Think about the number of snapshots that you want to take. Consider whether you want to create fast-restore clones in other zones of your region. Evaluate if you need cross-regional copies. You're charged for the storage consumption and the data transfer separately. Billing for the fast restore feature is set at a flat rate based on instance hours.
For more information about creating backups, see [Creating a backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-about). For more information about working with tags, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag). 
 Name The name of the snapshot, which you can change by clicking the pencil icon. For more information, see [Change the snapshot name](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-managesnapshots-vpc-rename). 
 Resource group Resource group defined when you set up your VPC. 
 Snapshot ID Copiable GUID of the snapshot. 
 CRN Copiable CRN of the snapshot. 
 Created Date and time that the snapshot resource creation process started. 
 Created by By the user, a manually created snapshot, or automatically by a [backup policy](https://cloud.ibm.com/docs/vpc?topic=vpc-backup-service-about&interface=uibackup-service-concepts). 
 Captured The date and time that this snapshot was captured, that is, the volume data was snapshotted. If absent, the snapshot wasn't captured or the snapshot was created before this feature was introduced (January 2022). 
 Region Region of the source volume and snapshot. 
 Size Size in GBs of the snapshot, inherited from the source volume. 
 Source volume Source volume from which the first snapshot was taken. Click the link for volume details. If the volume was deleted, the name appears without a link. 
 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.
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." The Plan status toggle is enabled by default.
8. Click Create to save the new plan.
[menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes.
2. Select Create.
3. Specify the volume name, optional resource group and tags, and specify the location. You're going to use the data from a snapshot to provision the volume.
4. Under Snapshot (optional), click Select snapshot. From the list, select a snapshot. All snapshots that are presented are in a stable state.

By default, the Nonbootable tab is selected that lists all data volume snapshots. To restore a boot volume, click the Bootable tab. Attach volume to new virtual server instance is selected by default. The boot volume is restored when the instance is created.
5. Click Save and continue. Information about the snapshot is shown on the volume provisioning page, including the name, its size, the date when it was created, its source volume, and whether it is a bootable snapshot. Bootable snapshot information includes the operating system and image. The encryption is inherited from the snapshot and shown in the encryption section.



Create a boot volume from a snapshot and provision an instance.







 Creating Block Storage for VPC volumes from the CLI 

You can create Block Storage for VPC volumes by using the command-line interface (CLI).



 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 the 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.
Connections with customized IKE or IPsec policies that contain weak ciphers will be disabled. For more information, see [Upgrading a VPN from a custom IKE or IPsec policy](https://cloud.ibm.com/docs/vpc?topic=vpc-upgrading-weak-ciphers&interface=apiupgrade-vpn-with-custom-policy).





 11 July 2023 



 For all version dates 

Image lifecycle management. You can now [deprecate](https://cloud.ibm.com/apidocs/vpc-betadeprecate-image) or [obsolete](https://cloud.ibm.com/apidocs/vpc-betaobsolete-image) custom images directly. Alternatively, you can schedule transition at a later date by specifying the deprecation_at or obsolescence_at properties when [creating](https://cloud.ibm.com/apidocs/vpc-betacreate-image) or [updating](https://cloud.ibm.com/apidocs/vpc-betaupdate-image) an image. If you need to revert a status change, you can transition deprecated or obsolete images back to available. For more information, see [Managing custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-images&interface=apicustom-images-list-api).

deprecated custom images remain usable, while obsolete images cannot be used to provision instances or bare metal servers.







 27 June 2023 



 For all version dates 

Copying snapshots and backups across regions. You can now specify an existing snapshot in one region to [create](https://cloud.ibm.com/apidocs/vpc/latestcreate-snapshot) a copy of the snapshot in another region. When you [list all snapshots](https://cloud.ibm.com/apidocs/vpc/latestlist-snapshots), you can see the direct snapshot copies in the other regions and you can use them to restore volumes in the other regions.
For more information, see [Restoring a volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore).





 Fast restore snapshot clones 

By using the snapshots fast restore feature, you create and keep a clone of the data in a zone within your VPC region. In other words, your data is fully available when the volume is created because it is already in the VPC region and not in Object Storage. In contrast, when data is not restored from a fast restore snapshot clone, volume data is copied from Object Storage when the volume is attached to an instance over time. The fast restore feature can achieve a

recovery time objective(RTO) quicker than restoring from a regular snapshot.

The fast restore feature can be enabled in the UI, from the CLI, with the API, or Terraform. In the CLI, API, and Terraform, the responses show clones. The UI shows fast restore snapshot clones as fast restore snapshots, but they are the same thing.

Billing for the fast restore feature is set at a flat rate based on instance hours.

For more information, see [Restoring a volume with the fast restore feature](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore&interface=uisnapshots-vpc-use-fast-restore).





 Cross-regional snapshot copies 

New

You can copy a snapshot from one region to another region, and later use that snapshot to restore a volume in the new region. This feature can be used in disaster recovery scenarios when you need to start your virtual server instance and data volumes in a different region. Or you can use the remote copy to create storage volumes in a new region to expand your VPC.

When you choose to create a cross-regional copy of a snapshot, you need to specify a single snapshot to be copied to the target region. The snapshot is created as normal, and stored in your regional Object Storage. A copy of the snapshot is created in an Object Storage bucket in the target region.
* View the delegate_vpc property in the requests and responses for /vpcs/{vpc_id}/routing_tables/{routing_table_id}/routes.
* View reserved IP ranges in POST /vpcs/{vpc_id}/address_prefixes, which creates an address pool prefix.









 27 January 2021 



 For all version dates 

Checksum (SHA256) for imported images. When you import a custom image to IBM Cloud VPC, you can now view the checksum that was generated for the image during the import operation. By generating a checksum for the image locally, and checking that the checksums match, you can verify the integrity of the imported image. For more information, see [Validating a custom image after importing](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-imagesvalidate-custom).

The sha256 checksum is available in the file details in API method GET /images/{id}. See [Retrieve an image](https://cloud.ibm.com/apidocs/vpcget-image).







 19 January 2021 



 For all version dates 

The quantity of memory for virtual server instance profiles is now provisioned in gibibytes (GiB), instead of gigabytes (GB). For example, creating a new bx2-4x16 virtual server instance provisions the instance with 16 GiB (17,179,869,184 bytes), instead of 16 GB (16,000,000,000 bytes). Virtual server instances that have already been provisioned are not affected.





 For version 2021-01-19 or later 

For requests using a version query parameter of 2021-01-19 or later, memory for virtual server instances is now expressed in gibibytes (GiB), instead of gigabytes (GB). For example, the memory property returned from GET /instances/{id} now reports in GiB (truncated to a whole number).







 16 December 2020 



 For all version dates 

Customer-managed encryption for block storage volumes and encrypted custom images.
Understanding business continuity and disaster recovery for IBM Cloud VPC 

Disaster recoveryinvolves a set of policies, tools, and procedures for returning a system, an application, or an entire data center to full operation after a catastrophic interruption. It includes procedures for copying and storing an installed system's essential data in a secure location, and for recovering that data to restore normalcy of operation.



  Responsibilities 

For more information about your responsibilities, see [Understanding your responsibilities when you use Virtual Private Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-responsibilities-vpc).





  Disaster recovery strategy 

IBM Cloud has

business continuityplans in place to provide for the recovery of services within hours if a disaster occurs. You are responsible for your data backup and associated recovery of your content.

IBM Cloud VPC provides mechanisms to protect your data and restore service functions. Business continuity plans are in place to achieve targeted

recovery point objective(RPO) andrecovery time objective(RTO) for the service. The following table outlines the targets for VPC services.



Table 1. RPO and RTO for IBM Cloud VPC services

 Disaster recovery objective  Target Value          

 RPO                          VPN for VPC: 24 hours 
 RTO                          VPN for VPC: 5 hours  







  Locations 

For more information about service availability within regions and data centers, see [Service and infrastructure availability by location](https://cloud.ibm.com/docs/overview?topic=overview-services_region).
The encryption key is not stored and is unavailable to IBM. After the VMware Cloud Director Data Center is deleted, all backups are deleted, and cannot be recovered.





 High availability and disaster recovery 

The VMware Shared management service is initially only offered in the IBM Cloud NA South and Europe regions. Recovering from potential disasters that affect an entire location requires planning and preparation.



* You are responsible for understanding your configuration, customization, and usage of the service.
* You are responsible for enabling your VMs or virtual applications (vApps) to participate in the provided backup service.
* You are responsible for being ready to restore all instances of your VMs or vApps used in the service in the restored location or new location.





 High availability 

VMware Shared supports high availability of the VMware Cloud Director service itself. The service achieves high availability automatically and transparently by using the Multizone region (MZR) feature that is provided by IBM Cloud.

However, you cannot configure workloads that are running VMs and vApps in a high availability manner across multiple IBM Cloud data center sites. VMware Shared currently allows workloads to operate in only one IBM Cloud data center site.

Use VMware Shared with vCenter Server to achieve high availability. You can deploy vCenter Server in multiple IBM Cloud data center regions.





 Disaster recovery 

Disaster recovery can become an issue if an IBM Cloud location experiences a significant failure that includes the potential loss of data. Because MZRs are not available across locations, you must wait for IBM to bring a location back online if it becomes unavailable. If underlying data services are compromised by the failure, you must also wait for IBM to restore those data services.

If a catastrophic failure occurs, IBM might not be able to recover data from database backups. In this case, you need to restore your data to return your service instance to its most recent state. You can restore the data to the same or to a different location, including a vCenter Server instance.

Your disaster recovery plan includes knowing, preserving, and being prepared to restore all data that is maintained on IBM Cloud.







 Related links
snapshot = "r138-e6664842-b370-496a-9ae7-da3fb647707c"
zone = "eu-de-1"
}

For more information, see [ibm_is_snapshot_clone](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_snapshot_clone).







 Next steps 

You can modify or delete snapshots and restore a volume from a snapshot.



* [Modify or delete snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-manage).
* [Restore a volume from a snapshot](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-restore).
If you created volume snapshots previously, the option to import one becomes available. Click the Snapshots toggle, and select a snapshot from the list. You can filter this list for snapshots with fast restore. Then, complete the required fields and click Create to provision the volume. A Block Storage for VPC volume is created and attached to the virtual server instance. On the instance details page, the Data volumes list is updated to show the new volume

For more information, 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).
5. When you're finished defining the attributes of your virtual server instance, click Create virtual server. The virtual server instance is created with the boot volume, which appears under Boot volume on the provision page.



A Block Storage for VPC volume can be attached to only one virtual server at a time. On the Block Storage for VPC volume summary page, you can view details about the virtual server instance by selecting the instance name under Attached instances.





 Creating and attach a Block Storage for VPC volume from an existing instance 

You can create a new Block Storage for VPC volume from an existing instance.



1. Go to the list of virtual server instances. In the [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Select an instance from the list.
3. On the instance details page, scroll to Storage volumes and click Attach.
4. In the side panel, click the down arrow under Block volumes and select Create a data volume. The side panel expands with fields to define the volume. For more information about these fields, see table 1.



* If you created volume snapshots previously, the option to import one becomes available.