|
| 1 | +--- |
| 2 | +title: Object Storage product reversibility policy |
| 3 | +updated: 2025-06-24 |
| 4 | +--- |
| 5 | + |
| 6 | +## Objective |
| 7 | + |
| 8 | +This document outlines the reversibility policy for the product Object Storage. |
| 9 | + |
| 10 | +This policy aims to implement the general principles of reversibility and our compliance with the SWIPO IaaS Code of Conduct for cloud providers. |
| 11 | + |
| 12 | +## List of features |
| 13 | + |
| 14 | +The features of the Product are divided into three categories: |
| 15 | + |
| 16 | +- The main features for which we guarantee you the possibility to migrate. |
| 17 | +- The OVHcloud implementation, the migration of which will require adaptations to a new environment. |
| 18 | +- Specific features which migration as such is impossible to guarantee because they are linked to the OVHcloud environment or specific developments. |
| 19 | + |
| 20 | +### Main features |
| 21 | + |
| 22 | +| **Feature** | **Description** | **Available formats** | **Migration model** | **Available documentation** | |
| 23 | +| --- | --- | --- | --- | --- | |
| 24 | +| S3<sup>1</sup> API Compatibility | S3 compatible interface (standard RESTful API, AWS CLI tools, SDK, etc.) | S3 (REST, JSON, multipart upload) | **Incoming**: Direct upload via compatible S3 API, CLI tools, SDK or migration from any other S3-compatible storage. <br> **Outgoing**: Direct upload/export via S3 API, CLI or SDK to any other S3-compatible provider. |[S3 API](/pages/storage_and_backup/object_storage/pcs_object_storage_standard_s3_and_swift_rest_api_compatibility) | |
| 25 | +| Massive export/import of objects | Batch data import/export via S3 tools (sync, cp, etc.) | S3 (objects, folders) | **Incoming**: Use rclone or equivalent tools to migrate data from another solution <br> **Outgoing**: Massive export via the same tools to another S3 platform or compatible. | [Manage buckets](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) | |
| 26 | +| Object versioning | Native management of object versions (storage of each version when editing/deleting) | S3 (versioning) | **Incoming**: Import versioned objects from another S3.<br> **Outgoing**: Export versions via API/CLI, compatible with other S3. | [Getting started with versioning](/pages/storage_and_backup/object_storage/s3_versioning) | |
| 27 | +| Server-side encryption (SSE-S3/SSE-C) | Native encryption of objects at rest, compatible with S3 standards | S3 (HSSE-S3, HSSE-C) | **Incoming**: Upload of encrypted or unencrypted data, transparent management.<br> **Output**: Export without adaptation, encryption maintained or reprocessed by the target. | [Object Storage Encryption](/pages/storage_and_backup/object_storage/s3_encrypt_your_objects_with_sse_c) | |
| 28 | +| Interoperability with third-party solutions | Native support for Veeam, HYCU, Nextcloud, Kubernetes, etc. | S3 (API, JSON, objets) | **Incoming**: Direct integration via plugins or connectors.<br> **Outgoing**: Export data via native tools or S3 API to the target. | [Object storage with Veeam](/pages/storage_and_backup/object_storage/s3_veeam) | |
| 29 | + |
| 30 | +### OVHcloud Implementation |
| 31 | + |
| 32 | +| **Feature** | **Description** | **Available formats** | **Migration model** | **Available documentation** | |
| 33 | +| --- | --- | --- | --- | --- | |
| 34 | +| Asynchronous Replication OVHcloud | Automatic replication of data to a separate OVHcloud region configured by the client | S3 (replicated objects) | **Incoming**: Not applicable to direct import, requires OVHcloud configuration.<br> **Outgoing**: Manual restore from the replicated region, then export to external target (requires adaptation if the target does not have an equivalent mechanism). | [Cross region replication](/pages/storage_and_backup/object_storage/s3_asynchronous_replication) | |
| 35 | +| Object Lock | Object immutability (WORM), prevents deletion/modification for a defined period | S3 (Object Lock) | **Incoming**: Requires the source to support S3 Object Lock.</b> **Outgoing**: Export possible, but the target must support S3 locking or manual adjustment of immutability policies.** | [Object storage ObjectLock](/pages/storage_and_backup/object_storage/s3_managing_object_lock) | |
| 36 | +| ACL and advanced access management | Rights management access via ACL S3, or specific policies | S3 (ACL, policies) | **Incoming** : Adaptation of accesses according to the target structure. <br> **Outgoing**: Export of objects, but reconfiguration of ACL/policies required on the destination platform | [Access management](/pages/storage_and_backup/object_storage/s3_bucket_acl) | |
| 37 | + |
| 38 | +### Specific features |
| 39 | + |
| 40 | +| **Feature** | **Description** | **Available formats** | **Migration model** | **Available documentation** | |
| 41 | +| --- | --- | --- | --- | --- | |
| 42 | +| Management via OVHcloud Manager/OVHcloud API | OVHcloud proprietary GUI and API for storage management | N/A | **Incoming**: Not applicable. **Output**: Scripts/API to be rewritten for the target environment. | [Manage-buckets](/pages/storage_and_backup/object_storage/s3_bucket_acl) | |
| 43 | + |
| 44 | +## List of architectures |
| 45 | + |
| 46 | +Object Storage by OVHcloud uses erasure coding to ensure resiliency and prevent from a rack failure. It garantees a high availability and the continuity of the service even in the event of major outages |
| 47 | +Asynchronous replication is available as an option (Asynchronous Replication), allowing automatic data backup to another OVHcloud region. |
| 48 | + |
| 49 | +## Partner services |
| 50 | + |
| 51 | +OVHcloud partners are listed with the keyword "Cloud Migration" in the [dedicated 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:** No extra billing. The service is stopped immediately once it's removed. |
| 58 | + |
| 59 | +## Data retention after termination of the contract |
| 60 | + |
| 61 | +The data (Objects and Buckets) can be deleted by customer action (CLI) or via a service decommission by deleting the Public Cloud project related to the product. This triggers an automatic release of resources. No data restoration will be possible after these actions. |
| 62 | + |
| 63 | +Manual export is necessary to preserve your data. |
| 64 | +However, you should pay close attention to the Object Lock feature. You can find more information on our guide to [Managing object immutability with Object Lock (WORM)](/pages/storage_and_backup/object_storage/s3_managing_object_lock). |
| 65 | + |
| 66 | +<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