Object Storage product reversibility policy
62 Views
27.06.2025 
Cloud / Object Storage S3
Objective
This document outlines the reversibility policy for the Object Storage product.
This policy aims to implement the general principles of reversibility and our compliance with the SWIPO IaaS Code of Conduct for cloud providers.
List of features
The features of the Object Storage product are divided into three categories:
- Main features for which we guarantee migration capacity.
- OVHcloud implementations that require adaptation to a new migration environment.
- Specific features that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments.
1 - Main features
| Feature | Description | Available formats | Migration model | Available documentation |
|---|---|---|---|---|
| S31 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. Outgoing: Direct upload/export via S3 API, CLI or SDK to any other S3-compatible provider. | S3 API |
| 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. Outgoing: Massive export via the same tools to another S3 platform or compatible. | Manage buckets |
| Object versioning | Native management of object versions (storage of each version when editing/deleting). | S3 (versioning) | Incoming: Import versioned objects from another S3. Outgoing: Export versions via API/CLI, compatible with other S3. | Getting started with versioning |
| Server-side encryption (SSE-S3/SSE-C) | Native encryption of objects at rest, compatible with S3 standards. | S3 (SSE-S3, SSE-C) | Incoming: Upload of encrypted or unencrypted data, transparent management. Output: Export without adaptation, encryption maintained or reprocessed by the target. | Object Storage Encryption |
| Interoperability with third-party solutions | Native support for Veeam, HYCU, Nextcloud, Kubernetes, etc. | S3 (API, JSON, objets) | Incoming: Direct integration via plugins or connectors. Outgoing: Export data via native tools or S3 API to the target. | Object storage with Veeam |
2 - OVHcloud Implementations
| Feature | Description | Available formats | Migration model | Available documentation |
|---|---|---|---|---|
| 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. 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 |
| Object Lock | Object immutability (WORM), prevents deletion/modification for a defined period. | S3 (Object Lock) | Incoming: Requires the source to support S3 Object Lock. Outgoing: Export possible, but the target must support S3 locking or manual adjustment of immutability policies. | Object storage ObjectLock |
| 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. Outgoing: Export of objects, but reconfiguration of ACL/policies required on the destination platform. | Access management |
3 - Specific features
| Feature | Description | Available formats | Migration model | Available documentation |
|---|---|---|---|---|
| Management via OVHcloud Control Panel/OVHcloud API | OVHcloud proprietary GUI and API for storage management. | N/A | Incoming: Not applicable. Outgoing: Scripts/API to be rewritten for the target environment. | Manage-buckets |
List of architectures
Object Storage by OVHcloud uses erasure coding to ensure resiliency and prevent from a rack failure. It guarantees a high availability and the continuity of the service even in the event of major outages.
Asynchronous replication is available as an option (Asynchronous Replication), allowing automatic data backup to another OVHcloud region.
Partner services
The OVHcloud partners concerned are listed in the OVHcloud partners directory under the "Data center expansion and migration" filter.
OVHcloud also offers a dedicated service : OVHcloud Professional Services.
Cost and fees
No termination fees: No extra billing, the service is stopped immediately once it's removed.
Data retention after termination of the contract
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.
Manual export is necessary to preserve your data.
However, you should pay close attention to the Object Lock feature. You can find more information on our guide : "Object Storage - Managing object immutability with Object Lock (WORM)".
1: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.
Global Reversibility Policy
441