--- title: "Enterprise File Storage - Clone a volume" description: "Find out how to clone a volume from your Enterprise File Storage solution using the OVHcloud API" url: https://docs.ovhcloud.com/en/guides/storage-and-backup/file-storage/enterprise-file-storage/netapp-clone-volume lang: en lastUpdated: 2024-12-09 --- # Enterprise File Storage - Clone a volume ## Objective A **volume clone** is a duplicate of an existing volume that can be used as any standard volume. It is created from a snapshot of an active volume. Changes made to the parent volume after the clone is created will not be reflected on the cloned volume. :::info In this guide, a volume is also called “share” as in the OVHcloud API. ::: **Discover the volume clone feature and learn how to clone a volume from your Enterprise File Storage offer using the OVHcloud API.** ## Use cases Volume clones may be created for a variety of reasons. Below are some examples. ### Allow access to up-to-date data for dev, QA or training environments Training, QA or development environments may need to be updated with data from a production environment to ensure that development and training are performed with the current dataset. Using the volume clone feature, automated operations can be put in place to ensure that the data in these environments remains up to date without giving access to production data. ![CloneVolumeUseCaseEnvironmentSync](/images/storage-and-backup/file-storage/enterprise-file-storage/netapp-clone-volume/clone_volume_use_case_1.png) ### Address and remedy logical data corruption Logical data corruptions can be caused by software errors, human errors or malicious activity. Unfortunately, logical data corruptions often cannot be addressed with standard high-availability and disaster recovery solutions. By creating Snapshots at a regular interval using a [Snapshot Policy](/en/guides/storage-and-backup/file-storage/enterprise-file-storage/netapp-snapshot-policy.md) and with the help of the volume clone feature it is possible to restore the system to a point in time before the corruption occurred. It is also possible to isolate the corrupted data and try to resolve the cause of the corruption by analysing the problem in a separate system. ![CloneVolumeUseCaseDataCorruption](/images/storage-and-backup/file-storage/enterprise-file-storage/netapp-clone-volume/clone_volume_use_case_2.png) ## Requirements - An active OVHcloud [Enterprise File Storage](https://www.ovhcloud.com/en-gb/storage-solutions/enterprise-file-storage/) service - Access to the [OVHcloud API](https://eu.api.ovh.com/) - An Enterprise File Storage volume with a `manual` snapshot *** ### OVHcloud Control Panel Access - **Direct link:** Enterprise File Storage - **Navigation path:** Bare Metal Cloud > Enterprise File Storage *** :::info You can create a volume and a `manual` snapshot through the [OVHcloud API](https://eu.api.ovh.com/) or the OVHcloud Control Panel . ::: :::tip If you are not familiar with using the OVHcloud API, please refer to our guide on [Getting started with the OVHcloud API](/en/guides/manage-and-operate/api/first-steps.md). ::: ## Limitations - Only `manual` snapshots can be used to create a new volume. However, if you want to clone a volume using an `automatic` snapshot, you can hold the snapshot to make it a `manual` snapshot using the `/hold` API endpoint before using it. Please refer to the guide [Enterprise File Storage - Hold an automatic snapshot](/en/guides/storage-and-backup/file-storage/enterprise-file-storage/netapp-hold-automatic-snapshot.md) for more information. - Creating volumes from `system` snapshots is not supported. - Cloned volume size should be **equal or greater** than the snapshot used for cloning. ## Instructions 1\. Identify the `id` of the snapshot that will be used with the following API call: 🇪🇺EU▾ [GET/storage/netapp/{serviceName}/share/{shareId}/snapshot](https://eu.api.ovh.com/console/?section=/storage/netapp&branch=v1#get-/storage/netapp/-serviceName-/share/-shareId-/snapshot) **Parameters:** - `serviceName`: is the service unique ID - `shareId`: is the share to clone from ![CloneVolume](/images/storage-and-backup/file-storage/enterprise-file-storage/netapp-clone-volume/clone_volume_step_1.png) 2\. Clone the volume from the snapshot by using the `/share` API route: 🇪🇺EU▾ [POST/storage/netapp/{serviceName}/share](https://eu.api.ovh.com/console/?section=/storage/netapp&branch=v1#post-/storage/netapp/-serviceName-/share) **Parameters:** - `serviceName`: is the service unique ID - `size`: is the share size. It should be **equal or greater** than the snapshot size. - `protocol`: is the share protocol. Only NFS is allowed. - `snapshotID`: is the snapshot ID to use when creating the share - `name`: (Optional) is the share name - `description`: (Optional) is the share description ![CloneVolume](/images/storage-and-backup/file-storage/enterprise-file-storage/netapp-clone-volume/clone_volume_step_2.png) The OVHcloud API will return an HTTP 201 (Created) code along with volume information. The volume status will be set to `creating_from_snapshot` and then will change to `available` once the volume creation is complete. Depending on the snapshot size, the volume creation may take some time. **A new volume is now created from it's parent volume snapshot.** ## Go further If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/professional-services/) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project. Join our [community of users](https://community.ovhcloud.com/).