diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.de-de.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.de-de.md index 5b23ab57a71..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.de-de.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.de-de.md @@ -1,5 +1,5 @@ --- -title: Public Cloud Reversibility Policy (EN) +title: Public Cloud Reversibility Policy updated: 2021-05-05 --- @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-asia.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-asia.md index 84ebec326b6..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-asia.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-asia.md @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-au.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-au.md index 84ebec326b6..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-au.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-au.md @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ca.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ca.md index 84ebec326b6..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ca.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ca.md @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-gb.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-gb.md index 84ebec326b6..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-gb.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-gb.md @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ie.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ie.md index 84ebec326b6..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ie.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-ie.md @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-sg.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-sg.md index 84ebec326b6..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-sg.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-sg.md @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-us.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-us.md index 84ebec326b6..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-us.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.en-us.md @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-es.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-es.md index 5b23ab57a71..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-es.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-es.md @@ -1,5 +1,5 @@ --- -title: Public Cloud Reversibility Policy (EN) +title: Public Cloud Reversibility Policy updated: 2021-05-05 --- @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-us.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-us.md index 5b23ab57a71..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-us.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.es-us.md @@ -1,5 +1,5 @@ --- -title: Public Cloud Reversibility Policy (EN) +title: Public Cloud Reversibility Policy updated: 2021-05-05 --- @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-ca.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-ca.md index 8d0fd835681..4ed709e1b4f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-ca.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-ca.md @@ -24,7 +24,7 @@ Les fonctionnalités Public Cloud sont divisées en trois catégories : |Compute|Démarre et exécute les instances en fonction de plusieurs images système et flavors disponibles.|qcow2|Effectuez des snapshots des instances, convertissez-les en images puis exportez les images.|[Créer et utiliser des snapshots OpenStack](https://www.ovh.com/blog/create-and-use-openstack-snapshots/) (EN)

[Transférer la sauvegarde d’une instance d’un datacenter à un autre](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d'une instance dans Horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon)| |Swift - Stockage Public Cloud|Stocke les fichiers accessibles via les API OpenStack Swift ou S3. Active l'utilisation des métadonnées pour les objets.|**Tout format** - les clients peuvent téléverser n'importe quel fichier sur l'object storage|Utilisez n'importe quel outil de synchronisation compatible avec l'API S3 ou l'API Swift (Par exemple, nous recommandons rclone).|[Premiers pas avec l'API Swift S3](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Débuter avec l’API Swift](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Archive publique dans le nuage|Stockage de fichiers à long terme|**Tous les formats** - Les clients peuvent télécharger n'importe quel fichier sur le stockage d'objets|Utilisez n'importe quel outil de synchronisation compatible avec S3 ou l'API rapide. Par exemple, nous recommandons rclone.|[Premiers pas avec l'API Swift S3](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Débuter avec l’API Swift](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block Storage|Attacher des volumes pour ajouter du stockage additionnel sur des instances Public Cloud|**Tout format** - Les clients peuvent téléverser n'importe quel fichier sur le block storage.|Convertissez le volume en image, exportez l'image|[Transférer la sauvegarde d’un volume d’un datacenter à l’autre](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block Storage|Attacher des volumes pour ajouter du stockage additionnel sur des instances Public Cloud|**Tout format** - Les clients peuvent écrire n’importe quel type de données dans leur volume de blocs | Exporter les données du volume de blocs et les importer dans le nouvel environnement | N/A | |Horizon - Interface Web|Panneau de configuration Web et interface de gestion|N/A|Aucune migration en soi, il s'agit juste d'une interface au-dessus des ressources|N/A| |Mistral - Gestion des flux de travail|Décrit et exécute les processus en tant qu'ensemble de tâches et de transitions.|Yaml|Exportez les fichiers de flux de travail et exécutez-les dans le nouvel environnement|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-fr.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-fr.md index 8d0fd835681..4ed709e1b4f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-fr.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.fr-fr.md @@ -24,7 +24,7 @@ Les fonctionnalités Public Cloud sont divisées en trois catégories : |Compute|Démarre et exécute les instances en fonction de plusieurs images système et flavors disponibles.|qcow2|Effectuez des snapshots des instances, convertissez-les en images puis exportez les images.|[Créer et utiliser des snapshots OpenStack](https://www.ovh.com/blog/create-and-use-openstack-snapshots/) (EN)

[Transférer la sauvegarde d’une instance d’un datacenter à un autre](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d'une instance dans Horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon)| |Swift - Stockage Public Cloud|Stocke les fichiers accessibles via les API OpenStack Swift ou S3. Active l'utilisation des métadonnées pour les objets.|**Tout format** - les clients peuvent téléverser n'importe quel fichier sur l'object storage|Utilisez n'importe quel outil de synchronisation compatible avec l'API S3 ou l'API Swift (Par exemple, nous recommandons rclone).|[Premiers pas avec l'API Swift S3](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Débuter avec l’API Swift](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Archive publique dans le nuage|Stockage de fichiers à long terme|**Tous les formats** - Les clients peuvent télécharger n'importe quel fichier sur le stockage d'objets|Utilisez n'importe quel outil de synchronisation compatible avec S3 ou l'API rapide. Par exemple, nous recommandons rclone.|[Premiers pas avec l'API Swift S3](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Débuter avec l’API Swift](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block Storage|Attacher des volumes pour ajouter du stockage additionnel sur des instances Public Cloud|**Tout format** - Les clients peuvent téléverser n'importe quel fichier sur le block storage.|Convertissez le volume en image, exportez l'image|[Transférer la sauvegarde d’un volume d’un datacenter à l’autre](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block Storage|Attacher des volumes pour ajouter du stockage additionnel sur des instances Public Cloud|**Tout format** - Les clients peuvent écrire n’importe quel type de données dans leur volume de blocs | Exporter les données du volume de blocs et les importer dans le nouvel environnement | N/A | |Horizon - Interface Web|Panneau de configuration Web et interface de gestion|N/A|Aucune migration en soi, il s'agit juste d'une interface au-dessus des ressources|N/A| |Mistral - Gestion des flux de travail|Décrit et exécute les processus en tant qu'ensemble de tâches et de transitions.|Yaml|Exportez les fichiers de flux de travail et exécutez-les dans le nouvel environnement|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.it-it.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.it-it.md index 5b23ab57a71..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.it-it.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.it-it.md @@ -1,5 +1,5 @@ --- -title: Public Cloud Reversibility Policy (EN) +title: Public Cloud Reversibility Policy updated: 2021-05-05 --- @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pl-pl.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pl-pl.md index 5b23ab57a71..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pl-pl.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pl-pl.md @@ -1,5 +1,5 @@ --- -title: Public Cloud Reversibility Policy (EN) +title: Public Cloud Reversibility Policy updated: 2021-05-05 --- @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pt-pt.md b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pt-pt.md index 5b23ab57a71..2858e6d5f5f 100644 --- a/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pt-pt.md +++ b/pages/account_and_service_management/reversibility/03-public-cloud-reversibility-policy/guide.pt-pt.md @@ -1,5 +1,5 @@ --- -title: Public Cloud Reversibility Policy (EN) +title: Public Cloud Reversibility Policy updated: 2021-05-05 --- @@ -24,7 +24,7 @@ Public cloud features are divided into three categories: |Compute|Start and run instances based on multiple system images and flavors available.|qcow2|Snapshot instances, convert them to images, export the images.|[Create and use OpenStack snapshots](https://www.ovh.com/blog/create-and-use-openstack-snapshots/)

[Transfer an Instance backup from one datacentre to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another)

[Gestion des snapshots d’une instance dans horizon](/pages/public_cloud/compute/managing_snapshots_in_horizon) (FR)| |Swift - Public cloud storage|Store files accessible through openstack swift API or S3 API. Enable the use of metadata for objects.|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| |Swift - Public cloud archive|Long-term file storage|**Every format** - customers may upload any file on the object storage|Use any synchronisation tool compatible with either S3 or swift API. As an example, we recommend rclone.|[Getting started with the Swift S3 API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_s3_api)

[Getting started with the Swift API](/pages/storage_and_backup/object_storage/pcs_getting_started_with_the_swift_api)| -|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - customers may upload any file on the object storage|Convert the volume to an image, export images|[Transfer a volume backup from one datacentre to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another)| +|Ceph - Block storage|Attach volumes for additional storage to public cloud instances|**Every format** - Customers can write any type of data to their block volume | Export block volume data and import it into the new environment|N/A| |Horizon - WebUI Service|Web control panel and management interface|N/A|No migration per se, this is just an interface above resources|N/A| |Mistral - Workflow management|Describe and execute processes as a set of tasks and their transitions.|Yaml|Export workflows files and run them in the new environment|N/A| diff --git a/pages/index.md b/pages/index.md index 0e26cf9e2ab..74c875981ce 100644 --- a/pages/index.md +++ b/pages/index.md @@ -873,7 +873,6 @@ + [Creating a volume from a backup](public_cloud/compute/create-volume-from-snapshot) + [Increasing the size of an additional disk](public_cloud/compute/increase_the_size_of_an_additional_disk) + [Test disk speed](public_cloud/compute/test_disk_speed) - + [Transfer a volume backup from one datacentre to another](public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) + [Migration](public-cloud-storage-block-storage-migration) + [Migrating a Block Storage volume to an encrypted LUKS volume](public_cloud/compute/migrating-non-encrypted-to-encrypted-volume) + [Change your Block Storage volume type](public_cloud/compute/switch_volume_type) diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.de-de.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.de-de.md index 6f7f09a6421..0f53c34c36e 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.de-de.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.de-de.md @@ -101,7 +101,7 @@ High Speed Volumes der zweiten Generation sind für die anspruchsvollsten Worklo >> >> > [!warning] >> > ->> > Hinweis: Das Volume muss in derselben Region wie die Instanz erstellt werden, mit der es verbunden werden soll. Ein in einer anderen Region erstelltes Volume kann entfernt und in der richtigen Region neu erstellt werden, oder Sie können zwischen Regionen migrieren, indem Sie [diese Anleitung](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) befolgen. +>> > Hinweis: Das Volume muss in derselben Region wie die Instanz erstellt werden, mit der es verbunden werden soll. Ein in einer anderen Region erstelltes Volume kann entfernt und in der richtigen Region neu erstellt werden. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-asia.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-asia.md index 0c0911519d0..9e2e825cb1c 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-asia.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-asia.md @@ -101,7 +101,7 @@ Generation 2 High-Speed volumes are optimized for the most demanding workloads. >> >> > [!warning] >> > ->> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region, or you can migrate the region by following [this guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-au.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-au.md index 0c0911519d0..9e2e825cb1c 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-au.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-au.md @@ -101,7 +101,7 @@ Generation 2 High-Speed volumes are optimized for the most demanding workloads. >> >> > [!warning] >> > ->> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region, or you can migrate the region by following [this guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ca.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ca.md index 0c0911519d0..9e2e825cb1c 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ca.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ca.md @@ -101,7 +101,7 @@ Generation 2 High-Speed volumes are optimized for the most demanding workloads. >> >> > [!warning] >> > ->> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region, or you can migrate the region by following [this guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-gb.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-gb.md index 0c0911519d0..9e2e825cb1c 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-gb.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-gb.md @@ -101,7 +101,7 @@ Generation 2 High-Speed volumes are optimized for the most demanding workloads. >> >> > [!warning] >> > ->> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region, or you can migrate the region by following [this guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ie.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ie.md index 0c0911519d0..9e2e825cb1c 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ie.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-ie.md @@ -101,7 +101,7 @@ Generation 2 High-Speed volumes are optimized for the most demanding workloads. >> >> > [!warning] >> > ->> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region, or you can migrate the region by following [this guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-sg.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-sg.md index 0c0911519d0..9e2e825cb1c 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-sg.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-sg.md @@ -101,7 +101,7 @@ Generation 2 High-Speed volumes are optimized for the most demanding workloads. >> >> > [!warning] >> > ->> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region, or you can migrate the region by following [this guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-us.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-us.md index 0c0911519d0..9e2e825cb1c 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-us.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.en-us.md @@ -101,7 +101,7 @@ Generation 2 High-Speed volumes are optimized for the most demanding workloads. >> >> > [!warning] >> > ->> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region, or you can migrate the region by following [this guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Please note: Your volume must be created in the same region as the instance to which you want to attach it. If you create it in another region, you can delete it and recreate it in the correct region. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-es.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-es.md index c6835d64bff..a6bf6d62c4f 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-es.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-es.md @@ -101,7 +101,7 @@ La generación 2 de los volúmenes High-Speed está optimizada para las cargas d >> >> > [!warning] >> ->> > Nota: El volumen debe crearse en la misma región que la instancia a la que desea asociarlo. Si lo crea en otra región, puede eliminarlo y volver a crearlo en la región correcta o puede migrar la región siguiendo [esta guía](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Nota: El volumen debe crearse en la misma región que la instancia a la que desea asociarlo. Si lo crea en otra región, puede eliminarlo y volver a crearlo en la región correcta. >> >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-us.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-us.md index c6835d64bff..a6bf6d62c4f 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-us.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.es-us.md @@ -101,7 +101,7 @@ La generación 2 de los volúmenes High-Speed está optimizada para las cargas d >> >> > [!warning] >> ->> > Nota: El volumen debe crearse en la misma región que la instancia a la que desea asociarlo. Si lo crea en otra región, puede eliminarlo y volver a crearlo en la región correcta o puede migrar la región siguiendo [esta guía](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Nota: El volumen debe crearse en la misma región que la instancia a la que desea asociarlo. Si lo crea en otra región, puede eliminarlo y volver a crearlo en la región correcta. >> >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-ca.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-ca.md index 6b1a5e14f15..d27a2612803 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-ca.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-ca.md @@ -101,7 +101,7 @@ La génération 2 des volumes High-Speed est optimisée pour les workloads les p >> >> > [!warning] >> > ->> > Remarque : Votre volume doit être créé dans la même région que l'instance à laquelle vous souhaitez l'attacher. Si vous le créez dans une autre région, vous pouvez le supprimer et le recréer dans la bonne région, ou vous pouvez migrer la région en suivant [ce guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Remarque : Votre volume doit être créé dans la même région que l'instance à laquelle vous souhaitez l'attacher. Si vous le créez dans une autre région, vous pouvez le supprimer et le recréer dans la bonne région. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-fr.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-fr.md index 6b1a5e14f15..d27a2612803 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-fr.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.fr-fr.md @@ -101,7 +101,7 @@ La génération 2 des volumes High-Speed est optimisée pour les workloads les p >> >> > [!warning] >> > ->> > Remarque : Votre volume doit être créé dans la même région que l'instance à laquelle vous souhaitez l'attacher. Si vous le créez dans une autre région, vous pouvez le supprimer et le recréer dans la bonne région, ou vous pouvez migrer la région en suivant [ce guide](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Remarque : Votre volume doit être créé dans la même région que l'instance à laquelle vous souhaitez l'attacher. Si vous le créez dans une autre région, vous pouvez le supprimer et le recréer dans la bonne région. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.it-it.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.it-it.md index 910b45ad84c..de1e2c185fb 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.it-it.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.it-it.md @@ -102,7 +102,7 @@ La generazione 2 dei volumi High Speed è ottimizzata per i workload più esigen >> >> > [!warning] >> > ->> > Nota: il volume deve essere creato nella stessa regione dell'istanza a cui si desidera associarlo. Se lo crei in un'altra Region, puoi eliminarlo e ricrearlo nella Region corretta, oppure puoi migrare la Region seguendo [questa guida](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Nota: il volume deve essere creato nella stessa regione dell'istanza a cui si desidera associarlo. Se lo crei in un'altra Region, puoi eliminarlo e ricrearlo nella Region corretta. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pl-pl.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pl-pl.md index 6b09000bbc7..2531eaaeaea 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pl-pl.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pl-pl.md @@ -101,7 +101,7 @@ Generowanie 2 wolumenów High-Speed jest zoptymalizowane pod kątem najbardziej >> >> > [!warning] >> > ->> > Uwaga: Wolumen musi być utworzony w tym samym regionie, co instancja, do której chcesz go przypisać. Jeśli utworzysz ją w innym regionie, możesz ją usunąć i odtworzyć we właściwej lokalizacji lub możesz przenieść ją ponownie, postępując zgodnie z [tym przewodnikiem](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Uwaga: Wolumen musi być utworzony w tym samym regionie, co instancja, do której ma zostać przypisany. Jeśli utworzysz ją w innym regionie, możesz ją usunąć i odtworzyć w odpowiednim regionie. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pt-pt.md b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pt-pt.md index 63d56bb4d1d..2ed46aa5f96 100644 --- a/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pt-pt.md +++ b/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance/guide.pt-pt.md @@ -101,7 +101,7 @@ A geração 2 dos volumes High-Speed é otimizada para as cargas de trabalho mai >> >> > [!warning] >> > ->> > Nota: O seu volume deve ser criado na mesma região que a instância à qual deseja associá-lo. Se o criar noutra região, poderá eliminá-lo e recriá-lo na região correta, ou migrá-lo seguindo [este manual](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another). +>> > Nota: O seu volume deve ser criado na mesma região que a instância à qual deseja associá-lo. Se o criar noutra região, poderá eliminá-lo e recriá-lo na região correta. >> > >> >> ![create disk](images/avolume02.png){.thumbnail} diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.de-de.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.de-de.md deleted file mode 100644 index 44d329c570f..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.de-de.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: Übertragen von Volume-Backups von einer OpenStack-Region in eine andere -excerpt: Erfahren Sie hier, wie Sie das Backup eines Volumes von einer OpenStack-Region in eine andere verschieben können -updated: 2024-01-11 ---- - -## Ziel - -Es kann vorkommen, dass Sie zusätzliche Volumes von einer OpenStack-Region in eine andere verschieben müssen; etwa weil Sie in einer neuen OpenStack-Region operieren möchten, oder weil Sie von [OVHcloud Labs](https://labs.ovh.com/) in die [Public Cloud](/links/public-cloud/compute) migrieren möchten. - -**Diese Anleitung erklärt, wie Sie ein Volume-Backup von einer OpenStack-Region in eine andere übertragen.** - -## Voraussetzungen - -Um den Transfer durchzuführen benötigen Sie eine Umgebung mit: - -- [OpenStack CLI](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Anbindung an die OpenStack API von OVHcloud. -- Verfügbarer Speicherplatz entsprechend der Größe der Volume-Disk (für temporären Backup-Speicher). - -Diese Umgebung wird als "Jump Host" verwendet, um das Backup von einer Region in eine andere zu übertragen. Bei dieser Umgebung kann es sich um eine bei OVHcloud oder auf Ihrem lokalen System gehostete Instanz handeln. - -## In der praktischen Anwendung - -### Backup erstellen - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -Wenn das Volume mit einer Instanz verbunden ist, muss es zuerst getrennt werden, bevor das Backup erstellt werden kann. - -Verwenden Sie den folgenden Befehl, um die Instanz-ID abzurufen: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Führen Sie dann den folgenden Befehl aus, um das Volume von seiner Instanz aus zu mounten: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Erstellen Sie nun mit folgendem Befehl ein Backup als Image: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Laden Sie das Backup herunter - -Führen Sie den folgenden Befehl aus, um die verfügbaren Images aufzulisten: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Identifizieren Sie das Backup in der Liste: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Verwenden Sie diesen Befehl, um das Backup herunterzuladen: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Backup in eine andere OpenStack-Region übertragen - -Um den Transferprozess zu starten, müssen Sie zunächst neue Umgebungsvariablen laden. - -> [!warning] -> -Wenn Sie Ihr Backup in eine OpenStack-Region innerhalb desselben Projekts verschieben, müssen Sie die Variable `OS_REGION_NAME` ändern. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -Wenn Sie Ihr Backup auf ein anderes Projekt oder oder in einen anderen Account verschieben, müssen Sie die mit diesem Account verbundenen Umgebungsvariablen mit dem folgenden Befehl neu laden: - -```sh -$ source openrc.sh -``` - -Um das Backup in die neue OpenStack-Region zu übertragen, verwenden Sie diesen Befehl: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Erstellen Sie ein Volume aus Ihrem Backup - -Verwenden Sie die Backup-ID als Image mit dem folgenden Befehl: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Weiterführende Informationen - -[Backup einer Instanz herunterladen von einer OpenStack-Region in eine andere übertragen](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Treten Sie unserer [User Community](/links/community) bei. diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-asia.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-asia.md deleted file mode 100644 index 71884aa2210..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-asia.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: 'Transferring a volume backup from one OpenStack region to another' -excerpt: 'This guide will show you how to transfer a volume backup from one OpenStack region to another' -updated: 2024-01-11 ---- - -## Objective - -It may become necessary to move additional volumes from one OpenStack region to another, either because you would prefer to move to a newly-available OpenStack region, or because you want to migrate from [OVHcloud Labs](https://labs.ovh.com/) (formerly RunAbove) to the [Public Cloud](/links/public-cloud/compute). - -**This guide will show you how to transfer a volume backup from one OpenStack region to another.** - -## Requirements - -In order to do the transfer, you will need an environment with: - -- OpenStack CLI. Use [our guide to know how to prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Connectivity to OVHCloud OpenStack APIs. -- Available storage that matches the volume's disk size (for temporary backup storage). - -This environment will be used as a "jump host" to transfer the backup from one region to another. This environment can be an instance hosted on OVHCloud or your local machine. - -## Instructions - -### Create a backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -If the volume is attached to an instance, you must first detach it before creating the backup. - -Use the command below to retrieve the instance ID: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Next, run the following command to detatch the volume from its instance: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Next, create a backup in the form of an image, using the following command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Download the backup - -Now, run this command to list the available images: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Next, identify the volume backup from the list: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Finally, run this command to download the backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transfer the backup to another OpenStack region - -To start the transfer process, you first need to load new environment variables. - -> [!warning] -> -If you are transferring to an OpenStack region within the same project, just change the OS_REGION_NAME variable. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -If you are transferring your backup to another project or account, you will have to reload the environment variables linked to that account using the following command: - -```sh -$ source openrc.sh -``` - -To transfer the backup to the new OpenStack region, use this command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Create a volume from your backup - -To create a volume from your backup, use the backup ID as the image with this command: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Go further - -[Downloading and transferring an instance backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-au.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-au.md deleted file mode 100644 index 71884aa2210..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-au.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: 'Transferring a volume backup from one OpenStack region to another' -excerpt: 'This guide will show you how to transfer a volume backup from one OpenStack region to another' -updated: 2024-01-11 ---- - -## Objective - -It may become necessary to move additional volumes from one OpenStack region to another, either because you would prefer to move to a newly-available OpenStack region, or because you want to migrate from [OVHcloud Labs](https://labs.ovh.com/) (formerly RunAbove) to the [Public Cloud](/links/public-cloud/compute). - -**This guide will show you how to transfer a volume backup from one OpenStack region to another.** - -## Requirements - -In order to do the transfer, you will need an environment with: - -- OpenStack CLI. Use [our guide to know how to prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Connectivity to OVHCloud OpenStack APIs. -- Available storage that matches the volume's disk size (for temporary backup storage). - -This environment will be used as a "jump host" to transfer the backup from one region to another. This environment can be an instance hosted on OVHCloud or your local machine. - -## Instructions - -### Create a backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -If the volume is attached to an instance, you must first detach it before creating the backup. - -Use the command below to retrieve the instance ID: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Next, run the following command to detatch the volume from its instance: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Next, create a backup in the form of an image, using the following command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Download the backup - -Now, run this command to list the available images: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Next, identify the volume backup from the list: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Finally, run this command to download the backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transfer the backup to another OpenStack region - -To start the transfer process, you first need to load new environment variables. - -> [!warning] -> -If you are transferring to an OpenStack region within the same project, just change the OS_REGION_NAME variable. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -If you are transferring your backup to another project or account, you will have to reload the environment variables linked to that account using the following command: - -```sh -$ source openrc.sh -``` - -To transfer the backup to the new OpenStack region, use this command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Create a volume from your backup - -To create a volume from your backup, use the backup ID as the image with this command: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Go further - -[Downloading and transferring an instance backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-ca.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-ca.md deleted file mode 100644 index 71884aa2210..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-ca.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: 'Transferring a volume backup from one OpenStack region to another' -excerpt: 'This guide will show you how to transfer a volume backup from one OpenStack region to another' -updated: 2024-01-11 ---- - -## Objective - -It may become necessary to move additional volumes from one OpenStack region to another, either because you would prefer to move to a newly-available OpenStack region, or because you want to migrate from [OVHcloud Labs](https://labs.ovh.com/) (formerly RunAbove) to the [Public Cloud](/links/public-cloud/compute). - -**This guide will show you how to transfer a volume backup from one OpenStack region to another.** - -## Requirements - -In order to do the transfer, you will need an environment with: - -- OpenStack CLI. Use [our guide to know how to prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Connectivity to OVHCloud OpenStack APIs. -- Available storage that matches the volume's disk size (for temporary backup storage). - -This environment will be used as a "jump host" to transfer the backup from one region to another. This environment can be an instance hosted on OVHCloud or your local machine. - -## Instructions - -### Create a backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -If the volume is attached to an instance, you must first detach it before creating the backup. - -Use the command below to retrieve the instance ID: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Next, run the following command to detatch the volume from its instance: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Next, create a backup in the form of an image, using the following command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Download the backup - -Now, run this command to list the available images: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Next, identify the volume backup from the list: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Finally, run this command to download the backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transfer the backup to another OpenStack region - -To start the transfer process, you first need to load new environment variables. - -> [!warning] -> -If you are transferring to an OpenStack region within the same project, just change the OS_REGION_NAME variable. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -If you are transferring your backup to another project or account, you will have to reload the environment variables linked to that account using the following command: - -```sh -$ source openrc.sh -``` - -To transfer the backup to the new OpenStack region, use this command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Create a volume from your backup - -To create a volume from your backup, use the backup ID as the image with this command: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Go further - -[Downloading and transferring an instance backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-gb.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-gb.md deleted file mode 100644 index 71884aa2210..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-gb.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: 'Transferring a volume backup from one OpenStack region to another' -excerpt: 'This guide will show you how to transfer a volume backup from one OpenStack region to another' -updated: 2024-01-11 ---- - -## Objective - -It may become necessary to move additional volumes from one OpenStack region to another, either because you would prefer to move to a newly-available OpenStack region, or because you want to migrate from [OVHcloud Labs](https://labs.ovh.com/) (formerly RunAbove) to the [Public Cloud](/links/public-cloud/compute). - -**This guide will show you how to transfer a volume backup from one OpenStack region to another.** - -## Requirements - -In order to do the transfer, you will need an environment with: - -- OpenStack CLI. Use [our guide to know how to prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Connectivity to OVHCloud OpenStack APIs. -- Available storage that matches the volume's disk size (for temporary backup storage). - -This environment will be used as a "jump host" to transfer the backup from one region to another. This environment can be an instance hosted on OVHCloud or your local machine. - -## Instructions - -### Create a backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -If the volume is attached to an instance, you must first detach it before creating the backup. - -Use the command below to retrieve the instance ID: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Next, run the following command to detatch the volume from its instance: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Next, create a backup in the form of an image, using the following command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Download the backup - -Now, run this command to list the available images: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Next, identify the volume backup from the list: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Finally, run this command to download the backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transfer the backup to another OpenStack region - -To start the transfer process, you first need to load new environment variables. - -> [!warning] -> -If you are transferring to an OpenStack region within the same project, just change the OS_REGION_NAME variable. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -If you are transferring your backup to another project or account, you will have to reload the environment variables linked to that account using the following command: - -```sh -$ source openrc.sh -``` - -To transfer the backup to the new OpenStack region, use this command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Create a volume from your backup - -To create a volume from your backup, use the backup ID as the image with this command: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Go further - -[Downloading and transferring an instance backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-ie.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-ie.md deleted file mode 100644 index 71884aa2210..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-ie.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: 'Transferring a volume backup from one OpenStack region to another' -excerpt: 'This guide will show you how to transfer a volume backup from one OpenStack region to another' -updated: 2024-01-11 ---- - -## Objective - -It may become necessary to move additional volumes from one OpenStack region to another, either because you would prefer to move to a newly-available OpenStack region, or because you want to migrate from [OVHcloud Labs](https://labs.ovh.com/) (formerly RunAbove) to the [Public Cloud](/links/public-cloud/compute). - -**This guide will show you how to transfer a volume backup from one OpenStack region to another.** - -## Requirements - -In order to do the transfer, you will need an environment with: - -- OpenStack CLI. Use [our guide to know how to prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Connectivity to OVHCloud OpenStack APIs. -- Available storage that matches the volume's disk size (for temporary backup storage). - -This environment will be used as a "jump host" to transfer the backup from one region to another. This environment can be an instance hosted on OVHCloud or your local machine. - -## Instructions - -### Create a backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -If the volume is attached to an instance, you must first detach it before creating the backup. - -Use the command below to retrieve the instance ID: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Next, run the following command to detatch the volume from its instance: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Next, create a backup in the form of an image, using the following command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Download the backup - -Now, run this command to list the available images: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Next, identify the volume backup from the list: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Finally, run this command to download the backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transfer the backup to another OpenStack region - -To start the transfer process, you first need to load new environment variables. - -> [!warning] -> -If you are transferring to an OpenStack region within the same project, just change the OS_REGION_NAME variable. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -If you are transferring your backup to another project or account, you will have to reload the environment variables linked to that account using the following command: - -```sh -$ source openrc.sh -``` - -To transfer the backup to the new OpenStack region, use this command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Create a volume from your backup - -To create a volume from your backup, use the backup ID as the image with this command: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Go further - -[Downloading and transferring an instance backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-sg.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-sg.md deleted file mode 100644 index 71884aa2210..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-sg.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: 'Transferring a volume backup from one OpenStack region to another' -excerpt: 'This guide will show you how to transfer a volume backup from one OpenStack region to another' -updated: 2024-01-11 ---- - -## Objective - -It may become necessary to move additional volumes from one OpenStack region to another, either because you would prefer to move to a newly-available OpenStack region, or because you want to migrate from [OVHcloud Labs](https://labs.ovh.com/) (formerly RunAbove) to the [Public Cloud](/links/public-cloud/compute). - -**This guide will show you how to transfer a volume backup from one OpenStack region to another.** - -## Requirements - -In order to do the transfer, you will need an environment with: - -- OpenStack CLI. Use [our guide to know how to prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Connectivity to OVHCloud OpenStack APIs. -- Available storage that matches the volume's disk size (for temporary backup storage). - -This environment will be used as a "jump host" to transfer the backup from one region to another. This environment can be an instance hosted on OVHCloud or your local machine. - -## Instructions - -### Create a backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -If the volume is attached to an instance, you must first detach it before creating the backup. - -Use the command below to retrieve the instance ID: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Next, run the following command to detatch the volume from its instance: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Next, create a backup in the form of an image, using the following command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Download the backup - -Now, run this command to list the available images: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Next, identify the volume backup from the list: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Finally, run this command to download the backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transfer the backup to another OpenStack region - -To start the transfer process, you first need to load new environment variables. - -> [!warning] -> -If you are transferring to an OpenStack region within the same project, just change the OS_REGION_NAME variable. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -If you are transferring your backup to another project or account, you will have to reload the environment variables linked to that account using the following command: - -```sh -$ source openrc.sh -``` - -To transfer the backup to the new OpenStack region, use this command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Create a volume from your backup - -To create a volume from your backup, use the backup ID as the image with this command: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Go further - -[Downloading and transferring an instance backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-us.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-us.md deleted file mode 100644 index 71884aa2210..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.en-us.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: 'Transferring a volume backup from one OpenStack region to another' -excerpt: 'This guide will show you how to transfer a volume backup from one OpenStack region to another' -updated: 2024-01-11 ---- - -## Objective - -It may become necessary to move additional volumes from one OpenStack region to another, either because you would prefer to move to a newly-available OpenStack region, or because you want to migrate from [OVHcloud Labs](https://labs.ovh.com/) (formerly RunAbove) to the [Public Cloud](/links/public-cloud/compute). - -**This guide will show you how to transfer a volume backup from one OpenStack region to another.** - -## Requirements - -In order to do the transfer, you will need an environment with: - -- OpenStack CLI. Use [our guide to know how to prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). -- Connectivity to OVHCloud OpenStack APIs. -- Available storage that matches the volume's disk size (for temporary backup storage). - -This environment will be used as a "jump host" to transfer the backup from one region to another. This environment can be an instance hosted on OVHCloud or your local machine. - -## Instructions - -### Create a backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -If the volume is attached to an instance, you must first detach it before creating the backup. - -Use the command below to retrieve the instance ID: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Next, run the following command to detatch the volume from its instance: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Next, create a backup in the form of an image, using the following command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Download the backup - -Now, run this command to list the available images: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Next, identify the volume backup from the list: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Finally, run this command to download the backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transfer the backup to another OpenStack region - -To start the transfer process, you first need to load new environment variables. - -> [!warning] -> -If you are transferring to an OpenStack region within the same project, just change the OS_REGION_NAME variable. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -If you are transferring your backup to another project or account, you will have to reload the environment variables linked to that account using the following command: - -```sh -$ source openrc.sh -``` - -To transfer the backup to the new OpenStack region, use this command: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Create a volume from your backup - -To create a volume from your backup, use the backup ID as the image with this command: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Go further - -[Downloading and transferring an instance backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.es-es.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.es-es.md deleted file mode 100644 index d7d71d2d88a..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.es-es.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -title: "Transferir la copia de seguridad de un volumen de una región de OpenStack a otra" -excerpt: "Cómo transferir una copia de seguridad de un volumen de una región de OpenStack a otra" -updated: 2024-01-11 ---- - -## Objetivo - -Es posible que necesite mover volúmenes adicionales de una región de OpenStack a otra, bien porque haya una nueva región disponible, bien porque quiera migrar de [OVHcloud Labs](https://labs.ovh.com/) al [Public Cloud](/links/public-cloud/compute). - -**Descubra cómo transferir una copia de seguridad de un volumen de una región de OpenStack a otra.** - -## Requisitos - -Para realizar la transferencia, necesitará un entorno con: - -- CLI OpenStack. Consulte nuestra guía «[Cómo preparar el entorno para utilizar la API de OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api)». -- Conectividad a la API OpenStack de OVHcloud. -- Espacio de almacenamiento disponible correspondiente al tamaño del disco del volumen (para el almacenamiento de copia de seguridad temporal). - -Este entorno se utilizará como « jump host » para transferir la copia de seguridad de una región a otra. Este entorno puede ser una instancia alojada en OVHcloud o en su máquina local. - -## Procedimiento - -### Crear una copia de seguridad - -```sh -root@server:~$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -Si el volumen está conectado a una instancia, primero deberá desvincularlo antes de crear la copia de seguridad. - -Utilice el siguiente comando para obtener el ID de la instancia: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -A continuación, ejecute el siguiente comando para desmontar el volumen desde su instancia: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Ahora cree una copia de seguridad como imagen con el siguiente comando: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Descargar la copia de seguridad - -Ejecute el siguiente comando para enumerar las imágenes disponibles: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Identifique la copia de seguridad en la lista: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Por último, ejecute este comando para descargar la copia de seguridad: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - - -### Transferir la copia de seguridad a otra región OpenStack - -Para iniciar el proceso de transferencia, primero debe cargar nuevas variables de entorno. - -> [!warning] -> -Si va a transferir su copia de seguridad a una región OpenStack del mismo proyecto, solo tiene que modificar la variable OS_REGION_NAME. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -Si va a transferir el backup a otro proyecto o cuenta, deberá volver a cargar las variables de entorno asociadas a dicha cuenta utilizando el siguiente comando: - -```sh -$ source openrc.sh -``` - -Para transferir la copia de seguridad a la nueva región OpenStack, utilice el siguiente comando: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Crear un volumen a partir de la copia de seguridad - -Utilice el ID de copia de seguridad como imagen con el siguiente comando: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Más información - -[Descargar y transferir la copia de seguridad de una instancia de una región de OpenStack a otra](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Interactúe con nuestra [comunidad de usuarios](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.es-us.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.es-us.md deleted file mode 100644 index d7d71d2d88a..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.es-us.md +++ /dev/null @@ -1,196 +0,0 @@ ---- -title: "Transferir la copia de seguridad de un volumen de una región de OpenStack a otra" -excerpt: "Cómo transferir una copia de seguridad de un volumen de una región de OpenStack a otra" -updated: 2024-01-11 ---- - -## Objetivo - -Es posible que necesite mover volúmenes adicionales de una región de OpenStack a otra, bien porque haya una nueva región disponible, bien porque quiera migrar de [OVHcloud Labs](https://labs.ovh.com/) al [Public Cloud](/links/public-cloud/compute). - -**Descubra cómo transferir una copia de seguridad de un volumen de una región de OpenStack a otra.** - -## Requisitos - -Para realizar la transferencia, necesitará un entorno con: - -- CLI OpenStack. Consulte nuestra guía «[Cómo preparar el entorno para utilizar la API de OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api)». -- Conectividad a la API OpenStack de OVHcloud. -- Espacio de almacenamiento disponible correspondiente al tamaño del disco del volumen (para el almacenamiento de copia de seguridad temporal). - -Este entorno se utilizará como « jump host » para transferir la copia de seguridad de una región a otra. Este entorno puede ser una instancia alojada en OVHcloud o en su máquina local. - -## Procedimiento - -### Crear una copia de seguridad - -```sh -root@server:~$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -Si el volumen está conectado a una instancia, primero deberá desvincularlo antes de crear la copia de seguridad. - -Utilice el siguiente comando para obtener el ID de la instancia: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -A continuación, ejecute el siguiente comando para desmontar el volumen desde su instancia: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Ahora cree una copia de seguridad como imagen con el siguiente comando: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Descargar la copia de seguridad - -Ejecute el siguiente comando para enumerar las imágenes disponibles: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Identifique la copia de seguridad en la lista: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Por último, ejecute este comando para descargar la copia de seguridad: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - - -### Transferir la copia de seguridad a otra región OpenStack - -Para iniciar el proceso de transferencia, primero debe cargar nuevas variables de entorno. - -> [!warning] -> -Si va a transferir su copia de seguridad a una región OpenStack del mismo proyecto, solo tiene que modificar la variable OS_REGION_NAME. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -Si va a transferir el backup a otro proyecto o cuenta, deberá volver a cargar las variables de entorno asociadas a dicha cuenta utilizando el siguiente comando: - -```sh -$ source openrc.sh -``` - -Para transferir la copia de seguridad a la nueva región OpenStack, utilice el siguiente comando: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Crear un volumen a partir de la copia de seguridad - -Utilice el ID de copia de seguridad como imagen con el siguiente comando: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Más información - -[Descargar y transferir la copia de seguridad de una instancia de una región de OpenStack a otra](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Interactúe con nuestra [comunidad de usuarios](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.fr-ca.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.fr-ca.md deleted file mode 100644 index 711337c4f90..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.fr-ca.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: "Transférer la sauvegarde d'un volume d'une région OpenStack à une autre" -excerpt: "Découvrez comment transférer une sauvegarde de volume d'une région OpenStack à une autre" -updated: 2024-01-11 ---- - -## Objectif - -Vous pouvez avoir besoin de déplacer des volumes additionnels d'une région OpenStack à une autre, soit parce qu'une nouvelle région est disponible, soit parce que vous souhaitez migrer d'[OVHcloud Labs](https://labs.ovh.com/) vers le [Public Cloud](/links/public-cloud/compute). - -**Découvrez comment transférer une sauvegarde de volume d'une région OpenStack à une autre.** - -## Prérequis - -Pour effectuer le transfert, vous aurez besoin d'un environnement avec : - -- CLI OpenStack. Consultez notre guide « [Comment préparer l'environnement pour utiliser l'API OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api) ». -- La Connectivité aux API OVHcloud OpenStack. -- De l'espace de stockage disponible correspondant à la taille du disque du volume (pour le stockage de sauvegarde temporaire). - -Cet environnement sera utilisé comme « jump host » pour transférer la sauvegarde d'une région à une autre. Cet environnement peut être une instance hébergée sur OVHcloud ou sur votre machine locale. - -## En pratique - -### Créer une sauvegarde - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -Si le volume est attaché à une instance, il faut d'abord le détacher avant de créer la sauvegarde. - -Utilisez la commande ci-dessous pour récupérer l'ID de l'instance : - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Ensuite, exécutez la commande suivante pour détacher le volume de son instance : - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Maintenant, créez une sauvegarde sous forme d'image à l'aide de cette commande suivante : - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Télécharger la sauvegarde - -Exécutez la commande suivante pour répertorier les images disponibles : - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Identifiez alors la sauvegarde dans la liste : - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Lancez enfin cette commande pour télécharger la sauvegarde : - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transférer la sauvegarde vers une autre région OpenStack - -Pour démarrer le processus de transfert, vous devez d'abord charger de nouvelles variables d'environnement. - -> [!warning] -> -Si vous transférez votre sauvegarde vers une région OpenStack au sein du même projet, vous devrez changer la variable `OS_REGION_NAME`. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -Si vous transférez votre sauvegarde vers un autre projet ou compte, vous devrez recharger les variables d'environnement liées à ce compte à l'aide de la commande suivante : - -```sh -$ source openrc.sh -``` - -Pour transférer la sauvegarde vers la nouvelle région OpenStack, utilisez cette commande : - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Créer un volume à partir de votre sauvegarde - -Pour créer un volume à partir de votre sauvegarde, utilisez l'ID de la sauvegarde comme image avec cette commande : - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Aller plus loin - -[Télécharger et transférer la sauvegarde d'une instance d'une région OpenStack à une autre](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.fr-fr.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.fr-fr.md deleted file mode 100644 index b1d3f4cf499..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.fr-fr.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: "Transférer la sauvegarde d'un volume d'une région OpenStack à une autre" -excerpt: "Découvrez comment transférer une sauvegarde de volume d'une région OpenStack à une autre" -updated: 2024-01-11 ---- - -## Objectif - -Vous pouvez avoir besoin de déplacer des volumes additionnels d'une région OpenStack à une autre, soit parce qu'une nouvelle région est disponible, soit parce que vous souhaitez migrer d'[OVHcloud Labs](https://labs.ovh.com/) vers le [Public Cloud](/links/public-cloud/compute). - -**Découvrez comment transférer une sauvegarde de volume d'une région OpenStack à une autre.** - -## Prérequis - -Pour effectuer le transfert, vous aurez besoin d'un environnement avec : - -- CLI OpenStack. Consultez notre guide « [Comment préparer l'environnement pour utiliser l'API OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api) ». -- La Connectivité aux API OVHcloud OpenStack. -- De l'espace de stockage disponible correspondant à la taille du disque du volume (pour le stockage de sauvegarde temporaire). - -Cet environnement sera utilisé comme « jump host » pour transférer la sauvegarde d'une région à une autre. Cet environnement peut être une instance hébergée sur OVHcloud ou sur votre machine locale. - -## En pratique - -### Créer une sauvegarde - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -Si le volume est attaché à une instance, il faut d'abord le détacher avant de créer la sauvegarde. - -Utilisez la commande ci-dessous pour récupérer l'ID de l'instance : - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Ensuite, exécutez la commande suivante pour détacher le volume de son instance : - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Maintenant, créez une sauvegarde sous forme d'image à l'aide de cette commande suivante : - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Télécharger la sauvegarde - -Exécutez la commande suivante pour répertorier les images disponibles : - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Identifiez alors la sauvegarde dans la liste : - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Lancez enfin cette commande pour télécharger la sauvegarde : - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transférer la sauvegarde vers une autre région OpenStack - -Pour démarrer le processus de transfert, vous devez d'abord charger de nouvelles variables d'environnement. - -> [!warning] -> -Si vous transférez votre sauvegarde vers une région OpenStack au sein du même projet, vous devrez changer la variable `OS_REGION_NAME`. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -Si vous transférez votre sauvegarde vers un autre projet ou compte, vous devrez recharger les variables d'environnement liées à ce compte à l'aide de la commande suivante : - -```sh -$ source openrc.sh -``` - -Pour transférer la sauvegarde vers la nouvelle région OpenStack, utilisez cette commande : - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Créer un volume à partir de votre sauvegarde - -Pour créer un volume à partir de votre sauvegarde, utilisez l'ID de la sauvegarde comme image avec cette commande : - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Aller plus loin - -[Télécharger et transférer la sauvegarde d'une instance d'une région OpenStack à une autre](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.it-it.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.it-it.md deleted file mode 100644 index 8d238a2c594..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.it-it.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -title: "Trasferire il backup di un volume da una Region OpenStack ad un'altra" -excerpt: "Scopri come trasferire un backup di volume da una Region OpenStack ad un’altra" -updated: 2024-01-11 ---- - -## Obiettivo - -In alcuni casi potrebbe essere necessario spostare volumi aggiuntivi da una Region OpenStack a un'altra, perché è disponibile una nuova Region o perché si desidera migrare da [OVHcloud Labs](https://labs.ovh.com/) al [Public Cloud](/links/public-cloud/public-cloud). - -**Questa guida ti mostra come migrare un backup di un volume da una Region OpenStack ad un'altra.** - -## Prerequisiti - -- CLI OpenStack. Consulta la nostra guida "[Come preparare l’ambiente per utilizzare l’API OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api)". -- Connettività con le API OVHcloud OpenStack. -- Spazio di storage disponibile corrispondente alla dimensione del disco del volume (per lo storage di backup temporaneo). - -Questo ambiente verrà utilizzato come "jump host" per trasferire il backup da una regione all'altra. L’ambiente può essere costituito da un’istanza ospitata in OVHcloud o sulla macchina locale. - -## Procedura - -### Crea un backup - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -Se il volume è associato a un’istanza, è necessario scollegarlo prima di creare il backup. - -Utilizza il comando qui sotto per recuperare l’ID dell’istanza: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Eseguire quindi il comando seguente per smontare il volume dalla sua istanza: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Crea un backup sotto forma di immagine utilizzando questo comando: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Gestisci i tuoi backup - -Per visualizzare le immagini disponibili, esegui questo comando: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Identifica il backup nella lista: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Esegui questo comando per scaricare il backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Trasferisci il backup in un'altra Region Openstack - -Prima di avviare il processo di trasferimento è necessario impostare le nuove variabili d’ambiente. - -> [!warning] -> -Se si trasferisce il backup in una regione Openstack dello stesso progetto, è sufficiente modificare la variabile OS_REGION_NAME. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -Per migrare il backup verso un altro progetto o account, è necessario ricaricare le variabili d'ambiente associate a questo account utilizzando il seguente comando: - -```sh -$ source openrc.sh -``` - -Per trasferire il backup nella nuova Region Openstack, esegui il comando: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Crea un volume a partire dal tuo backup - -Per effettuare questa operazione, esegui il seguente comando utilizzando l’identificativo dell’immagine del backup: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Per saperne di più - -[Scaricare e trasferire il backup di un’istanza da una Region OpenStack ad un’altra](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Contatta la nostra [Community di utenti](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.pl-pl.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.pl-pl.md deleted file mode 100644 index f8bc2c33c58..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.pl-pl.md +++ /dev/null @@ -1,195 +0,0 @@ ---- -title: "Przenoszenie kopii zapasowej wolumenu z jednego regionu OpenStack do innego" -excerpt: "Dowiedz się, jak przenieść kopię zapasową wolumenu z jednego regionu OpenStack do innego" -updated: 2024-01-11 ---- - -## Wprowadzenie - -Może zaistnieć potrzeba przeniesienia dodatkowych wolumenów z jednego regionu OpenStack do innego, ponieważ jest dostępny nowy region lub chcesz przenieść z [OVHcloud Labs](https://labs.ovh.com/) do [Public Cloud](/links/public-cloud/compute). - -**Dowiedz się, jak przenieść kopię zapasową wolumenu z jednego regionu OpenStack do innego.** - -## Wymagania początkowe - -Do przeniesienia będziesz potrzebował środowiska z: - -- CLI OpenStack. Zapoznaj się z przewodnikiem "[Jak przygotować środowisko do korzystania z API OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api)". -- Łączność z API OVHcloud OpenStack. -- Dostępnego miejsca do magazynowania odpowiadającego rozmiarowi dysku woluminu (dla tymczasowego magazynu kopii zapasowych). - -Środowisko to będzie używane jako "jump host" do przenoszenia kopii zapasowej z jednego regionu do innego. Środowisko to może być instancją hostowaną w OVHcloud lub na Twojej maszynie lokalnej. - -## W praktyce - -### Utwórz kopię zapasową - -```sh -$ openstack volume list -+--------------------------------------+--------------+--------+------+----------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+----------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+----------------------------------+ -``` - -Jeśli wolumin jest podłączony do instancji, przed utworzeniem kopii zapasowej należy go odłączyć. - -Użyj poniższego polecenia, aby pobrać ID instancji: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -Następnie wprowadź poniższą komendę, aby odmontować wolumin z jego instancji: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Teraz utwórz obrazkową kopię zapasową, używając następującego polecenia: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Pobierz kopię zapasową - -Aby wyświetlić dostępne obrazy, wprowadź następującą komendę: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -Wyszukaj następnie kopię zapasową na liście: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Następnie wprowadź następującą komendę, aby pobrać kopię zapasową: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Przeniesienie kopii zapasowej do innego regionu Openstack - -Aby rozpocząć proces transferu, należy najpierw załadować nowe zmienne środowiskowe. - -> [!warning] -> -Jeśli przenosisz Twoją kopię zapasową do regionu Openstack w tym samym projekcie, zmień zmienną OS_REGION_NAME. -> - -```sh -$ export OS_REGION_NAME=SBG1 -``` - -Jeśli przenosisz kopię zapasową instancji do innego projektu lub na inne konto, pobierz ponownie zmienne środowiskowe powiązane z tym kontem, używając następującej komendy: - -```sh -$ source openrc.sh -``` - -Aby przenieść kopię zapasową do nowego regionu Openstack, użyj poniższego polecenia: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Utwórz wolumen z kopii zapasowej - -Użyj identyfikatora kopii zapasowej jako obrazu za pomocą następującego polecenia: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Sprawdź również - -[Pobieranie i przesyłanie kopii zapasowej instancji z jednego regionu OpenStack do innego](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Dołącz do [grona naszych użytkowników](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.pt-pt.md b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.pt-pt.md deleted file mode 100644 index 35fd79d199c..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/guide.pt-pt.md +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: "Transferir o backup de um volume de uma região OpenStack para outra" -excerpt: "Descubra como transferir um backup de volume de uma região OpenStack para outra" -updated: 2024-01-11 ---- - -> [!primary] -> Esta tradução foi automaticamente gerada pelo nosso parceiro SYSTRAN. Em certos casos, poderão ocorrer formulações imprecisas, como por exemplo nomes de botões ou detalhes técnicos. Recomendamos que consulte a versão inglesa ou francesa do manual, caso tenha alguma dúvida. Se nos quiser ajudar a melhorar esta tradução, clique em "Contribuir" nesta página. -> - -## Objetivo - -Poderá ter de migrar volumes adicionais de uma região OpenStack para outra, quer seja porque uma nova região está disponível, quer seja porque deseja migrar de [OVHcloud Labs](https://labs.ovh.com/) para [Public Cloud](/links/public-cloud/compute). - -**Descubra como transferir um backup de volume de uma região do OpenStack para outra..** - -## Requisitos - -- CLI OpenStack. Consulte o nosso guia « [Como preparar o ambiente para utilizar a API OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api) ». -- A Conectividade às API OVHcloud OpenStack. -- Do espaço de armazenamento disponível correspondente ao tamanho do disco do volume (para o armazenamento de backup temporário). - -Este ambiente será utilizado como « jump host » para transferir a cópia de segurança de uma região para outra. Este ambiente pode ser uma instância alojada na OVHcloud ou na sua máquina local. - -## Instruções - -### Criação de um backup - -```sh -openstack volume list -+--------------------------------------+--------------+--------+------+------------------------------------+ -| ID | Display Name | Status | Size | Attached to | -+--------------------------------------+--------------+--------+------+------------------------------------+ -| 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | volume | in-use | 10 | Attached to Server 1 on /dev/sdb | -+--------------------------------------+--------------+--------+------+------------------------------------+ -``` - -Se o volume estiver associado a uma instância, deve em primeiro lugar desassociá-lo antes de criar o backup. - -Utilizar o comando abaixo para recuperar o ID da instância: - -```sh -$ openstack server list -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -| ID | Name | Status | Networks | Image | Flavor | -+--------------------------------------+-----------+--------+--------------------------------------------------------------------+ -| a8b6b51-4413-4d1a-8113-9597d804b07e | Server 1 | ACTIVE | Ext-Net=155.55.55.155, 2607:5300:23x:5000::8d5 | Centos 7 | b2-7 | -+--------------------------------------+-----------+--------+------------------------------------------------+----------+--------+ -``` - -De seguida, execute o comando abaixo para desmontar o volume a partir da instância: - -```sh -$ openstack server remove volume a8b6b51-4413-4d1a-8113-9597d804b07e 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 -``` - -Agora, crie um backup sob a forma de imagem através deste comando: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --volume 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 snap_volume -+---------------------+------------------------------------------------------+ -| Property | Value | -+---------------------+------------------------------------------------------+ -| container_format | bare | -| disk_format | qcow2 | -| display_description | | -| id | 673b0ad9-1fca-485c-ae2b-8ee271b71dc7 | -| image_id | 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | -| image_name | snap_volume | -| size | 10 | -| status | uploading | -| updated_at | 2015-10-21T08:33:34.000000 | -| volume_type | [..........] | -+---------------------+------------------------------------------------------+ -``` - -### Descarregar o backup - -Execute o seguinte comando para listar as imagens disponíveis: - -```sh -$ openstack image list -+--------------------------------------+--------------------------------+--------+ -| ID | Name | Status | -+--------------------------------------+--------------------------------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 73958794-ecf6-4e68-ab7f-1506eadac05b | Debian 7 | active | -| bdcb5042-3548-40d0-b06f-79551d3b4377 | Debian 8 | active | -| 7250cc02-ccc1-4a46-8361-a3d6d9113177 | Fedora 19 | active | -| 57b9722a-e6e8-4a55-8146-3e36a477eb78 | Fedora 20 | active | -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | active | -| 3bda2a66-5c24-4b1d-b850-83333b580674 | Ubuntu 12.04 | active | -| 9bfac38c-688f-4b63-bf3b-69155463c0e7 | Ubuntu 14.04 | active | -| 6a123897-a5bb-46cd-8f5d-ecf9ab9877f2 | Windows-Server-2012-r2 | active | -+--------------------------------------+--------------------------------+--------+ -``` - -De seguida, identifique o backup na lista: - -```sh -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -| ID | Name | disk_format |container_format| | Status | -+--------------------------------------+---------------------------+----------------+-----------+--------+ -| 8625f87e-8248-4e62-a0ce-a89c7bd1a9be | snap_volume | qcow2 | bare | 319356928 | active | -+--------------------------------------+-------------+-------------+----------------+-----------+--------+ -``` - -Por fim, execute este comando para descarregar o backup: - -```sh -$ openstack image save --file snap_volume.qcow 8625f87e-8248-4e62-a0ce-a89c7bd1a9be -``` - -### Transferir a cópia de segurança para outra região OpenStack - -Para lançar o processo de transferência, deverá começar por carregar novas variáveis de ambiente. - -> [!warning] -> -Se transferir a sua cópia de segurança para uma região OpenStack no mesmo projeto, deverá alterar a variável OS_REGION_NAME. -> - -```sh -export OS_REGION_NAME=SBG1 -``` - -Se transferir o seu backup para outro projeto ou conta, deverá recarregar as variáveis de ambiente associadas a esta conta através do seguinte comando: - -```sh -$ source openrc.sh -``` - -Para transferir a cópia de segurança para a nova região OpenStack, utilize o comando abaixo: - -```sh -$ openstack image create --disk-format qcow2 --container-format bare --file snap_volume.qcow snap-volume -+------------------+------------------------------------------------------+ -| Field | Value | -+------------------+------------------------------------------------------+ -| checksum | None | -| container_format | bare | -| created_at | 2019-03-22T15:26:04Z | -| disk_format | qcow2 | -| file | /v2/images/783136d3-365a-49c6-9024-1e2f9c2db51a/file | -| id | aa2a39c6-433c-4e94-995a-a12c4398d457 | -| min_disk | 0 | -| min_ram | 0 | -| name | snap_volume | -| owner | b3e26xxxxxxxxxxxxxxxxxxx12b0ba29 | -| properties | locations='[]' | -| protected | False | -| schema | /v2/schemas/image | -| size | None | -| status | queued | -| tags | | -| updated_at | 2019-03-22T15:26:04Z | -| virtual_size | None | -| visibility | private | -+------------------+------------------------------------------------------+ -``` - -### Crie um volume a partir do seu backup - -Utilize o ID da backup como imagem com o seguinte comando: - -```sh -$ openstack volume create --type classic --image aa2a39c6-433c-4e94-995a-a12c4398d457 --size 10 volume_from_snap -+---------------------+--------------------------------------+ -| Field | Value | -+---------------------+--------------------------------------+ -| attachments | [] | -| availability_zone | nova | -| bootable | false | -| consistencygroup_id | None | -| created_at | 2019-03-22T15:39:39.880479 | -| description | None | -| encrypted | False | -| id | 938b13c9-414e-45b5-b0fc-cfea743f54e1 | -| multiattach | False | -| name | volume_from_snap | -| properties | | -| replication_status | disabled | -| size | 10 | -| snapshot_id | None | -| source_volid | None | -| status | creating | -| type | classic | -| updated_at | None | -| user_id | f63a1d2f27df455bb306bb79b0f2e2aa | -+---------------------+--------------------------------------+ -``` - -## Quer saber mais? - -[Descarregar e transferir a cópia de segurança de uma instância de uma região OpenStack para outra](/pages/public_cloud/compute/transfer_instance_backup_from_one_datacentre_to_another). - -Fale com nossa [comunidade de utilizadores](/links/community). \ No newline at end of file diff --git a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/meta.yaml b/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/meta.yaml deleted file mode 100755 index 5bfab9a89e6..00000000000 --- a/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another/meta.yaml +++ /dev/null @@ -1,4 +0,0 @@ -id: 0a8f7660-ced3-4af7-980a-c29416609251 -full_slug: public-cloud-compute-storage-transfer-volume-backup-between-datacenters -reference_category: public-cloud-storage-block-storage -translation_banner: true \ No newline at end of file diff --git a/pages/public_cloud/compute/volume-backup/guide.de-de.md b/pages/public_cloud/compute/volume-backup/guide.de-de.md index 79a922841c2..4664083d7b0 100644 --- a/pages/public_cloud/compute/volume-backup/guide.de-de.md +++ b/pages/public_cloud/compute/volume-backup/guide.de-de.md @@ -90,6 +90,4 @@ Weitere Informationen zu diesem Thema finden Sie in unserer [Anleitung zur Erste [Die Größe einer zusätzlichen Disk erweitern](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Übertragen von Volume-Backups von einer OpenStack-Region in eine andere](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Für den Austausch mit unserer User Community gehen Sie auf . diff --git a/pages/public_cloud/compute/volume-backup/guide.en-asia.md b/pages/public_cloud/compute/volume-backup/guide.en-asia.md index bfc3eee0e05..ada6e040fbe 100644 --- a/pages/public_cloud/compute/volume-backup/guide.en-asia.md +++ b/pages/public_cloud/compute/volume-backup/guide.en-asia.md @@ -78,6 +78,4 @@ You can find further information in [this guide](/pages/public_cloud/compute/cre [Increasing the size of an additional disk](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferring a volume backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Join our [community of users](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.en-au.md b/pages/public_cloud/compute/volume-backup/guide.en-au.md index bfc3eee0e05..ada6e040fbe 100644 --- a/pages/public_cloud/compute/volume-backup/guide.en-au.md +++ b/pages/public_cloud/compute/volume-backup/guide.en-au.md @@ -78,6 +78,4 @@ You can find further information in [this guide](/pages/public_cloud/compute/cre [Increasing the size of an additional disk](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferring a volume backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Join our [community of users](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.en-ca.md b/pages/public_cloud/compute/volume-backup/guide.en-ca.md index bfc3eee0e05..ada6e040fbe 100644 --- a/pages/public_cloud/compute/volume-backup/guide.en-ca.md +++ b/pages/public_cloud/compute/volume-backup/guide.en-ca.md @@ -78,6 +78,4 @@ You can find further information in [this guide](/pages/public_cloud/compute/cre [Increasing the size of an additional disk](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferring a volume backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Join our [community of users](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.en-gb.md b/pages/public_cloud/compute/volume-backup/guide.en-gb.md index bfc3eee0e05..ada6e040fbe 100644 --- a/pages/public_cloud/compute/volume-backup/guide.en-gb.md +++ b/pages/public_cloud/compute/volume-backup/guide.en-gb.md @@ -78,6 +78,4 @@ You can find further information in [this guide](/pages/public_cloud/compute/cre [Increasing the size of an additional disk](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferring a volume backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Join our [community of users](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.en-ie.md b/pages/public_cloud/compute/volume-backup/guide.en-ie.md index bfc3eee0e05..ada6e040fbe 100644 --- a/pages/public_cloud/compute/volume-backup/guide.en-ie.md +++ b/pages/public_cloud/compute/volume-backup/guide.en-ie.md @@ -78,6 +78,4 @@ You can find further information in [this guide](/pages/public_cloud/compute/cre [Increasing the size of an additional disk](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferring a volume backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Join our [community of users](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.en-sg.md b/pages/public_cloud/compute/volume-backup/guide.en-sg.md index bfc3eee0e05..ada6e040fbe 100644 --- a/pages/public_cloud/compute/volume-backup/guide.en-sg.md +++ b/pages/public_cloud/compute/volume-backup/guide.en-sg.md @@ -78,6 +78,4 @@ You can find further information in [this guide](/pages/public_cloud/compute/cre [Increasing the size of an additional disk](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferring a volume backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Join our [community of users](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.en-us.md b/pages/public_cloud/compute/volume-backup/guide.en-us.md index bfc3eee0e05..ada6e040fbe 100644 --- a/pages/public_cloud/compute/volume-backup/guide.en-us.md +++ b/pages/public_cloud/compute/volume-backup/guide.en-us.md @@ -78,6 +78,4 @@ You can find further information in [this guide](/pages/public_cloud/compute/cre [Increasing the size of an additional disk](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferring a volume backup from one OpenStack region to another](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Join our [community of users](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.es-es.md b/pages/public_cloud/compute/volume-backup/guide.es-es.md index 669ea865dfe..a5b245e91f9 100644 --- a/pages/public_cloud/compute/volume-backup/guide.es-es.md +++ b/pages/public_cloud/compute/volume-backup/guide.es-es.md @@ -91,6 +91,4 @@ Para más información, consulte [nuestra guía sobre la creación de un volumen [Aumentar el tamaño de un disco adicional](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferir la copia de seguridad de un volumen de una región de OpenStack a otra](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Interactúe con nuestra comunidad de usuarios en . diff --git a/pages/public_cloud/compute/volume-backup/guide.es-us.md b/pages/public_cloud/compute/volume-backup/guide.es-us.md index aa11c031092..21c2dc59e80 100644 --- a/pages/public_cloud/compute/volume-backup/guide.es-us.md +++ b/pages/public_cloud/compute/volume-backup/guide.es-us.md @@ -91,6 +91,4 @@ Para más información, consulte [nuestra guía sobre la creación de un volumen [Aumentar el tamaño de un disco adicional](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferir la copia de seguridad de un volumen de una región de OpenStack a otra](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Interactúe con nuestra comunidad de usuarios en . diff --git a/pages/public_cloud/compute/volume-backup/guide.fr-ca.md b/pages/public_cloud/compute/volume-backup/guide.fr-ca.md index c0111f49ad0..4df52a66c48 100644 --- a/pages/public_cloud/compute/volume-backup/guide.fr-ca.md +++ b/pages/public_cloud/compute/volume-backup/guide.fr-ca.md @@ -87,6 +87,4 @@ Retrouvez plus d’informations à ce sujet dans [notre guide sur la création d [Augmenter la taille d’un disque supplémentaire](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transférer la sauvegarde d'un volume d'une région OpenStack à une autre](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.fr-fr.md b/pages/public_cloud/compute/volume-backup/guide.fr-fr.md index b39cc15ad3a..c2624a1e471 100644 --- a/pages/public_cloud/compute/volume-backup/guide.fr-fr.md +++ b/pages/public_cloud/compute/volume-backup/guide.fr-fr.md @@ -86,6 +86,4 @@ Retrouvez plus d’informations à ce sujet dans [notre guide sur la création d [Augmenter la taille d’un disque supplémentaire](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transférer la sauvegarde d'un volume d'une région OpenStack à une autre](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/public_cloud/compute/volume-backup/guide.it-it.md b/pages/public_cloud/compute/volume-backup/guide.it-it.md index 350ced193ed..887804a82ad 100644 --- a/pages/public_cloud/compute/volume-backup/guide.it-it.md +++ b/pages/public_cloud/compute/volume-backup/guide.it-it.md @@ -91,6 +91,4 @@ Per maggiori informazioni, consulta la [nostra guida sulla creazione di un volum [Aumenta la dimensione di un disco aggiuntivo](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Trasferire il backup di un volume da una Region OpenStack ad un'altra](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Contatta la nostra Community di utenti all’indirizzo . diff --git a/pages/public_cloud/compute/volume-backup/guide.pl-pl.md b/pages/public_cloud/compute/volume-backup/guide.pl-pl.md index fd705b66d66..6aace36cd15 100644 --- a/pages/public_cloud/compute/volume-backup/guide.pl-pl.md +++ b/pages/public_cloud/compute/volume-backup/guide.pl-pl.md @@ -91,6 +91,4 @@ Więcej informacji na ten temat znajdziesz w [naszym przewodniku dotyczącym two [Zwiększ rozmiar dodatkowego dysku](/pages/public_cloud/compute/create_and_configure_an_additional_disk_on_an_instance) -[Przenoszenie kopii zapasowej wolumenu z jednego regionu OpenStack do innego](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Dołącz do społeczności naszych użytkowników na stronie . diff --git a/pages/public_cloud/compute/volume-backup/guide.pt-pt.md b/pages/public_cloud/compute/volume-backup/guide.pt-pt.md index eee9b3829a5..d170d52b3cc 100644 --- a/pages/public_cloud/compute/volume-backup/guide.pt-pt.md +++ b/pages/public_cloud/compute/volume-backup/guide.pt-pt.md @@ -91,6 +91,4 @@ Para mais informações, consulte o [nosso manual sobre a criação de um volume [Aumentar o tamanho de um disco adicional](/pages/public_cloud/compute/increase_the_size_of_an_additional_disk) -[Transferir o backup de um volume de uma região OpenStack para outra](/pages/public_cloud/compute/transfer_volume_backup_from_one_datacentre_to_another) - Fale com a nossa comunidade de utilizadores em .