|
| 1 | +--- |
| 2 | +title: Cold Storage product reversibility policy |
| 3 | +updated: 2025-06-13 |
| 4 | +--- |
| 5 | + |
| 6 | +## Objective |
| 7 | + |
| 8 | +This document outlines the reversibility policy for the product Cold Storage covering OVHcloud's Cold Archive offer. |
| 9 | + |
| 10 | +This policy aims at implementing the global reversibility principles and requirements of SWIPO IaaS Code of Conduct for Cloud Providers. |
| 11 | + |
| 12 | +## Features map |
| 13 | + |
| 14 | +The product features are divided into three categories: |
| 15 | + |
| 16 | +- The **core features** for which we guarantee the ability to migrate. |
| 17 | +- The **OVHcloud implementation**, which migration will require adaptations to a new environment. |
| 18 | +- **Specific functionalities** which migration as such is impossible to guarantee as they are tied to OVHcloud environment or specific developments. |
| 19 | + |
| 20 | +### Core features |
| 21 | + |
| 22 | +|Feature|Description|Available formats|Migration model|Available documentation| |
| 23 | +|---|---|---|---|---| |
| 24 | +| **Standard S3<sup>1</sup> API Compatibility**| Access and management via S3-compatible API (RESTful, AWS CLI tools, SDK, etc.). | S3 (REST, JSON, objects) | **Incoming**: Direct upload into an Object Storage bucket via S3 API, CLI, or SDK. <br> **Outgoing**: Direct retrieval/export via S3 API, CLI, or SDK to any other S3-compatible provider. | [Cold Archive offer presentation](/links/public-cloud/cold-archive) <br> [Cold Archive offer documentation](/products/storage-object-storage) | |
| 25 | +| **Massive Import/Export of objects** | Batch data migration using S3 commands (`aws s3 cp/sync`, etc.). | S3 (objects, folders)| **Incoming**: Copy data from another S3 solution to OVHcloud Object Storage bucket. <br> **Outgoing**: Massive export via same tools to another S3 or compatible platform. | [Cold Archive offer documentation](/products/storage-object-storage) | |
| 26 | +| **Server-Side Encryption**| Native AES-256 bucket-level encryption, compatible with S3 SSE. | S3 (SSE-S3, SSE-C) | **Incoming**: Upload of encrypted or unencrypted data, transparently handled. <br> **Outgoing**: Export without adaptation; encryption maintained or reprocessed by the target. | [Cold Archive offer documentation](/products/storage-object-storage) | |
| 27 | +| **Long-Term data Retention** | Data stored on magnetic tapes, with a lifespan over 10 years. | S3 (objects) | **Incoming**: Import without adaptation. <br> **Outgoing**: Export of objects via S3 API; retrieval on any compatible storage. |[Cold Archive offer documentation](/products/storage-object-storage) | |
| 28 | + |
| 29 | +### OVHcloud implementation |
| 30 | + |
| 31 | +|Feature|Description|Available formats|Migration model|Available documentation| |
| 32 | +|---|---|---|---|---| |
| 33 | +| **Full Bucket Archiving** | Archiving applies to the entire bucket (no object-level archiving). | S3 (bucket) | **Incoming**: Requires grouping of objects to archive into a dedicated bucket. <br> **Outgoing**: Export objects from the bucket, then import into the target (adaptation may be required if the target does not support bucket-level archiving). | [Cold Archive offer documentation](/products/storage-object-storage) | |
| 34 | +| **Delayed Restore ("unfreeze")** | Data must be "unfrozen" before download (several hours of latency). | S3 (objects) | **Incoming**: Not applicable. <br> **Outgoing**: User must initiate a restore ("unfreeze") request, then download the objects within a 24-hour window; adaptation needed if the target lacks this mechanism. | [Cold Archive offer documentation](/products/storage-object-storage) | |
| 35 | +| **Data Immutability** | Ability to make data immutable for a defined or indefinite period (WORM). | S3 (Object Lock) | **Incoming**: Source must support S3 data immutability. <br> **Outgoing**: Export possible, but target must support S3 locking or require manual adjustment of immutability policies. | [Cold Archive offer documentation](/products/storage-object-storage) | |
| 36 | + |
| 37 | +### Specific functionalities |
| 38 | + |
| 39 | +|Feature|Description|Available formats|Migration model|Available documentation| |
| 40 | +|---|---|---|---|---| |
| 41 | +|**Anti-DDoS**|The anti-DDoS is a set of equipment and means put in place to absorb distributed denial of service attacks. It includes an analysis of traffic, the "aspiration" towards a specialized network, and mitigation, ensured by VAC technology developed by OVHcloud.|N/A|**Incoming**: The Anti-DDoS is a component of our infrastructure, enabled by default. No action is required.<br><br>**Outcoming**: Order and configure an anti-DDoS with the new provider.|[OVHcloud anti-DDoS protection](/links/security/antiddos)<br><br>[Anti-DDoS Technology](/links/security/antiddos)| |
| 42 | +| **OVHcloud 4-Datacenter Architecture** | Distribution across 4 datacenters in France using 8+4 erasure coding. | N/A | **Incoming**: Not applicable. <br> **Outgoing**: Not transferable, depends on the target architecture. | [Cold Archive offer presentation](/links/public-cloud/cold-archive) | |
| 43 | +| **Management via OVHcloud Manager/API** | Proprietary OVHcloud graphical interface and APIs for archive management. | N/A | **Incoming**: Not applicable. <br> **Outgoing**: Scripts/APIs need to be rewritten for the target; manual management may be required. | [Cold Archive offer documentation](/products/storage-object-storage) | |
| 44 | + |
| 45 | +## Architecture listing |
| 46 | + |
| 47 | +OVHcloud's Cold Storage product is based on a geo-distributed architecture across four physically separated data centers (several kilometers apart), using IBM magnetic tape technology. Data is stored using 8+4 erasure coding, ensuring extreme resilience and tolerance to the loss of an entire site. |
| 48 | + |
| 49 | +## Partner services |
| 50 | + |
| 51 | +OVHcloud partners are listed under the keyword **"Cloud Migration"** in the [dedicated partner directory](/links/partner). |
| 52 | + |
| 53 | +OVHcloud also offers a dedicated service: [OVHcloud Professional Services](/links/professional-services). |
| 54 | + |
| 55 | +## Cost and fees |
| 56 | + |
| 57 | +No termination fees: There is no additional charge by default for data migration. Billing stops as soon as the service is terminated. However, a pricing change will occur when data is restored, based on the current pricing of the storage medium to which the data has been transferred. |
| 58 | + |
| 59 | +## Retention of data after contract termination |
| 60 | + |
| 61 | +OVHcloud does not retain any data after the service is terminated. Data are irreversibly deleted. A manual export must be performed beforehand to preserve the data. |
| 62 | +To retrieve their data, the customer must unarchive it and then retrieve it from the bucket where it has been restored.<br> |
| 63 | +**Note:** the unarchiving process can take up to 48 hours. |
| 64 | + |
| 65 | +<sup>1</sup>: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc. |
0 commit comments